memsearch vs okf-agent-memory
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 — Git-native agent memory on Google's OKF v0.2: Markdown+YAML concepts in knowledge/, a zero-dep Go CLI/MCP with <300µs BM25 search, provenance and trust tiers.
memsearch also stores memory as Markdown but retrieves through Milvus embeddings; OKF stays lexical (BM25) and dependency-free, trading semantic recall for zero infra and zero API cost.
| memsearch | okf-agent-memory | |
|---|---|---|
| Stars | 2.6k | 542 |
| Forks | 244 | 33 |
| Language | Python | Go |
| License | MIT | MIT |
| Last activity | yesterday | yesterday |
| Topics | memory, coding | memory, coding, knowledge-graphs |
| Curated connections | 10 | 5 |
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.
okf-agent-memory — the curator's take
Pick this when you want agent memory you can `git diff` and code-review: every concept is a Markdown file with provenance, trust tier and staleness metadata, and progressive-disclosure indexes keep loads small. It is lexical-only (BM25) by design — no embeddings, no API cost — so it wins on decisions, constraints and glossary-style facts, not on fuzzy semantic recall of past conversations. Skip it if you want automatic session capture (it is search-before-write, human/agent-authored) or memory shared across many repos; it is per-project and lives in the repo.