Head to head
claude-mem vs graphify
claude-mem and graphify solve the same job (Memory & context), so this is a pick-one decision. claude-mem is our default here: Runs with no intervention after install, which is why it beats a manual notes file. Content wrapped in <private> tags is excluded from storage.
Quick read
- Editor's pick: claude-mem.
| Field | claude-memgithub.com Not yet swept | graphifygithub.com Not yet swept |
|---|---|---|
| What it is | Captures what the agent does via hooks, compresses events into semantic summaries, stores them in SQLite with FTS5 plus a Chroma vector DB, and injects the relevant slice into future sessions. Progressive disclosure: search returns a ~50–100 token index before you fetch detail. ~91k stars. | Turns a mixed corpus — code, docs, SQL schemas, configs, PDFs, images — into a queryable knowledge graph. Code extraction is deterministic and local; only prose and images route through Claude. Every edge is labeled EXTRACTED, INFERRED or AMBIGUOUS. Outputs graph.json, an interactive HTML visualization, a report and an Obsidian vault. ~107k stars. |
| Category | Memory & context | Memory & context |
| Cost tier | free | free |
| Pricing | Free · Apache-2.0 | Free |
| Why builders pick it | Runs with no intervention after install, which is why it beats a manual notes file. Content wrapped in <private> tags is excluded from storage. | The mixed-corpus part is your project angle — it will ingest editorial PDFs, style guides and back-issue docs alongside the code, not just source files. The --wiki export produces agent-navigable markdown grouped by concept. |
| Watch out for | not logged | not logged |
| How to wire it up | npx claude-mem install | uv tool install graphifyy |
| Editor's pick | Yes | No |
Other matchups worth running
Agent endpoint: GET /api/public/compare?slugs=claude-mem,graphify