[BUG] Rate Limit Reached without typing anything, and /insights causes insane token usage
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 wanted to code in Claude Code CLI in my terminal on Windows. I was immediately met with "API Error: Rate limit reached". I tried debugging around, and I went to claude.ai's "Usage" page, and noticed no token usage for today and almost none for the week.
I then tried some commands, re-opening Claude Code, and nothing works. I tested /insights, which I believe then spiked up A TON of token usage on my account... causing 100% of my token usage within 20 seconds... Now I'm completely out of tokens, without having written A SINGLE LINE OF CODE.
This is a major bug, I tried writing to support, but was only able to get an AI bot to respond to me and said: "I understand you're requesting a refund or usage limit reset due to unexpected usage spikes in Claude Code CLI. Let me look up your account information to help resolve this issue." then it said: "We've determined that your purchase doesn't meet our refund eligibility criteria due to a previously issued refund.
If you have any other questions or need assistance with something else, please feel free to open a new request."
<img width="1100" height="1377" alt="Image" src="https://github.com/user-attachments/assets/61884902-8c00-4893-946c-3887024d540f" />
What Should Happen?
Write code and not steal my token usage for no reason.
Error Messages/Logs
API Error: Rate limit reached
Steps to Reproduce
- Type in Claude Code
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
2.1.86 (Claude Code)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
This issue has 13 comments on GitHub. Read the full discussion on GitHub ↗