agentmemory vs claude-mem
claude-mem is much bigger: 93.2k stars against 28.0k. Over the days we have tracked them agentmemory moved +25.3% and claude-mem +6.6%, so agentmemory is growing faster right now.
Neither one leads on the six capability axes, so the choice comes down to which of them fits the way you already work.
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
Provides a local, multi-agent persistent memory server with hybrid retrieval and confidence scoring that shares memories across any MCP/HTTP agent.
- Stars
- 28.0k
- Tracked growth
- +25.3%
- Maturity
- ●●●●●
- Last commit
- 5d ago
- Language
- TypeScript
- License
- Apache-2.0
- Cost to run
- Free to run locally; optional cloud API keys for agent LLMs.
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
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 | agentmemory | claude-mem |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Diff + related files | ●●●●● Related files & memory |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Confidence scoring | ●●●●● Configurable filters |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Config file options | ●●●●● Config file & modes |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Fully local | ●●●●● Self-hostable (local worker) |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Provider-agnostic | ●●●●● Bring-your-key (many providers) |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One-command setup | ●●●●● One-command install |
Which one to pick
Pick agentmemory if…
Easy setup — one-command local memory server with a demo and adapters for many coding agents, preserving session memory across restarts.
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.
What people want from each one
rohitg00/agentmemory
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
Questions people ask
Is agentmemory better than claude-mem?
Neither one leads on the six capability axes, so the choice comes down to which of them fits the way you already work. agentmemory is worth picking when easy setup — one-command local memory server with a demo and adapters for many coding agents, preserving session memory across restarts.
Which of agentmemory and claude-mem keeps my code private?
agentmemory: Fully local (5/5). claude-mem: Self-hostable (local worker) (4/5).
What does each one cost to run?
agentmemory: Free to run locally; optional cloud API keys for agent LLMs.. claude-mem: Your API key for model calls; optional cloud backup to cmem.ai.
Full profiles: rohitg00/agentmemory and thedotmack/claude-mem. Everything else in Memory & context.