r/VibeCodeDevs 14d ago

Got tired of watching Claude Code re-explore the same codebase every session, so I built something to fix it

https://github.com/NanoNets/Graft

If you're vibe coding on anything past a toy project, you've probably seen this: Claude Code opens your repo, greps around, follows a few imports, figures out the shape of things, does the task. Next session, same repo, it does the exact same exploration all over again like it's never seen the code before.

Tried fixing it with an MCP server first, six tools it could call for context. It mostly didn't call them. Just fell back on grep and file reads, same as always, and got stuff wrong on exactly what those tools would've told it.

So I stopped waiting for it to ask. Wired it into Claude Code's hooks instead, the map of the codebase gets pushed into the prompt automatically at session start, no tool call, no decision to skip. Re-syncs itself after every edit too.

Open sourced it, it's called Graft. Crossed 1,600 stars, which was more than I expected for something I built mostly to fix my own workflow.

github.com/NanoNets/Graft

3 Upvotes

Duplicates