claude-mem
you only use Claude Code, want zero cost, and are happy with basic session-to-session context continuity.
← all comparisons
compare ·claude-mem vs. 3ngram
if you only use Claude Code, claude-mem is a solid free first step.
the moment you move between Claude, ChatGPT, or Cursor, it stops working — 3ngram keeps project memory, decisions, commitments, blockers, and source context available wherever the work continues.
at a glance ·7 capabilities
claude-mem vs. 3ngram, side by side.
| capability | 3ngram | claude-mem |
|---|---|---|
| what it is | shared memory and follow-through for AI work | open-source Claude Code plugin |
| memory model | typed — decisions, commitments, blockers, patterns | flat, untyped observations |
| capture method | intentional + autoyou control what matters | auto-captures everything via lifecycle hooks |
| follow-through | overdue tracking, stale commitments, blocker surfacing | none |
| works in | any MCP client (Claude, ChatGPT, Cursor, Codex) | Claude Code only |
| storage | cloud-synced across devices | local SQLite + ChromaDB |
| web dashboard | yes | no |
3ngram
you want your AI work carried forward across tools — decisions, commitments, blockers, reusable workflows, and source context included — instead of trapped in one Claude Code setup.
claude-mem captures. 3ngram structures the work and follows through.
The two can coexist during a transition.