deja-vuIndexes the session histories your coding agents already wrote — 17 harnesses, months retroactive — and serves recall over MCP. 84.9% hit@1 on LongMemEval-S, no LLM, no embeddings. One Go binary.
Why switchBoth give a coding agent cross-session recall. Deja-vu is retroactive and free — it indexes the session logs 17 harnesses already wrote, no LLM, no embeddings, one Go binary. Claude-mem only knows sessions it captured, but pays an LLM per session to produce curated observations instead of raw history.
Full comparison → opencode-memOpenCode plugin giving coding agents persistent cross-session memory — local SQLite + vector search, automatic memory capture, user-profile learning, and a web UI. Nothing leaves your machine.
Why switchSame plugin-level memory pattern with automatic capture and local vector search, scoped to OpenCode only. Pick opencode-mem if that is your harness and you want something small; claude-mem spans many harnesses and ships a worker, viewer and MCP toolset.
Full comparison → ai-memoryRust long-term memory server for coding CLIs: lifecycle hooks capture sessions into a sanitized shared wiki, then hand a bounded summary to the next agent so Codex can resume what Claude Code started.
Why switchAlso hooks coding-CLI sessions into a long-term store, but written in Rust and shaped as a sanitized shared wiki rather than a per-session observation stream. Choose by artifact: readable wiki versus searchable observations.
Full comparison → EverOSOne portable memory layer for every agent: conversations, files and trajectories kept as canonical Markdown, indexed locally by SQLite and LanceDB, with offline reflection that refines them.
Why switchEveros keeps memory as canonical Markdown you can read, edit and git across any agent; claude-mem keeps it in SQLite + Chroma behind a worker API and web viewer. Portability and auditability versus search quality and automation.
Full comparison →