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 job — persistent cross-session memory for coding agents — different reach: opencode-mem goes deep on one host (OpenCode, local SQLite, nothing leaves the machine); memsearch spans four hosts with one shared Markdown+Milvus store.
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 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 → 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 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 → pro-workflowOne SQLite store under every Claude Code session: corrections become FTS5-searchable rules that auto-load, research grows persistent wikis, and 37 hook scripts add quality gates.
Why switchSame job on rival harnesses: a persistent local store under every coding-agent session. pro-workflow puts SQLite + FTS5 rules under Claude Code; opencode-mem puts SQLite + vector recall with auto-capture under OpenCode.
Full comparison → claude-reflectClaude Code plugin that learns from your corrections — hooks capture them in-session, /reflect syncs approved learnings to CLAUDE.md/AGENTS.md, /reflect-skills mines history into reusable commands.
Why switchBoth close the cross-session learning loop for coding agents: claude-reflect distills your corrections into CLAUDE.md via /reflect; opencode-mem auto-captures work into a searchable vector store and injects relevant memories per session.
Full comparison → MemMoltStructured long-term memory over MCP: an enforced bucket-thread-memo hierarchy in one SQLite file, hybrid FTS5 + vector search fused with RRF, local embeddings.
Why switchLocal SQLite+vector agent memory either way: opencode-mem auto-captures per-session for OpenCode; MemMolt is deliberate, structured recall for any MCP client.
Full comparison →