Graphicle vs claude-mem: session memory, plus the code graph.
claude-mem gives Claude Code a memory of past sessions. Graphicle's session capture follows its design, and adds a code graph, your docs and reviewed decisions.
Checked against claude-mem's own pages on 27 October 2026
Side by side
claude-mem and Graphicle.
claude-mem, by Alex Newman, is an open-source Claude Code plugin: hooks capture each session, a model compresses it into observations, and later sessions search them.
| claude-mem | Graphicle | |
|---|---|---|
| Session capture | Hooks; a model compresses each session | Hooks for Claude Code and Codex; turns kept word for word |
| Model needed | Yes: its hosted observer, your key or your Anthropic plan | Only to propose memories; local models work |
| Remembers | Sessions, observations and summaries | Sessions, docs, reviewed decisions and the code graph |
| Storage | SQLite and Chroma; optional cloud backup | One SQLite file |
| Licence | Apache-2.0 | Apache-2.0 |
We have not run Graphicle and claude-mem on the same tasks.
Which one fits
Which one fits.
Choose claude-mem if
- You only want session memory for Claude Code, as a plugin.
Choose Graphicle if
- You want sessions, docs, decisions and the code graph in one place.
- You want sessions captured without a model.
Graphicle's session capture follows claude-mem's session-capture and work-state designs (Apache-2.0), credited in NOTICE.
Checked on 27 October 2026. Product names are trademarks of their owners; no affiliation or endorsement is implied.