[BUG] Opus usage limit confusing
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?
Title: Opus 4.6 permanently rate limited on Pro subscription - 5 days and counting
Claude Code version: 2.1.87
Platform: Windows 11
Description:
For the past 5 days I have been unable to use Claude Opus 4.6 in Claude Code from terminal. Every request returns "API Error: Rate
limit reached" immediately. Sonnet 4.6 works fine in the same session. The usage meter shows significant weekly budget
remaining. I can also use opus 4.6 from console, but when i try using it in terminal it gives me the error.
Expected behavior:
Opus 4.6 should be available on a Pro subscription. Sonnet 4.6 works without issue.
What I've tried:
- Restarting Claude Code
- Waiting multiple days (5 days total, no recovery)
- Confirmed Sonnet 4.6 works normally
- Confirmed Opus works in claude.ai web console
Notes:
The issue appears to be Opus-specific and persistent, not a temporary burst limit. Weekly reset (Monday) did not
restore access.
What Should Happen?
I should be able to use opus 4.6 in my terminal as before I did.
Error Messages/Logs
⎿ API Error: Rate limit reached
Steps to Reproduce
To reproduce:
- Open Claude Code terminal
- Switch model to Opus 4.6 (/model)
- Send any message
- Immediately receive: "API Error: Rate limit reached"
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.87
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
I downgraded my plan from max to pro a week ago. This started to happen after that. But its still strange as I did almost nothing that week and I can not use opus from terminal. Many of my tools use opus from terminal and thus are not usable anymore for me. This is critical issue for me.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗