The same as a lot of people, my 5 hour token usage went from never being hit to being burnt up in an hour this weekend, and persists with the new version of CC. What I did notice this morning though was my jest test runs were taking a long time, and reported 37,000 tests passing instead of closer to 4000. Turns out because of my config, jest was running all the tests in all of the worktrees being created under .claude in my project folder. I’ve not seen these worktrees before, and I had 8 stale copies of my project. I asked Claude and got this answer: ❯ We’ve been burning more tokens than usual. Would these stale worktree folders have an impact? ⏺ Yes, absolutely. Every tool call that scans the repo — Grep, Glob, file reads with relative patterns — would have been searching through 8 full copies of the codebase sitting in .claude/worktrees/. That’s 8x the content being indexed, searched, and returned in results, which means 8x the tokens consumed for those operations. The .gitignore entry helps with git commands, but the Grep/Glob tools may still traverse those directories unless they respect gitignore. The best defense is what we just did — cleaning up stale worktrees and preventing future accumulation. I’m going to see how token burn is with these worktrees cleaned up. I think native git worktree support is a recent change? submitted by /u/marcusr_uk
Originally posted by u/marcusr_uk on r/ClaudeCode
You must log in or # to comment.