[BUG] 'Usage limit reached' displayed when extra usage is available
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?
Business account with Premium tier. I have sufficient extra usage allocated on my account to cover intended usage, but my sessions are being blocked with 'Usage limit reached - resets at 6:00pm' which is when my weekly usage of plan tokens will reset.
<img width="870" height="238" alt="Image" src="https://github.com/user-attachments/assets/1d0f7734-3405-4b08-828a-df3175c19f31" />
Plan usage shows Weekly - all models at 100%, resets in 6h. The Claude desktop app blocks any interaction with the session despite having allocation remaining.
<img width="903" height="224" alt="Image" src="https://github.com/user-attachments/assets/c2e9b6a5-11b5-4744-a341-fef49126140f" />
<img width="918" height="82" alt="Image" src="https://github.com/user-attachments/assets/3e6f74b1-1c49-42da-8863-25db803f0bce" />
I believe this is a bug where the Claude UI is using the token limits from the Premium plan to gate access to the sessions, rather than the extra usage capability.
What Should Happen?
After usage has been depleated from the premium plan, the UI should switch to extra usage and not block access to the thread.
Error Messages/Logs
Steps to Reproduce
- Be on Premium business plan
- Have extra usage enabled and funded
- Use up weekly allowance
- See that threads are blocked pending the counter reset, despite balance existing
The same applies on Web sessions or Cloud sessions accessed through Claude Desktop
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
latest (i'm blocked from entering commands to check!)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗