claude-mem vs mem0
The two are close in size: 93.2k stars for claude-mem, 64.7k for mem0. Over the days we have tracked them claude-mem moved +6.6% and mem0 +6.1%, 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
- 93.2k
- Tracked growth
- +6.6%
- Maturity
- ●●●●●
- Last commit
- 5h ago
- Language
- JavaScript
- 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
- 64.7k
- Tracked growth
- +6.1%
- Maturity
- ●●●●●
- Last commit
- 18h ago
- Language
- Python
- License
- Apache-2.0
- Cost to run
- Your LLM/API key costs; self-host or paid cloud available
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.
| Axis | claude-mem | mem0 |
|---|---|---|
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)
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.
What people want from each one
thedotmack/claude-mem
Hacker News: Claude-Mem drew 2 points and 1 comments.
- v13.24.0 ships the 13.23.1 bundle: manifest/worker version mismatch makes the hook kill the worker on every event 👍 5
- [plan-14] Child Process Ownership — every process the worker spawns dies with the worker 👍 2
- Unexpectedly high API cost: claude-mem adds ~64% on top of my actual coding model spend 👍 2
mem0ai/mem0
Hacker News: Show HN: Mem0 – open-source Memory Layer for AI apps drew 201 points and 61 comments.
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.