add conversation id functionality #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
💡 Enable Vercel Agent with $100 free credit for automated AI reviews |
Dhravya
approved these changes
Oct 22, 2025
Dhravya
pushed a commit
that referenced
this pull request
Nov 7, 2025
Feat: NewChat now have different ConversationID. Retains user's Memory
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TL;DR
Added
conversationIdparameter to the supermemory wrapper in the chat API.What changed?
Added the conversation ID (
id) as theconversationIdparameter when initializing the language model with supermemory in the chat API route handler.How to test?
Why make this change?
This change ensures that the supermemory system can properly track and associate memories with specific conversations by their ID. Without this parameter, the system might not correctly maintain context between different messages in the same conversation, potentially leading to degraded conversation quality and memory retrieval issues.