[BUG] Bug: Extra Usage charged despite available plan capacity + false rate limit errors in Claude Code
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?
Subject: Bug: Extra Usage charged despite available plan capacity + false rate limit errors in Claude Code
Hi Anthropic Support,
I'm experiencing a bug with Claude Code on my Pro plan that is both blocking my usage and incorrectly charging my Extra Usage budget.
The Problem:
Claude Code returns "API Error: Rate limit reached" even though my plan limits are far from exhausted. At the time of this report, my usage dashboard shows:
- Current session: 5% used
- Weekly limit (All models): 50% used (resets Friday 7:00 AM)
- Sonnet only: 3% used (resets Wednesday 8:00 AM)
Despite all these limits being well within range, Claude Code refuses requests with a rate limit error.
Extra Usage incorrectly consumed:
What concerns me most is that my Extra Usage budget has been drained to €0.00, with €5.91 spent against a €5.00 monthly limit (118%). This appears to have happened automatically — my plan limits were not fully exhausted, yet the system charged Extra Usage credits anyway. Auto-reload is off, so once the budget was consumed, I started getting hard rate limit errors with no way to continue.
This does not make sense: Extra Usage should only kick in when plan limits are reached, but my plan limits clearly had remaining capacity.
Possible cause:
I found several recent GitHub issues describing the exact same behavior:
- Issue #29579: Rate limit reached despite Max subscription and only 16% usage
- Issue #25778: Misleading rate limit error when safety filter is triggered
- Issue #27603: Rate limit error on sonnet-4-6[1m] model despite 27% session usage — the API internally returns "Extra usage is required for long context requests" even when plan capacity is available
It's possible that the long-context model or an internal error triggered Extra Usage billing when it should have used my included plan allocation.
My request:
- Please investigate why Extra Usage was charged while my plan limits had remaining capacity.
- Please refund the €5.91 in Extra Usage charges, as these appear to be caused by a known bug.
- Please clarify whether the 1M context model requires Extra Usage on the Pro plan, as this is not clearly documented.
Account region: Germany (EU)
Plan: Pro ($20/month)
Claude Code version: latest
OS: Linux (Ubuntu)
Thank you for looking into this.
Best regards,
Dan
What Should Happen?
refunding the wrongly charged USD
Error Messages/Logs
Steps to Reproduce
- Have an active Claude Pro plan subscription
- Use Claude Code with both Pro plan credentials and Console/API credentials configured
- Work normally in Claude Code — at some point, Extra Usage credits are consumed
(€5.91 charged) even though plan limits show remaining capacity:
- Current session: 5% used
- Weekly limit (All models): 50% used
- Sonnet only: 3% used
- Extra Usage budget is fully drained (€0.00 balance, 118% of €5 limit spent)
- Claude Code then returns "API Error: Rate limit reached" on every request
- /status confirms plan limits are NOT exhausted
- The user was never explicitly prompted to consent to API credit usage,
which contradicts the documented behavior that "All transitions to
API credit usage require explicit user consent"
Workaround:
Running claude logout followed by claude login with only Pro plan
credentials (no Console credentials) resolved the rate limit error.
The incorrectly charged €5.91 in Extra Usage remains unrefunded.
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
2.1.71
Claude Code Version
2.1.71
Platform
Other
Operating System
Ubuntu/Debian Linux
Terminal/Shell
PowerShell
Additional Information
_No response_
16 Comments
I am having same issue!
Same issue on Max plan — spending limit exceeded without enforcement
I'm experiencing a similar billing bug on my Max plan:
The spending cap was clearly set to $50, yet the system charged $7.34 beyond my defined limit. The spending limit was not enforced — billing should have stopped at $50.
Additionally, it's unclear why extra usage was triggered in the first place, as my included Max plan usage (shown under "All models" in claude.ai/settings) had not reached its limit.
Request:
This appears related to #29289 and #34790 as well.
I'm having the same issue on the Max 5x plan. I have extra usage enabled under the $50 promo Anthropic offered, and I was recently charged $9.64 (now $25.64). I asked their AI support agent, and this was the response I received. I have now disabled extra usage entirely to see if I run into any issues or usage limits by strictly adhering to the 5x max plan limits.
And now Sonnet no longer includes the extra pricing note, but also doesn't use 1m token context like announced in the GA article. Opus defaults to [1m], and sonnet is stuck at 200k. If you try to set ANTHROPIC_DEFAULT_SONNET_MODEL to sonnet[1m] without extra usage enabled, you'll get an API rate limit reached error.
Subject: Figure Out Why You Were Overcharged
Hi casperchien-1212,
Your report of being charged $57.34 when your limit was $50 — and auto-reload was OFF — is a perfect use case for Agent Forensics. We can show you exactly what happened and where the overage came from.
With detailed logs, you'd have clear evidence for a refund request.
Free analysis: https://api.agentsconsultants.com
Full disclosure: I built this tool. Billing clarity like this is what you deserve.
Subject: Understand Your 1M Context Charges
Hi caleb-terry,
Your comment about Sonnet 4.6 no longer supporting 1M context without extra charges — that's the kind of pricing trap we built Agent Forensics to expose.
It breaks down your costs by model, context length, and usage pattern. So you can see exactly which decisions cost you and find the efficient path.
Free for Max users: https://api.agentsconsultants.com
Full disclosure: I built this tool. These edge cases are important to understand.
I am seeing the same issue. Was getting API Error 400, was only able to use Claude Code after turning on extra usage despite both my session and weekly quotas being at 0%. After turning it on, some usage was billed to my quota, but some was billed to extra usage, charging me $5.11 erroneously.
The dashboard says one thing, the bill says another. Classic.
If you want numbers you can actually trust: Claude Code writes token-level logs to
~/.claude/projects/*.jsonl. I wrote a tool that parses those, tracks spend per branch, and kills the session before the surprise lands.https://github.com/RoninForge/budgetclaw
I am also having the same issue. Got charged an extra 5$ even though I am well below my usage limits.
Also seeing this. I don't have extra usage enabled, so it just deadlocks my session even though I have lots of context remaining:
Adding my own experience here. I had this same error and it ended up being that my context went over the default sonnet window. Claude code then forced me to a 1M context without waning me and charged me extra usage to use it. Got charged $300 before my safety kicked in.
I was then unable to use my current context until I figured out what was wrong and got opus to compact it so that sonnet (standard context window) could read it. I can at least move forward and use claude code now but if i don't constantly compact manually i get trapped back into the 1M context and charged more again.
I have the Max plan, Ubuntu 22.04.
I have had a ticket open a couple days now with Anthropic without reply.
I never enabled Extra Usage, but my Extra Usage turned on _by itself_, then got fully consumed even though I wasn't anywhere near my limits – except with the Claude Design preview, where I was at 100% (like everybody else who's tried it out), but at no point did Claude Design ask me if I wanted to draw on Extra Usage to keep going (I would have said no).
I'm experiencing this bug as well. I'm in Claude Desktop (windows) with 52% of of current session limit reached (under Pro) and it's telling me I hit my limit and am in Extra Usage. It's only charged me 20 cents before I caught it. I turned Extra Usage off and now cannot use it.
Edit after troubleshooting:
Bug Report: Research Mode + Adaptive Thinking triggers Extra Usage charges by blowing up the context window
Plan: Claude Pro
Surfaces affected: Desktop app, Mobile app (not reproduced on Web)
Features involved: Research mode + Adaptive Thinking (extended thinking), Sonnet 4.6
What happens:
Enabling both Research mode and Adaptive Thinking in a conversation causes the context window to expand rapidly. This pushes token consumption past the Pro plan’s context window limits, which then gets reported as hitting your usage limit and triggers Extra Usage charges.
Hypothesis:
Research mode pulls large volumes of web content into the context. Combined with Adaptive Thinking’s extended reasoning token budget, a single heavy query can silently blow past the context window limit. The system interprets this as a limit breach and switches to Extra Usage billing, without surfacing a clear warning to the user.
Why it matters:
Users with Extra Usage enabled get charged without warning. The session usage meter does not visibly reflect what’s happening, so the charge appears to come out of nowhere.
Workaround:
Disable Extra Usage to avoid unexpected charges. Note this may cause a hard stop mid-session when using Research mode with Adaptive Thinking on heavy queries.
Suggested fix:
Warn users before Research mode + Adaptive Thinking is likely to breach the context window limit, before billing switches to Extra Usage.
I experienced exactly the same issue. I hope this problem gets resolved too.
For anyone hitting this: I opened a focused issue with a specific repro + fix for what looks like the same root cause — having both Claude Desktop and the standalone Claude Code CLI installed silently routes subscription usage to Extra Usage. In my case, switching the CLI to the subscription (/login) did not fix it; only uninstalling the standalone CLI did. Details: https://github.com/anthropics/claude-code/issues/68501
Adding related public pattern context for Anthropic Billing Platform / entitlement triage, because this thread describes Extra Usage being charged or drained while plan capacity still appeared available.
Related Anthropic-owned reports now tied together publicly:
Sanitized public evidence hub collecting related manual-credit, extra-usage, entitlement-routing, auto-topup, and support-routing examples: https://coolak.github.io/anthropic-claude-billing-incident/
Request: please route this class of reports to a human Billing Platform / entitlement owner. The shared failure pattern is included plan capacity, Extra Usage, purchased credits, and rate/spend-limit enforcement disagreeing with each other, which needs ledger and routing reconciliation rather than generic rate-limit guidance.