memsearch vs opencode-mem
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. — versus — OpenCode 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.
Same 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.
| memsearch | opencode-mem | |
|---|---|---|
| Stars | 2.3k | 1.2k |
| Forks | 206 | 121 |
| Language | Python | TypeScript |
| License | MIT | — |
| Last activity | yesterday | today |
| Topics | memory, coding | memory, coding |
| Curated connections | 3 | 4 |
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.
opencode-mem — the curator's take
For OpenCode users tired of re-explaining their architecture every session: auto-capture summarizes each prompt's work via a background structured-output call that reuses your existing opencode provider auth, memories inject into the first chat message, and the `.opencode-mem-project` marker file solves multi-repo workspaces properly (directory-driven identity, not env vars). A real web UI at :4747 for browsing what it learned. NOT for Claude Code — this is OpenCode-specific; pro-workflow and claude-reflect are the equivalents on that side. Auto-capture needs a provider that speaks structured output, and the default local embedding model downloads on first use. Inspired by opencode-supermemory, but local-first.