feat:Adds new Param in getChatMessages for better context handling #4273
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.
This is a proposal to introduce a new parameter in the
getChatMessages
function that allows us to retrieve the latest user message, enabling more accurate memory retrieval. Currently, Mem0 Memory usesget_all
to fetch all user memories, but this change would allow us to perform a semantic search, which is more efficient for handling context.I'd like to understand if there's a better approach to achieve this, and whether it makes sense to apply the same logic to other components as well. Thanks!
Changelog
getChatMessages
Method: Introduced a new parametercurrentMessages
to allow for dynamic message retrieval based on the latest user input, improving the context handling during chat sessions.currentMessages
to the chat history, ensuring that the latest user input is considered when fetching the memories.