Free Tool link: https://grape-root.vercel.app/ One thing that kept bothering me while using Claude Code was that every follow-up prompt often feels like a cold start . The model re-explores the same repo files again, which burns a lot of tokens even when nothing has changed. So I started experimenting with a small MCP tool called GrapeRoot to make sessions behave almost stateful . The idea is simple: keep track of which files the agent already explored remember which files were edited or queried avoid re-reading unchanged files repeatedly route the model back to relevant files instead of scanning the repo again Under the hood it maintains a lightweight repo graph + session graph , so follow-up prompts don’t need to rediscover the same context. In longer coding sessions this reduced token usage ~50–70% for people using it almost 80+ people with average 4.1/5 feedback , which basically means the $20 Claude plan lasts much longer . Still early and experimenting, but a few people have already tried it and shared feedback. Curious if others using Claude Code have noticed how much token burn actually comes from re-reading repo context rather than reasoning. submitted by /u/intellinker
Originally posted by u/intellinker on r/ClaudeCode