[BUG] API Error / Usage exhausted when I just started and have plenty of usage left.
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?
I have only asked one medical question on Claude chat, then an hour later I open claude code to work on a project. First prompt and it says "API Error: Server is temporarily limiting requests (not your usage limit) · Rate limited"
Below it says "usage limit reached"
I go to the next project, enter a prompt and it responds. A few seconds later it also says Usage limit reached"
With those two prompts I was able to enter simple questions, instant answers and it used 27% of my current session usage. I have only used 21% of my weekly limits. And Claude code says I have hit my limit. Help says I have hit my organizational limit.
Usage this week was quickly exhausted after my month reset. Even when using lower models. Not the usage I was able to get with higher models.
What Should Happen?
Be able to use the program without hitting limits until I actually hit limits. Not use a quarter of my session usage with 2 simple questions and answers.
Error Messages/Logs
API Error: Server is temporarily limiting requests (not your usage limit) · Rate limited
Usage Limit Reached
Steps to Reproduce
Try to use Claude
Claude Model
Not sure / Multiple models
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
Claude 1.3109.0 (35cbf6) 2026-04-16T20:32:01.000Z
Platform
Other
Operating System
Windows
Terminal/Shell
Terminal.app (macOS)
Additional Information
<img width="1391" height="762" alt="Image" src="https://github.com/user-attachments/assets/5aea7ede-9331-4176-b41c-281e51d6e179" />
<img width="1255" height="496" alt="Image" src="https://github.com/user-attachments/assets/ba47d00b-fdeb-46f0-a80a-f72018d29c82" />
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗