Mem0 question

[vijaykammili]

Hey @whysosaket , @toi500 , @HenryHengZJ - Thanks for adding the mem0 node, it's great! I'm looking to implement user memory search across sessions to recall past interactions in new sessions. Any advice on how to achieve this?

For Ex:

User: X
Session: 11111 (Runid)
User Input: My name is X

User: X
Session: 22222 (Runid)
User Input: I like cars

User: X
Session: 33333 (Runid)
User Input: Tell me about myself
Retrieved Memories: Name is X, Likes cars
Agent: Your name is X and you like cars.

I've tried a few different ways but couldn't seem to get the mem0 node to behave this way? Any suggestions?

[toi500]

Isn't that what the mem0 node does by default? As soon as you hardcode the User ID in the node, mem0 will construct a set of memories for that user ID, for that whole flow, independently from where the user query it.

So, you can have Flowise Session IDs 11111, 22222, 33333 all pointing to the same User ID (in Mem0).

Here is an example. I provide my name and say I love cars in 2 different Flowise sessions ID still, in another new session ID, the AI puts both pieces of knowledge together from Mem0.

[vijaykammili]

Thank you @toi500 - Yes that is accurate, if you leave everything default. However, When i try to pass a user id and run id via overrrideconfig, it doesn't behave this way. It forgets the information i provided in the past two sessions.

Here is what gets inserted into mem0 with defaults.

Here it is with overrideconfig values of user id of "vj" and unique run ids for each session

I think the sessionid is being inserted as the user id and user id as agent id when performing an overrride config

[toi500]

Could you share what your Flowise Mem0 node looks like? Additional Para included.

[vijaykammili]

Sure.

Mem0 node:

Additional Params:

Here is the payload.

{
"question": "Hi my name is vj",
"streaming": false,
"chatId": "11111",
"overrideConfig": {
"sessionId": "11111",
"user_id": "vj",
"run_id" : "11111"
}
}

Response: Hello How can i help you?

{
"question": "What is my name?",
"streaming": false,
"chatId": "11112",
"overrideConfig": {
"sessionId": "11111",
"user_id": "vj",
"run_id" : "11111"
}
}

Response: Your name is vj.

2nd session

{
"question": "What is my name?",
"streaming": false,
"chatId": "22222",
"overrideConfig": {
"sessionId": "22222",
"user_id": "vj",
"run_id" : "22222"
}
}

[whysosaket]

Hey @vijaykammili, sorry for the late reply! The issue is happening because we used get_all instead of search.

In our setup, user_id is tied to long-term memories, while run_id is used for short-term memories. The get_all method only fetches based on one ID, so you’d need to pass both user_id and run_id to get the full context.

This is handled properly in search, which takes both into account. The good news is that this will be resolved once we roll out the semantic search in Flowise Node — check out PR #4273 for details.

[toi500]

I was not aware of this limitation. Thank you @vijaykammili for pointing it out and @whysosaket for the explanation and the PR.

cc: @HenryHengZJ

[vijaykammili]

@whysosaket. Thank you so much. That makes sense.