Claude Code auto-memory vs claude-mem
Claude Code auto-memory vs claude-mem: side-by-side comparison of two claude code memory mechanisms systems — architecture, taxonomy, license, pricing, MCP/A2A support, and direct edges.
Claude Code auto-memory · claude-mem
Cost & capability
| Claude Code auto-memory | claude-mem | |
|---|---|---|
| Capability band | competent | competent |
| Capability composite | 70 | 55 |
| Cost tier | — | free |
| $/Mtok input | — | 0 |
| $/Mtok output | — | 0 |
| Use cases | Code Generation Focused, Long Running Session, Offline Capable | Code Generation Focused, Long Running Session |
Where they differ (8)
Rows where both sides have data and the values disagree — the shortlist of dimensions that actually distinguish these two systems.
| Claude Code auto-memory | claude-mem | |
|---|---|---|
| Capability composite | 70 | 55 |
| Use cases | Code Generation Focused, Long Running Session, Offline Capable | Code Generation Focused, Long Running Session |
| Type | Per-project file directory | Episodic / session-log compression |
| Created | 2025-03 (Claude Code v1.0 launched Feb/Mar 2025; auto-memory feature in subsequent releases; v2.1.59+ required) | 2025-09 |
| Backend storage | file (~/.claude/projects/<project>/MEMORY.md) | searched not found |
| Multi-tenancy | hard-isolation (per project) | searched not found |
| MCP | native (first-party) — Claude Code consumes MCP | native (first-party) |
| OpenTelemetry | searched not found | no |
At a glance
| Claude Code auto-memory | claude-mem | |
|---|---|---|
| Section | Claude Code memory mechanisms | Claude Code memory mechanisms |
| Tier | T1 | T1 |
| Type | Per-project file directory | Episodic / session-log compression |
| Created | 2025-03 (Claude Code v1.0 launched Feb/Mar 2025; auto-memory feature in subsequent releases; v2.1.59+ required) | 2025-09 |
| Latest release | — | v12.7.0 2026-05-06 |
| License | — | AGPL-3.0 |
| GitHub | — | 72.7k★ +9.1k/mo TypeScript |
| Pricing | — | free / open source (AGPL-3.0); no paid tier |
| Backend storage | file (~/.claude/projects/<project>/MEMORY.md) | searched not found |
| Deployment | — | local — SQLite + FTS5 per project; optional Chroma vector; no cloud |
| API surface | — | searched not found |
| Embedding | — | searched not found |
| Multi-tenancy | hard-isolation (per project) | searched not found |
| MCP | native (first-party) — Claude Code consumes MCP | native (first-party) |
| A2A | not supported | not supported |
| OpenTelemetry | searched not found | no |
| Optimised for | Claude-Code-native + MCP-portable memory | Claude-Code-native + MCP-portable memory |
| Anti-fit | not for non-Claude-Code clients (some are MCP-portable) | not for non-Claude-Code clients (some are MCP-portable) |
Taxonomy
| Axis | Claude Code auto-memory | claude-mem |
|---|---|---|
| storage | file | file |
| retrieval | injection | injection |
| persistence | cross-session | cross-session |
| update | append-only | consolidation |
| unit | fact | summary |
| governance | user-controllable | inspectable |
| conflict | append | append |
Pros & cons
Claude Code auto-memory
Pros: Per-project automatic memory built into the runtime — no plugin install, no external store, no extra prompts.
Cons: Single-vendor lock-in to Claude Code; no inspect/edit UI for what's been auto-saved; opaque to other tools.
claude-mem
Pros: OSS plugin that adds auto-memory + indexing without sending data to Anthropic's cloud — strongest privacy posture for Claude Code memory.
Cons: Plugin install + maintenance burden; less polished than first-party auto-memory.