[BUG] Persistent massive token drain on Max 20x Plan (Weekly limit exhausting in 1 day)
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
I am reporting a critical and persistent bug regarding token consumption via the VS Code extension. I am on the Max 20x plan, but for a long time now, my entire weekly limit gets exhausted in just a single day with very minimal coding work.
This is not a one-time glitch; it has been happening continuously. It seems the extension is either caching context incorrectly, constantly re-reading the entire workspace in the background, or miscalculating token usage entirely.
I already tried reaching out to standard customer support but only received an automated AI reply from "Fin" stating that limits cannot be reset. As a premium developer paying for the Max 20x tier, this makes the tool completely unusable for me.
What Should Happen?
The token usage should strictly reflect actual generation and direct user prompts. A 20x weekly limit should absolutely not drain in one day of light work.
The extension's background context reading needs to be optimized or fixed so that it doesn't blindly consume limits without explicit user requests. I expect the engineering team to look into my account's usage logs, identify this token leak, and fix the underlying caching/syncing issue so I can actually use the plan I paid for.
Error Messages/Logs
Steps to Reproduce
- Use the Claude extension in VS Code with a Max 20x account.
- Perform normal, lightweight coding tasks (no massive codebase generations).
- Observe the usage limit hit 100% within a few hours or a single day.
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
opus 4.8
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗