[BUG] API Rate limit even if I just started the session with available quota

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?

Environment:

• OS: Windows
• Claude Code version: 2.1.76
• Plan: Pro
• Model at time of issue: Opus

What happened:
Every request immediately returned "API Error: Rate limit reached" despite only 11% usage shown. Even claude logout returned the same error.

I tried the following without success:

• Deleting credentials.json and re-logging in
• Running /status (showed normal usage)

Workaround found:
Switching to Sonnet, sending one message, then switching back to Opus resolved the issue. This suggests the rate limit error is Opus-specific and not account-wide — but the error message gives no indication of this, making it very hard to diagnose.

Suggested improvements:

1. The error message should specify which model is rate-limited (e.g. "Opus rate limit reached, try Sonnet")
2. claude logout should never require an API call that can be rate-limited
3. The usage dashboard should show per-model quota, not just a single global percentage

Hope this helps. Happy to provide logs if needed.

What Should Happen?

Use my credits at the start of the session

Error Messages/Logs

API Error: Rate limit reached

Steps to Reproduce

I could not tell

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.76

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Windows Terminal

Additional Information

_No response_