feat: add Mem0 memory provider support and update docs#227
Open
kartik-mem0 wants to merge 1 commit into666ghj:mainfrom
Open
feat: add Mem0 memory provider support and update docs#227kartik-mem0 wants to merge 1 commit into666ghj:mainfrom
kartik-mem0 wants to merge 1 commit into666ghj:mainfrom
Conversation
dosubot
bot
added
size:XXL
kartik-mem0
force-pushed
the
feat/mem0-integration
branch
from
44d0a4a to
da3528e
Compare
Adds Mem0 as an optional memory backend alongside the existing Zep Cloud integration. Users choose via MEMORY_PROVIDER env var (zep default, mem0 optional). Supports both Mem0 Platform (SaaS) and Mem0 OSS (self-hosted). Zero breaking changes - all existing Zep behavior is untouched.
kartik-mem0
force-pushed
the
feat/mem0-integration
branch
from
da3528e to
0bca4c4
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds Mem0 as an optional memory backend alongside the existing Zep Cloud integration. Users choose via MEMORY_PROVIDER env var (zep default, mem0 optional). Supports both Mem0 Platform (SaaS) and
Mem0 OSS (self-hosted). Zero breaking changes — all existing Zep behavior is untouched.
How it works
MEMORY_PROVIDER=zep (default) → existing Zep services, no change
MEMORY_PROVIDER=mem0 → Mem0 backend (Platform or OSS)
A thin MemoryProvider interface sits between API routes and the backend. ZepProvider delegates to existing Zep services (pure delegation, no behavior change). Mem0Provider implements the same
interface using mem0ai SDK.
Existing Zep service files (graph_builder.py, zep_entity_reader.py, zep_tools.py, zep_graph_memory_updater.py) are completely untouched.
Setup for Mem0
pip install mem0ai # only needed if using Mem0
Platform (managed)
MEMORY_PROVIDER=mem0
MEM0_API_KEY=your_key
OR OSS (self-hosted)
MEMORY_PROVIDER=mem0
OPENAI_API_KEY=your_key
Test plan