claude-mem vs graphicle
Cross-harness session memory: hooks capture what the agent does, an LLM compresses it into observations, and the next session gets the relevant ones back via progressive-disclosure MCP tools. — versus — One Rust program giving coding agents a code graph plus memory of docs, decisions and past sessions, served over MCP to Claude Code, Codex, Cursor and VS Code.
For the memory half: both remember past agent sessions. claude-mem compresses observations; Graphicle ties them to the code graph.
| claude-mem | graphicle | |
|---|---|---|
| Stars | 113k | 509 |
| Forks | 9.8k | 36 |
| Language | JavaScript | Rust |
| License | Apache-2.0 | Apache-2.0 |
| Last activity | yesterday | yesterday |
| Topics | memory, coding | code-intel, memory |
| Curated connections | 12 | 5 |
claude-mem — the curator's take
The most widely installed of the capture-and-reinject memory plugins, and the one with the most product around it: 5 lifecycle hooks, a Bun worker with an HTTP API and live web viewer, SQLite plus FTS5 plus Chroma for hybrid search, and a 3-layer MCP search pattern (index → timeline → full detail) that keeps recall at ~50-100 tokens per hit until you actually want the body. Installs into Claude Code, OpenCode, Antigravity, OpenClaw and more, with `<private>` tags to keep things out of the store and optional cloud sync. The tradeoffs: it spends model tokens summarizing every session, it drags in Bun and uv, and what you get back is a generated observation rather than the raw transcript — if you want auditable, greppable memory you can edit by hand, look at the Markdown-first options instead.
graphicle — the curator's take
Use it when you want code intelligence and project memory from one local install instead of a code-graph MCP plus a separate memory server. Skip it if you already run a dedicated code graph you like, or need team-shared memory. Its memory comparison against seven systems is pre-release and self-reported.