[BUG] /usage and /status return 429 rate limit after single request
Resolved 💬 4 comments Opened Mar 5, 2026 by Marcel-Bich Closed Mar 5, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report
- [x] I am using the latest version of Claude Code
What's Wrong?
The /usage command returns a rate limit error after a single successful request. Steps to reproduce:
- Open Claude Code (v2.1.69)
- Run
/statusand navigate to Usage - works fine, data loads - Immediately run
/usageagain - fails with rate limit error - All subsequent
/statusor/usagecalls also fail with the same error
Error message:
Error: Failed to load usage data: {"error":{"message":"Rate limited. Please try again later.","type":"rate_limit_error"}}
The rate limit on the usage endpoint appears to be extremely aggressive - a single request seems to exhaust the allowed quota, and subsequent requests fail even after waiting.
What Should Happen?
/usage and /status should be usable multiple times during a session without hitting rate limits. The usage endpoint should allow at least a few requests per minute for normal interactive use.
Additional Context
- Plan: Max
- OS: Ubuntu 24.04 (Wayland/GNOME)
- Claude Code version: 2.1.69
- claude.ai website shows usage data without issues, only the CLI endpoint is affected
- This started around March 2-3, 2026, coinciding with the Anthropic Usage Reporting outage (see status.claude.com history)
- The outage is marked as "resolved" but the aggressive rate limiting on the usage endpoint persists
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗