Head to head
planning-with-files vs codegraph
planning-with-files and codegraph solve the same job (Memory & context), so this is a pick-one decision. planning-with-files is our default here: The fix for the single most annoying failure mode: Claude forgetting the design decisions you made two sessions ago and re-inventing the component. Deterministic completion gate means half-finished refactors do not get abandoned.
Quick read
- Editor's pick: planning-with-files.
| Field | planning-with-filesgithub.com Not yet swept | codegraphgithub.com Not yet swept |
|---|---|---|
| What it is | Makes the agent externalize its plan to disk (task_plan.md, findings.md, progress.md) so it survives /clear, compaction and crashes. Five lifecycle hooks re-read and re-inject the plan on session start and before major decisions. A Stop hook blocks termination until every phase is done. | Parses the repo with a Rust/tree-sitter kernel into a local SQLite graph of symbols, call edges and imports, served to agents over MCP — so the agent asks one structured question instead of grepping dozens of files. 100% local. Benchmarked at 88% fewer tool calls and 62% fewer tokens. ~67k stars. |
| Category | Memory & context | Memory & context |
| Cost tier | free | free |
| Pricing | Free · MIT | Free · MIT |
| Why builders pick it | The fix for the single most annoying failure mode: Claude forgetting the design decisions you made two sessions ago and re-inventing the component. Deterministic completion gate means half-finished refactors do not get abandoned. | Pays off once the codebase is big enough that Claude spends its first ten tool calls just finding things. Auto-syncs via OS file watchers, so no manual reindexing. |
| Watch out for | not logged | not logged |
| How to wire it up | npx skills add OthmanAdi/planning-with-files -g | npm i -g @colbymchenry/codegraph |
| Editor's pick | Yes | No |
Other matchups worth running
Agent endpoint: GET /api/public/compare?slugs=codegraph,planning-with-files