claude-mem vs mem0

The two are close in size: 101.9k stars for claude-mem, 67.5k for mem0. Over the days we have tracked them claude-mem moved +15.4% and mem0 +9.8%, so claude-mem is growing faster right now.

claude-mem leads on context depth and model freedom. mem0 does not take any axis by a clear margin.

Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.

Where they stand today

Claude-Mem pairs a Claude Code–focused persistent memory with progressive-disclosure search tools and a local worker/web UI to deliver token-efficient, session-persistent context.

Stars
101.9k
Tracked growth
+15.4%
Maturity
●●●●●
Last commit
9h ago
Language
TypeScript
License
Apache-2.0
Cost to run
Your API key for model calls; optional cloud backup to cmem.ai

Provides a production-ready, self-hostable memory layer with a token-efficient memory algorithm, entity linking, and agent skills for easy integration into AI assistants.

Stars
67.5k
Tracked growth
+9.8%
Maturity
●●●●●
Last commit
9h ago
Language
Python
License
Apache-2.0
Cost to run
Your LLM/API key costs; self-host or paid cloud available
0%+15%90 tracked days
thedotmack/claude-memmem0ai/mem0

Six axes, head to head

Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.

Axisclaude-memmem0
Context depth
How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository.
●●●●●
Related files & memory
●●●●●
User/session only
Noise control
How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only.
●●●●●
Configurable filters
●●●●●
Multi-signal retrieval
Customization
How far it bends to your team: custom rules, prompts, style guides, per-path config.
●●●●●
Config file & modes
●●●●●
Plugins & config
Privacy
Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only.
●●●●●
Self-hostable (local worker)
●●●●●
Self-hostable
Model freedom
Whether you can point it at any provider, or it is wired to one.
●●●●●
Bring-your-key (many providers)
●●●●●
Multiple LLMs
Setup ease
What it takes to get a first useful run out of it.
●●●●●
One-command install
●●●●●
One-command start

Which one to pick

Pick claude-mem if…

Easy setup — one-command installer and a local worker that preserves and injects compressed session context into future Claude Code sessions.

  • Context depth: Related files & memory (3/5 against 1/5)
  • Model freedom: Bring-your-key (many providers) (5/5 against 3/5)
Runs in cli, ide, coding-agent-plugin, web-app. Works with byok, anthropic, openai, gemini.

Pick mem0 if…

Self-hostable — one-command bootstrap and SDKs let teams add a scalable, token-efficient memory layer while keeping data under their control.

Runs in cli, web-app, coding-agent-plugin. Works with byok, openai.

What people want from each one

Questions people ask

Is claude-mem better than mem0?

claude-mem leads on context depth and model freedom. mem0 does not take any axis by a clear margin. claude-mem is worth picking when easy setup — one-command installer and a local worker that preserves and injects compressed session context into future Claude Code sessions.

Which of claude-mem and mem0 keeps my code private?

claude-mem: Self-hostable (local worker) (4/5). mem0: Self-hostable (4/5).

What does each one cost to run?

claude-mem: Your API key for model calls; optional cloud backup to cmem.ai. mem0: Your LLM/API key costs; self-host or paid cloud available.

Full profiles: thedotmack/claude-mem and mem0ai/mem0. Everything else in Memory & context.