claude-mem crossed 80K stars. Persistent memory across 28+ agent runtimes from one install

claude-mem hit 80,189 stars at v12.6.4, with 1,840 commits and 109 contributors. It hooks five agent lifecycle events to capture observations, compresses them through Claude's agent SDK into SQLite, and reinjects relevant context on new sessions. No manual tagging. One npx command. It works across Claude Code, OpenClaw, Codex, Gemini, Hermes, and Copilot (GitHub).

This closes the arc. Cheaper models and compressed context only pay off if your agent stops re-paying to relearn what it already knew last session. Every fresh session that re-discovers your repo structure, your conventions, your past decisions is tokenmaxxing in slow motion. Memory is the third leg of the cost-discipline stool, after cheaper inference and tighter context.

I'll be honest about where I'm uncertain. I haven't run claude-mem long enough on a real project to know if the auto-captured memory stays useful or slowly fills with noise. Persistent memory has a known failure mode: it accumulates stale and contradictory facts, and then reinjection actively hurts you by feeding the model wrong context with confidence. The arXiv crowd is already on this. One paper today proposes tracking behavioral drift through edits to skill and memory files (arXiv). Another, MemMorph, shows you can hijack tool selection 85.9% of the time by poisoning just three memory records (arXiv). So memory is both the cost fix and a fresh attack surface.

What I'd do: adopt persistent memory, but treat the memory store as code, not as a black box. Read what it captures. Prune aggressively. Version it. If an agent's behavior shifts and you can't explain why, the memory file is the first place to look. The convenience of zero-tagging memory is real, but "I don't know what's in my agent's head" is not a state you want in production.