ai-memory vs memsearch
Rust 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. — versus — Zilliz'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.
Same '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.
| ai-memory | memsearch | |
|---|---|---|
| Stars | 4.3k | 2.5k |
| Forks | 314 | 233 |
| Language | Rust | Python |
| License | MIT | MIT |
| Last activity | today | yesterday |
| Topics | memory, coding | memory, coding |
| Curated connections | 6 | 8 |
ai-memory — the curator's take
The strongest bet if you genuinely switch harnesses mid-task: hook and MCP installers for roughly fifteen CLIs, a portable event ledger, `ai-memory run <harness>` for managed cross-vendor resume, and one Rust binary you can systemd. You pay for that reach in surface area — per-harness caveats matter (several CLIs discard SessionStart stdout, so handoffs come back through MCP `memory_handoff_accept`; Codex and Kiro need an explicit `finalize-session`), and you configure capture exclusions plus LLM and embedding providers. If you live in exactly one harness, a single-harness plugin gets you 80% of this with a tenth of the setup.
memsearch — the curator's take
The cross-platform play is the point: a conversation in Claude Code becomes searchable context in Codex, OpenCode and OpenClaw — one memory, four plugins, zero per-agent setup. Memories live in readable Markdown (greppable, versionable) with Milvus doing hybrid search, and the standout feature is procedural: it watches for workflows you repeat and distills them into installable skills, maintained in the background. NOT for single-agent loyalists — if you only run Claude Code, opencode-mem-style plugins are lighter — and it's a Zilliz project: the Milvus dependency is also the funnel; check what 'backed by Milvus' costs you operationally before teams adopt.