[BUG] Max plan: CLI stuck on 'API Error: Rate limit reached' with weekly usage at 91%
Resolved 💬 3 comments Opened Feb 19, 2026 by pavelbe Closed Feb 22, 2026
Preflight Checklist
- [x] I searched existing issues and found related reports (#25531, #26699, #21621), but this report adds a reproducible Max plan case with screenshots and a Claude feedback ID.
- [x] This is a single bug report.
- [x] I am using the latest available Claude Code version on my machine.
What Is Wrong?
Claude Code CLI returns API Error: Rate limit reached for every prompt for 5-6 hours continuously, even though usage UI shows weekly quota is not exhausted.
At approximately February 19, 2026, 09:53 MSK (06:53 UTC):
- Weekly usage: 91% used (~9% remaining)
- Current session: 0% used (new session)
- CLI still fails on every request with rate-limit error
This blocks all CLI work despite remaining weekly quota.
What Should Happen?
If weekly quota still has remaining capacity and current session usage is 0%, CLI requests should be accepted.
Error Messages and Logs
API Error: Rate limit reached
Steps to Reproduce
- Open Claude Code CLI (
claude) on Windows 11 + WSL Ubuntu. - Ensure Usage page shows:
- Weekly limits (All models): 91% used (not exhausted)
- Current session: 0% used
- Send any prompt in CLI (for example:
hi). - Observe immediate failure with
API Error: Rate limit reached. - Repeat after waiting; issue remains reproducible for 5-6 hours.
Environment
- Claude Code CLI version: 2.1.47
- OS: Windows 11 + WSL Ubuntu
- Plan: Claude Max (not API-key billing)
- Max tier: x20
- Repro date: February 19, 2026
Additional Context
- Claude feedback already submitted:
836a1742-0f17-4018-bdfa-3924ac5e0156 - Evidence screenshots:
- https://ibb.co/Vcsk7dX5
- https://ibb.co/V0wGnFSw
Please check possible desynchronization between Usage dashboard state and backend CLI rate limiter, and force a limiter/quota state refresh for affected accounts.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗