[BUG] Usage extremely high after 5-10 minutes into planning a feature
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?
When planning a feature and getting started for the day, I was not more than 5-10 minutes into my session and I checked usage (which has repeatedly been suspiciously low during mornings for me recently) and it was 51%! This is not normal usage. I have been using Claude Code for months and never experienced this. It started about a week or two ago.
<img width="875" height="212" alt="Image" src="https://github.com/user-attachments/assets/27af6cc1-8e1a-4ee6-bf43-2203dfb963b9" />
<img width="474" height="406" alt="Image" src="https://github.com/user-attachments/assets/0bb8557b-5955-4484-9452-c07ec9737cf8" />
What Should Happen?
Usage for 5-10 minutes of actual use (the additional time was me starting a new session to track usage and ask claude how to file this issue report, etc.) for what I was doing would normally be around 2% instead of 51%. I am a fairly long-running Claude Max subscriber.
Error Messages/Logs
Steps to Reproduce
I am not sure how to reproduce it, but I did see that Lydia Hallie on X acknowledged this issue and said a fix is being worked on, which I appreciate as a user, but what will happen to all the lost usage? My work depends on this normally outstanding service. I lost billable hours several days in the last weeks due to instantly hitting usage limits.
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.87 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
I had to stop ideating the features I was planning for a presentation to a large client next week due to fears of hitting usage limits and not being able to tackle other more pressing work that could come up. I think you guys are already working on a fix, I get it. I just hope there will be some recompense.
This issue has 10 comments on GitHub. Read the full discussion on GitHub ↗