Claude Code Opus Fails with Rate Limit Error Despite Available Weekly Capacity

Issue Details

A Claude Max subscriber encountered a rate limiting issue when switching to Claude Opus in Claude Code after hitting their Sonnet weekly limit. Despite having 97% of their weekly "All models" capacity available, every request to Opus in Claude Code returns: API Error: Rate limit reached.

The user's usage dashboard showed:

• All models weekly: 3% used
• Sonnet only weekly: 100% used
• Current session: 46% used

Technical Context

The user was using Claude Code v2.1.74 with the model correctly set to claude-opus-4-6 via the /model command. They confirmed via /status that they were logged in as a "Claude Max Account" rather than using the Claude API or Console billing path.

Debugging Attempts

The user tried:

• /logout and /login to re-authenticate
• Multiple attempts with the same error each time
• Confirmed Opus works normally on claude.ai from the same account simultaneously

Support Response

Anthropic's AI support chatbot "Fin" stated this was "working as designed," explaining that hitting Sonnet's 100% limit affects access to other models like Opus for "fair resource distribution." The chatbot did not provide documentation for this policy and did not escalate to human support when requested.

Contradictions Noted

The user identified several inconsistencies:

• The dashboard shows separate limits for Sonnet and "All Models," implying independent tracking
• Opus works on claude.ai from the same account at the same time
• No documentation exists stating that hitting one model's cap blocks other models
• The "All models" metric showing 3% usage doesn't reflect actual availability

Potential Causes

The user suggests three possible explanations:

• A hidden per-model or per-interface throttle not surfaced in the dashboard
• A rate limiter bug specific to Claude Code
• Inaccurate dashboard information