[BUG] /usage command fails with rate_limit_error when checking usage data
Status Open
Reported on v2.1.71
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 9 comments · opened Mar 9, 2026
What's Wrong?
When running the /usage command to check current usage and limits in Claude Code, the UI displays an error:
Error: Failed to load usage data: {"error":{"message":"Rate limited. Please try again later.","type":"rate_limit_error"}}The /usage dialog opens but immediately fails to load any data, making it impossible to monitor current token usage or remaining quota.
What Should Happen?
The /usage dialog should successfully load and display current session usage statistics, token consumption, and remaining quota without being rate limited by the usage data endpoint itself.
Steps to Reproduce
- Open Claude Code in an active session
- Type
/usageand press Enter - Observe the error: "Error: Failed to load usage data: rate_limit_error"
Additional Context
This appears related to #31637 where the /api/oauth/usage endpoint aggressively rate limits usage monitoring requests. The error occurs on the Anthropic Max plan.
Environment
- Claude Code version: 2.1.71 (Claude Code)
- OS: Windows 10 Pro (Build 19045)
- Terminal: Windows Terminal 1.23.20211.0
- Platform: Anthropic Max
9 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Still reproducing on v2.1.83. Root cause traced in #31637.
Triggered via /status → Usage tab, same error:
Error: Failed to load usage data: {"error":{"type":"rate_limit_error","message":"Rate limited. Please try again later."}}
Status and Config tabs load fine. /usage command also fails the same way. Conversations and model inference are completely unaffected — only the usage data endpoint is rate-limited.
Per the analysis in #31637, the root cause is overly aggressive rate limiting on the /api/oauth/usage endpoint — approximately 5 requests per access token before returning 429, with no recovery and no Retry-After header. This effectively makes Claude
Code's built-in usage monitoring unusable under normal use.
This issue is marked as stale, but the problem clearly persists. Would appreciate some attention from the team — even a more generous rate limit on the usage endpoint or more aggressive client-side caching would resolve this.
Same issue here.
Experiencing same issue. v2.1.104
Same issue with the v2.1.104
Occurs with CLI v2.1.107.
Occurs with CLI v2.1.109.
Might be related to general Claude errors
Same with CLI v2.1.150
As a workaround, doing
/logoutand/loginreset the rate limit for my OAuth session token, allowing me to use the endpoint again.