engrim vs memsearch
Local SQLite episodic memory shared across Antigravity, Claude Code, Cursor, Windsurf and Codex: hooks/MCP capture decisions, FTS5+model2vec hybrid recall reloads ~1k tokens per session. — 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.
Both aim at one memory shared across Claude Code, Codex and friends; memsearch needs Milvus for retrieval, engrim is a dependency-free SQLite file.
| engrim | memsearch | |
|---|---|---|
| Stars | 222 | 2.6k |
| Forks | 12 | 244 |
| Language | Python | Python |
| License | MIT | MIT |
| Last activity | yesterday | yesterday |
| Topics | memory, coding | memory, coding |
| Curated connections | 5 | 10 |
engrim — the curator's take
Use it when you actually switch harnesses mid-project — Gemini in Antigravity in the morning, Claude Code in the afternoon — and want one memory both write to and read from, with `origin_agent` provenance on every entry. `engrim setup` auto-wires hooks, MCP and status lines for whatever it finds under ~/. The retrieval is cheap and offline (FTS5 + static model2vec embeddings, no API), and the deliberate 4k-char 'memory pack' cap keeps it from becoming a second context window. Don't pick it for cross-project or team memory (it is per-project, per-machine), or if you want raw transcript capture rather than curated decisions/facts/feedback. Small project (~200 stars, one maintainer) — expect rough edges.
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.