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 switchOpposite entry point: deja-vu retro-indexes session logs your harnesses already wrote — no hooks, no embeddings, months of history instantly — while ai-memory installs hooks to capture and summarize from here on.
Full comparison → claude-memCross-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.
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 → memantoCompanion memory agent for 20+ coding agents, built on Moorcheh — its own information-theoretic engine, no third-party vector DB to manage. Runs local (Docker + Ollama, keyless) or on their cloud.
Why switchBoth give coding agents cross-session memory with nothing to write by hand: deja-vu retro-indexes the logs your harnesses already produced (no hooks, no embeddings, months instantly), memanto runs its own retrieval engine over captured context. Instant history vs richer recall.
Full comparison → memsearchZilliz's unified memory for coding agents: one Markdown + Milvus store shared across Claude Code, Codex, OpenCode and OpenClaw — hybrid search, plus repeated workflows distilled into skills.
Why switchUnified memory across coding agents, opposite bets: memsearch curates a Markdown+Milvus store going forward; deja mines the raw session logs you already have, no embeddings at all.
Full comparison → hivemindActiveloop's shared brain for agent TEAMS: traces from Claude Code, Codex, Cursor & co become reusable skills every teammate's agent can execute — cloud-backed, 25% cheaper on LoCoMo.
Why switchBoth mine the session histories your coding agents already wrote; deja-vu serves personal retroactive recall over MCP, hivemind turns team traces into skills every teammate's agent can run.
Full comparison → agentmemoryPersistent memory for coding agents on the iii engine: MCP server with 53 tools, 12 auto-capture hooks, hybrid search + knowledge graph, zero external DBs. Claims 95% R@5 and 92% token cuts.
Why switchBoth serve coding-agent memory over MCP. agentmemory is a 53-tool capture-everything suite; deja is one binary that only indexes and recalls — pick by how much machinery you want.
Full comparison →