Anthropic Auto Dream vs claude-mem

Anthropic Auto Dream vs claude-mem: side-by-side comparison of two claude code memory mechanisms systems — architecture, taxonomy, license, pricing, MCP/A2A support, and direct edges.

Anthropic Auto Dream · claude-mem

Cost & capability

Anthropic Auto Dreamclaude-mem
Capability bandcompetentcompetent
Capability composite7055
Cost tiermidfree
$/Mtok input0
$/Mtok output0
Use casesCode Generation Focused, Long Running SessionCode Generation Focused, Long Running Session

Where they differ (12)

Rows where both sides have data and the values disagree — the shortlist of dimensions that actually distinguish these two systems.

Anthropic Auto Dreamclaude-mem
Capability composite7055
Cost tiermidfree
TypeREM-style sub-agent memory consolidationEpisodic / session-log compression
Created2026-05 (research-preview rollout in Claude Code; server-side feature flag)2025-09
Pricingbundled with Claude Code (no separate fee)free / open source (AGPL-3.0); no paid tier
Backend storagelocal filesystem (~/.claude/projects/<project>/memory/)searched not found
DeploymentLocal CLI (Claude Code) — Claude.ai web not in scopelocal — SQLite + FTS5 per project; optional Chroma vector; no cloud
API surface/dream slash command + /memory toggle (Auto-dream: on)searched not found
MCPnative (first-party — Claude Code built on MCP)native (first-party)
OpenTelemetryno — local CLI featureno
Optimised forbackground memory consolidation + bounded MEMORY.md size + surgical updatesClaude-Code-native + MCP-portable memory
Anti-fitnot for users on Claude.ai web (CLI-only); not for environments where consolidation logic must be auditablenot for non-Claude-Code clients (some are MCP-portable)

At a glance

Anthropic Auto Dreamclaude-mem
SectionClaude Code memory mechanisms Claude Code memory mechanisms
TierT1 T1
TypeREM-style sub-agent memory consolidation Episodic / session-log compression
Created2026-05 (research-preview rollout in Claude Code; server-side feature flag) 2025-09
Latest release v12.7.0 2026-05-06
License AGPL-3.0
GitHub 72.7k★ +9.1k/mo TypeScript
Pricingbundled with Claude Code (no separate fee) free / open source (AGPL-3.0); no paid tier
FundingAnthropic total $12.4B+ raised; $40B valuation
Backend storagelocal filesystem (~/.claude/projects/<project>/memory/) searched not found
DeploymentLocal CLI (Claude Code) — Claude.ai web not in scope local — SQLite + FTS5 per project; optional Chroma vector; no cloud
API surface/dream slash command + /memory toggle (Auto-dream: on) searched not found
Embedding searched not found
Multi-tenancy searched not found
MCPnative (first-party — Claude Code built on MCP) native (first-party)
A2Anot supported not supported
OpenTelemetryno — local CLI feature no
Optimised forbackground memory consolidation + bounded MEMORY.md size + surgical updates Claude-Code-native + MCP-portable memory
Anti-fitnot for users on Claude.ai web (CLI-only); not for environments where consolidation logic must be auditable not for non-Claude-Code clients (some are MCP-portable)

Taxonomy

AxisAnthropic Auto Dreamclaude-mem
storagefilefile
retrievalextraction-pullinjection
persistencelong-termcross-session
updateconsolidationconsolidation
unitfactsummary
governanceuser-controllableinspectable
conflictllm-arbitrateappend

Pros & cons

Anthropic Auto Dream

Pros: Bounded MEMORY.md size (200 lines) prevents context bloat; surgical updates preserve user-edited content; user-toggleable; complements rather than replaces CLAUDE.md.

Cons: Closed-source; opt-out mechanism not formally documented; consolidation logic opaque; no audit log for what was pruned/merged; only Claude Code (not Claude.ai web).

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.

Rows last verified 2026-05-14 / 2026-05-14. Data is CC-BY-4.0 — see how to read this.