StackMap
Subscribe
Explore / claude-mem
thedotmack

claude-mem

Cross-harness session memory: hooks capture what the agent does, an LLM compresses it into observations, and the next session gets the relevant ones back via progressive-disclosure MCP tools.

92,509 8,129 JavaScript Apache-2.0updated 2 days ago
View on GitHubDispute this mapping →
Curator's take

The most widely installed of the capture-and-reinject memory plugins, and the one with the most product around it: 5 lifecycle hooks, a Bun worker with an HTTP API and live web viewer, SQLite plus FTS5 plus Chroma for hybrid search, and a 3-layer MCP search pattern (index → timeline → full detail) that keeps recall at ~50-100 tokens per hit until you actually want the body. Installs into Claude Code, OpenCode, Antigravity, OpenClaw and more, with `<private>` tags to keep things out of the store and optional cloud sync. The tradeoffs: it spends model tokens summarizing every session, it drags in Bun and uv, and what you get back is a generated observation rather than the raw transcript — if you want auditable, greppable memory you can edit by hand, look at the Markdown-first options instead.

Mapped by ShipWithAI editors · links verified

Continue your stack

What teams reach for next — and why each earns a place beside claude-mem. Ranked by curator confidence.