Free tool: https://grape-root.vercel.app/ Recently I stopped using Cursor and moved back to Claude Code. One thing Cursor does well is context management. But during longer sessions I noticed it leans heavily on thinking models, which can burn through tokens pretty fast. While experimenting with Claude Code directly, I realized something interesting: most of my token usage wasn’t coming from reasoning. It was coming from Claude repeatedly 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 persistent project memory for Claude Code. The idea is simple: Instead of forcing the model to rediscover the same repo context 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 After testing it during a few coding sessions, token usage dropped ~50–70% for me. My $20 Claude Code plan suddenly lasts 2–3× longer , which honestly feels closer to using Claude Max. Early stats (very small but interesting): ~800 visitors in the first 48 hours 25+ people already set it up some devs reporting longer Claude sessions Still very early and I’m experimenting with different approaches. Curious if others here have noticed that token burn often comes more from repo re-scanning than actual reasoning . Would love feedback. submitted by /u/intellinker
Originally posted by u/intellinker on r/ClaudeCode
You must log in or # to comment.