If you burn through your Claude Code plan in a couple of days, this is why, and there is now a free fix.

The problem

Every time you open a new Claude Code session, Claude has to reread your entire codebase from zero. Every file, every line, every function. It has no memory of the last session, so it starts from nothing each time.

On a small project that is fine. On a real codebase it is brutal, and it is the single biggest reason people tear through their usage limits and start eyeing the more expensive plan.

What Graphify does

You run it once inside your project. It scans the whole codebase and builds a complete knowledge graph of what is in there, mapping every connection, every relationship, and how the pieces actually fit together.

After that, when you open a new session, Claude navigates the graph instead of rereading your files. It looks up what it needs rather than ingesting everything to find out.

What it saves

Around 70% less token consumption. For a lot of people that is the difference between needing the expensive plan and being perfectly fine on the cheaper one.

It is completely free and open source.

Why this approach makes sense

The fix is not a bigger context window, it is better retrieval. Reading an entire codebase to answer a question about one function was always the wrong shape. Indexing it once and looking things up is how every other developer tool has worked for decades.

Worth knowing: you will want to re-run it after major structural changes, since the graph reflects the codebase at the time you built it.

Most AI cost problems are not pricing problems. They are architecture problems, and this one had an obvious fix sitting there the whole time.

Run it once on your biggest repo. The difference shows up on the very next session you open.
– Anir

If this is the kind of AI thinking you want working on your own business, apply to work with me. And to catch the next breakdown, join the newsletter.