engrim vs opencode-mem
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 — 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 local SQLite + vector recall for coding agents; opencode-mem is an OpenCode plugin, engrim targets Antigravity/Claude Code/Cursor/Codex via hooks and MCP.
| engrim | opencode-mem | |
|---|---|---|
| Stars | 222 | 1.6k |
| Forks | 12 | 154 |
| Language | Python | TypeScript |
| License | MIT | MIT |
| Last activity | yesterday | 4 days ago |
| Topics | memory, coding | memory, coding |
| Curated connections | 5 | 7 |
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.
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.