[FEATURE] Mem0 Memory transition to V2 #2776
Description
Feature Area
Integration with external tools.
CrewAI currently has an option to use Mem0 for short-term, long-term, and external memory.
It would be beneficial to maintain it updated and configurable.
Describe the solution you'd like
The Mem0 has moved to v2.
This includes:
- First, support for memories associated with a specific conversation session or interaction with the help of
run_idparam for short-term memory. - Secondly, there is no ability to turn off agent memories. The agent name is always being passed as agent ID with every add API call, but in some situations, it is necessary that agents are memory-less.
- Thirdly, it would be cool to have support for mem0 new features such as (I find the most relevant once)
memory inclusion,custom categories. - And last but not least, it would be great to move from deprecated search v1 to search v2 - mem0 api reference.
I suggest updating Mem0Storage class
Describe alternatives you've considered
No response
Additional context
No response
Willingness to Contribute
I can test the feature once it's implemented.
I can try implementing it as well, just give me the instructions on how to create a branch for Mem0?
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
Participants
Activity
[-]Mem0 External Memory transition to V2[/-][+][FEATURE] Mem0 External Memory transition to V2[/+]Vidit-Ostwal commentedon May 8, 2025
Just a follow up question,
org_idandproject_idhave been removed from the mem0 V2?rusXL commentedon May 8, 2025
Nope, you still can pass them, but they are optional. Refer to official Mem0 API Docs for more.
lucasgomide commentedon May 15, 2025
@Dev-Khant do you wanna play with that?
Vidit-Ostwal commentedon May 21, 2025
Hi @rusXL, I will patch this up.
Seems like a quick fix to me.
Just has one question.
when using user_id along with run_id,
and when I do
memory.reset()all the memory gets deleted, is there any way in Mem0, where memory are getting reset for a specific run_id.This is in case, user just wants to remove one particulae run_id memory.
Let me know, as I was not able to find any documentation around resetting with new version.
[-][FEATURE] Mem0 External Memory transition to V2[/-][+][FEATURE] Mem0 Memory transition to V2[/+]rusXL commentedon May 25, 2025
Hi there. I have changed the description of the issue.
The scope is bigger.
So far, the pull requests I see do not really implement the transition and have a bunch of critical issues.
I am ready to take on implementing it myself, or review the changes
lucasgomide commentedon Jun 10, 2025
@rusXL I really appreciate that.. Let me know when the PR is ready to review (:
Vidit-Ostwal commentedon Jun 10, 2025
@lucasgomide, I think the PR I have made has all the updated features
#2893 (comment)
lucasgomide commentedon Jun 10, 2025
@Vidit-Ostwal from my understand rusXL said that is not ready, am i wrong?
let me know if is ready to review (:
Vidit-Ostwal commentedon Jun 10, 2025
Yup, took his feedback and made all the changes, asked for a review from him, got a thumbs up, thought that he is done reviewing it.
Particularly from my end, the PR is ready.
lucasgomide commentedon Jun 10, 2025
Added in my list to review, tks.
github-actions commentedon Jul 11, 2025
This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
github-actions commentedon Jul 16, 2025
This issue was closed because it has been stalled for 5 days with no activity.
lucasgomide commentedon Jul 16, 2025
Hey @Vidit-Ostwal, since you're working on that, could you give us a quick update on how things are going?