Free tool: https://grape-root.vercel.app/ While experimenting with Claude Code, 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 folders. 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 during sessions In my tests (and early users), token usage dropped ~50–70% , which basically made my $20 Claude Code plan last 2–3× longer and as a solo dev it is more than enough for me and i guess for you too!? That’s why I jokingly say: you might not need the $100 plan, $20 plans could already be enough. Some early stats (still small but interesting): ~1600+ visitors in 72 hours 50+ people already set it up Developers reporting noticeably longer Claude sessions with rating 4.2/5 Still very early and I’m experimenting with different approaches. Curious if others here notice the same pattern: Use this tool and provide your valuable feedback :) submitted by /u/intellinker
Originally posted by u/intellinker on r/ClaudeCode