[BUG] Rate limit blocks all commands including /status after upgrading to Max plan
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?
What's Wrong?
After upgrading to Max plan, Claude Code blocks every command — including /status and claude logout — showing "You've hit your limit · resets 11am (Europe/Madrid)" on every single input. The upgrade to Max should have reset or increased the usage limit, but the block persists for all commands.
Steps to Reproduce:
Had an active usage limit on a previous plan
Upgraded to Max plan
Opened a new terminal session
Every command returns: You've hit your limit · resets 11am (Europe/Madrid)
Expected behavior:
Max plan upgrade should reset or increase usage limits. At minimum, commands like /status should work to check actual usage.
Actual behavior:
All commands blocked, including diagnostic ones. Cannot check real usage percentage.
Environment:
Plan: Max (recently upgraded)
Timezone: Europe/Madrid
Claude Code: latest version
What Should Happen?
Max plan upgrade should reset or increase usage limits. Diagnostic commands like /status should always work regardless of usage limits.
Error Messages/Logs
You've hit your limit · resets 11am (Europe/Madrid)
Steps to Reproduce
- Hit usage limit on previous plan
- Upgraded to Max plan
- Opened new terminal session
- Every command returns: "You've hit your limit · resets 11am (Europe/Madrid)"
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
Claude Code v2.1.71
Platform
Other
Operating System
Windows
Terminal/Shell
Other
Additional Information
Command Prompt (Windows CMD)
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗