Free tool: https://grape-root.vercel.app/ While experimenting, I noticed something interesting: most of my token usage wasn’t coming from reasoning, it was coming from Claude re-scanning the same parts of the repo on follow-up prompts . Same files. Same context. New tokens burned every turn. So I built a small MCP tool called GrapeRoot to experiment with better context/state management for Claude Code. The idea is simple: instead of rediscovering the repo every prompt, keep lightweight project state across turns. Right now it: tracks which files were already explored avoids re-reading unchanged files auto-compacts context between turns shows live token usage In my tests and user’s experience, token usage dropped roughly 50–70% , which made my $20 Claude Code plan last 2–3× longer . That’s why I jokingly say: you might not need the $100 plan — two $20 plans could already be enough. Some early stats (small but interesting): ~800 visitors in 48 hours 25+ people already set it up a few devs reporting longer Claude sessions Still early and I’m experimenting with different approaches. Curious if others here also feel that token burn mostly comes from repo re-scanning rather than reasoning . submitted by /u/intellinker
Originally posted by u/intellinker on r/ClaudeCode