Add mem0 Memory Implementation #6510

alpha-xone · 2025-05-11T19:51:11Z

Why are these changes needed?

These changes are needed to expand AutoGen's memory capabilities with a robust, production-ready integration with Mem0.ai.

This PR adds a new memory component for AutoGen that integrates with Mem0.ai, providing a robust memory solution that supports both cloud and local backends. The Mem0Memory class enables agents to store and retrieve information persistently across conversation sessions.

Key Features

Seamless integration with Mem0.ai memory system
Support for both cloud-based and local storage backends
Robust error handling with detailed logging
Full implementation of AutoGen's Memory interface
Context updating for enhanced agent conversations
Configurable search parameters for memory retrieval

Related issue number

Checks

I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://github.com/microsoft/autogen/blob/main/CONTRIBUTING.md to build and test documentation locally.
I've added tests (if relevant) corresponding to the changes introduced in this PR.
I've made sure all auto checks have passed.

gitguardian · 2025-05-11T19:51:46Z

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

alpha-xone · 2025-05-11T20:18:00Z

@microsoft-github-policy-service agree

ekzhu

Thanks for the PR! Could you add unit tests so we can ensure the correctness of the features?

codecov · 2025-05-13T03:34:19Z

Codecov Report

Attention: Patch coverage is 80.00000% with 30 lines in your changes missing coverage. Please review.

Project coverage is 79.77%. Comparing base (8a2582c) to head (7ed5163).

Files with missing lines	Patch %	Lines
...ackages/autogen-ext/src/autogen_ext/memory/mem0.py	80.00%	30 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##             main    #6510    +/-   ##
========================================
  Coverage   79.77%   79.77%            
========================================
  Files         228      229     +1     
  Lines       17054    17204   +150     
========================================
+ Hits        13605    13725   +120     
- Misses       3449     3479    +30

Flag	Coverage Δ
unittests	`79.77% <80.00%> (+<0.01%)`	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

…nto mem0-memory

alpha-xone · 2025-05-13T09:03:47Z

Thanks for replying 🚀

Unit test added: https://github.com/alpha-xone/autogen/actions/runs/14992498495
This is tested with my mem0 api key. If the test is from the main branch, it requires another key to test.

ekzhu · 2025-05-14T17:00:43Z

Thanks for adding the tests. Can we use the open source verison of mem0? I think it can run entirely locally.

alpha-xone · 2025-05-14T17:18:36Z

Yes we can. I'm running it locally with the combination of neo4j for graph storage + chromadb for vector db + SQLite for historical db. All we need to do is setup the local environment and pass a dict of configurations of these in. But for unit testing, I'm not sure how to make these environments ready to test.

ekzhu · 2025-05-14T22:48:54Z

For SQLite and Chroma DB, I think you can instantiate directly as test fixture, right? See example on ChromaDBVectorMemory tests: https://github.com/microsoft/autogen/blob/78ef148c88beb29a7e7602aa39a772b0ffbc50d5/python/packages/autogen-ext/tests/memory/test_chroma_memory.py

For Neo4j, there should be github actions that can set this up in CI. For local integration test, we can skip it if no neo4j server is running.

Besides all these above, I thought mem0's can run independently as in-memory python code? That's my impression reading their documentation. https://docs.mem0.ai/open-source/python-quickstart#basic

…nto mem0-memory

alpha-xone · 2025-05-16T10:55:42Z

The neo4j container cannot initiated on the server:
https://github.com/alpha-xone/autogen/actions/runs/15066738718

  Error: Failed to initialize container neo4j:5.19
Error: One or more containers failed to start.

I can only test locally with the same config in the test_mem0.py file - it's working on my side.

…nto mem0-memory

alpha-xone · 2025-06-03T01:08:59Z

@alpha-xone, I merged from main into this branch, and approved the workflows to run.

Instead of running mem0 in a fully local way, test_mem0.py seems to be expecting a cloud API key.

FAILED tests/memory/test_mem0.py::test_component_serialization - ValueError: Mem0 API Key not provided. Please provide an API Key.

hi @rickyloynd-microsoft

Thanks for merging. Looks like this function was only one missing MagicMock decorator. I've removed environment variables and tried again in CI again - it has passed without keys: https://github.com/alpha-xone/autogen/actions/runs/15406124123

rickyloynd-microsoft · 2025-06-03T01:20:47Z

Thanks for merging. Looks like this function was only one missing MagicMock decorator. I've removed environment variables and tried again in CI again - it has passed without keys: https://github.com/alpha-xone/autogen/actions/runs/15406124123

That's awesome!

Any questions about how to fix and test the format & lint checks etc? The instructions here about uv can be challenging.

alpha-xone · 2025-06-03T01:25:16Z

Thanks for merging. Looks like this function was only one missing MagicMock decorator. I've removed environment variables and tried again in CI again - it has passed without keys: https://github.com/alpha-xone/autogen/actions/runs/15406124123

That's awesome!

Any questions about how to fix and test the format & lint checks etc? The instructions here about uv can be challenging.

I've tested the format & lint locally with the poe check command you shared earlier. Does it raise errors on the cloud?

rickyloynd-microsoft · 2025-06-03T04:02:33Z

I've tested the format & lint locally with the poe check command you shared earlier. Does it raise errors on the cloud?

Yes, you should be able to see the failing checks listed at the bottom of the PR Conversation page in github.

rickyloynd-microsoft · 2025-06-03T19:25:33Z

@alpha-xone, the repo currently has an issue with uv versioning, which may be causing a lot of the check failures in the list. I'll try to give you some solution steps soon.

rickyloynd-microsoft · 2025-06-03T22:13:34Z

@alpha-xone, your PR should update python/uv.lock. Please try the following steps:

Pull the current remote mem0-memory branch to your local branch, to get the latest merges from main.
Checkout python/uv.lock
Overwrite uv.lock with the latest copy of uv.lock from main.
In the python dir, do uv sync --all-extras. This will modify uv.lock.
Run the usual local poe checks.
Checkin and push the modified uv.lock to your remote branch.

Hopefully this will fix most of the remaining errors.

alpha-xone · 2025-06-04T01:46:17Z

Hi @rickyloynd-microsoft

Thanks a lot for the detailed instructions. I'm trying the fixes and hopefully can fix in few days.

alpha-xone · 2025-06-07T16:21:50Z

hi @rickyloynd-microsoft

I tried the above steps, and I've uploaded the uv.lock after step 4 but before 5.
The poe check does not work as below.
Copilot says it may be due to docker and OpenAI keys, which I don't have on my side.
These are not related to, nor required for the codes I added.

Is it possible to run the tests online again and I tried to look where to fix? Thanks

rickyloynd-microsoft · 2025-06-07T17:00:07Z

hi @rickyloynd-microsoft

I tried the above steps, and I've uploaded the uv.lock after step 4 but before 5. The poe check does not work as below. Copilot says it may be due to docker and OpenAI keys, which I don't have on my side. These are not related to, nor required for the codes I added.

Is it possible to run the tests online again and I tried to look where to fix? Thanks

Sure, if you push a change to the branch, I'll approve the checks to be run again.

alpha-xone · 2025-06-07T17:05:18Z

hi @rickyloynd-microsoft

Great, thanks. Could you approve current branch pls - there is no update to main button now - I think there's no change since my last upload. There could be some time to fix CIs. Thanks

rickyloynd-microsoft · 2025-06-07T17:26:56Z

hi @rickyloynd-microsoft

Great, thanks. Could you approve current branch pls - there is no update to main button now - I think there's no change since my last upload. There could be some time to fix CIs. Thanks

There's no button for me to approve the check workflow right now, because you haven't pushed any changes since the last time it ran.

alpha-xone · 2025-06-07T17:30:13Z

does it require Eric to review?

rickyloynd-microsoft · 2025-06-07T17:33:10Z

does it require Eric to review?

Merging the PR requires the review, and it requires that all the checks pass.

alpha-xone · 2025-06-07T18:21:45Z

Should be able to approve now:

Fixed the bug in uv.lock - it's missing the agbench version, which is missing running the uv command.

rickyloynd-microsoft · 2025-06-07T19:18:47Z

Should be able to approve now:

Fixed the bug in uv.lock - it's missing the agbench version, which is missing running the uv command.

Not sure I understand. No PR can be approved or merged until none of the checks fail. For instance, PR #6622 passes the checks and is awaiting approval.

alpha-xone · 2025-06-08T01:48:48Z

finally! all checks passed!

The problem was:
uv sync --all-extras does not add version to a few autogen packages in their [[package]] sections.
Hope noting this can make easier for others in the future. 🙏

rickyloynd-microsoft · 2025-06-08T03:33:35Z

finally! all checks passed!

The problem was: uv sync --all-extras does not add version to a few autogen packages in their [[package]] sections. Hope noting this can make easier for others in the future. 🙏

That's great! Do you have recommendations for the [[package]] sections or the readme.md to help others deal with this?

alpha-xone · 2025-06-08T07:05:43Z

@alpha-xone, your PR should update python/uv.lock. Please try the following steps:

Pull the current remote mem0-memory branch to your local branch, to get the latest merges from main.

Checkout python/uv.lock

Overwrite uv.lock with the latest copy of uv.lock from main.

In the python dir, do uv sync --all-extras. This will modify uv.lock.

Run the usual local poe checks.

Checkin and push the modified uv.lock to your remote branch.

Hopefully this will fix most of the remaining errors.

Sure.

On top of the 5 steps above, just add two versions below.
The problem with uv.lock will be gone:

[[package]]Add commentMore actions
name = "agbench"Add commentMore actions
version = "0.0.1a1"

...

[[package]]Add commentMore actions
name = "autogenstudio"
version = "0.4.2.2"

Note: need to read the exact versions from main.

rickyloynd-microsoft · 2025-06-08T13:39:55Z

I'll try to run the code and finish reviewing the PR this week. Thanks @alpha-xone !

add mem0 memory implementation

4c78cf9

alpha-xone and others added 2 commits May 12, 2025 04:07

remove secrets

41fd2aa

Merge branch 'main' into mem0-memory

42f82af

alpha-xone added 3 commits May 12, 2025 11:59

add documentation

64f9005

fix load_component

63aa592

fix demo

343d363

alpha-xone changed the title ~~add mem0 memory implementation~~ Add mem0 Memory Implementation May 12, 2025

victordibia and others added 2 commits May 12, 2025 09:08

Merge branch 'main' into mem0-memory

455d4ab

Merge branch 'main' into mem0-memory

b360f78

ekzhu requested changes May 13, 2025

View reviewed changes

alpha-xone added 7 commits May 13, 2025 14:00

add unitest

042ccf4

Merge branch 'mem0-memory' of https://github.com/alpha-xone/autogen i…

b55669a

…nto mem0-memory

add workflow to test

f7a2a85

fix install dependencies

7931b47

fix dependencies

3f4db19

env variables ref fix

b675474

coverage in console

317841e

Merge branch 'main' into mem0-memory

6fb0ed3

alpha-xone added 3 commits May 16, 2025 18:39

add tests for local mem0 storeage

caa825e

Merge branch 'mem0-memory' of https://github.com/alpha-xone/autogen i…

f8f0b4d

…nto mem0-memory

fix neo4j container

07180fe

ekzhu self-assigned this May 19, 2025

Merge branch 'mem0-memory' of https://github.com/alpha-xone/autogen i…

4085d7b

…nto mem0-memory

Merge branch 'main' into mem0-memory

c51860b

alpha-xone and others added 4 commits June 6, 2025 20:43

Merge branch 'main' into mem0-memory

2584a6e

correct format

d615eae

updated uv.lock

72878f6

formating

b8345db

alpha-xone requested a review from ekzhu June 7, 2025 17:28

alpha-xone added 3 commits June 8, 2025 01:38

commit for approval of CI

e902e03

updated uv.lock

3d3980d

try fixing uv.lock

ab95e5b

fix uv.lock

7ed5163

Add mem0 Memory Implementation #6510

Are you sure you want to change the base?

Add mem0 Memory Implementation #6510

Uh oh!

Conversation

alpha-xone commented May 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Why are these changes needed?

Key Features

Related issue number

Checks

Uh oh!

gitguardian bot commented May 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

️✅ There are no secrets present in this pull request anymore.

Uh oh!

alpha-xone commented May 11, 2025

Uh oh!

ekzhu left a comment

Choose a reason for hiding this comment

Uh oh!

codecov bot commented May 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

alpha-xone commented May 13, 2025

Uh oh!

ekzhu commented May 14, 2025

Uh oh!

alpha-xone commented May 14, 2025

Uh oh!

ekzhu commented May 14, 2025

Uh oh!

alpha-xone commented May 16, 2025

Uh oh!

alpha-xone commented Jun 3, 2025

Uh oh!

rickyloynd-microsoft commented Jun 3, 2025

Uh oh!

alpha-xone commented Jun 3, 2025

Uh oh!

rickyloynd-microsoft commented Jun 3, 2025

Uh oh!

rickyloynd-microsoft commented Jun 3, 2025

Uh oh!

rickyloynd-microsoft commented Jun 3, 2025

Uh oh!

alpha-xone commented Jun 4, 2025

Uh oh!

alpha-xone commented Jun 7, 2025

Uh oh!

rickyloynd-microsoft commented Jun 7, 2025

Uh oh!

alpha-xone commented Jun 7, 2025

Uh oh!

rickyloynd-microsoft commented Jun 7, 2025

Uh oh!

alpha-xone commented Jun 7, 2025

Uh oh!

rickyloynd-microsoft commented Jun 7, 2025

Uh oh!

alpha-xone commented Jun 7, 2025

Uh oh!

rickyloynd-microsoft commented Jun 7, 2025

Uh oh!

alpha-xone commented Jun 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rickyloynd-microsoft commented Jun 8, 2025

Uh oh!

alpha-xone commented Jun 8, 2025

Uh oh!

rickyloynd-microsoft commented Jun 8, 2025

Uh oh!

Uh oh!

alpha-xone commented May 11, 2025 •

edited

Loading

gitguardian bot commented May 11, 2025 •

edited

Loading

codecov bot commented May 13, 2025 •

edited

Loading

alpha-xone commented Jun 8, 2025 •

edited

Loading