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 are cross-harness memory companions for coding agents; memanto leans on its own information-theoretic retrieval engine with no vector DB to run, ai-memory on lifecycle-hook capture compiled into a shared wiki plus explicit vendor-to-vendor handoffs.
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 switchSame 'one memory shared by every coding CLI' pitch: memsearch keeps Markdown in Milvus and distills repeated workflows into skills, ai-memory keeps a sanitized observation wiki and optimizes for the moment you swap vendors mid-task.
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 are MCP-plus-hooks memory servers for coding agents. agentmemory maximizes tool surface (53 tools, hybrid search and a knowledge graph); ai-memory keeps the surface small and spends its complexity on multi-harness compatibility.
Full comparison → 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 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 → 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 switchopencode-mem is the single-harness version of this idea: one OpenCode plugin, local SQLite, almost no setup. ai-memory pays in configuration to span a dozen CLIs and carry context between them.
Full comparison →