Claude usage limit reached
The plan quota was consumed and the session paused until reset.
173 issues · 27 open · 146 resolved (84%) · first seen May 23, 2025
First response · account
What to do now
Most likely: Authentication, usage state or session size blocked the request.
- Check the exact account, organization and usage window currently selected.
- Try a new short session before deleting credentials or local history.
- If the state is inconsistent across machines, preserve diagnostics and re-authenticate once.
These are conservative triage steps, not an official Anthropic fix. Use the issue and workaround evidence below before making a destructive configuration change.
Is this getting better or worse?
This class of problem is converging. 37 new reports in the last 90 days vs 62 in the 90 before — -40%. The open backlog peaked at 31 in 2025-10 and sits at 27 today.
Derived by counting each matching issue from its creation date until it closed. First-party
computation over the anthropics/claude-code tracker — the trend is not published
anywhere upstream.
Which builds report this
54 of these reports name the Claude Code build they were running, spanning 42 releases. Heaviest reporters:
- Claude Code v2.1.42
- Claude Code v2.1.220
- Claude Code v2.1.169
- Claude Code v2.1.191
- Claude Code v2.1.162
- Claude Code v2.1.175
- Claude Code v2.1.142
- Claude Code v2.1.150
Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.
Do these get fixed?
Median time to close is 32 days across 146 closures. Of the 146 closures with a recorded reason, 18% were closed as completed and 119 as not-planned or duplicate. The most recent completed fix landed in 2026-08.
Workarounds reported by the community
27 of these issues post a workaround someone says worked. The highest-engagement ones:
- [BUG] Claude Max plan session limits exhausted abnormally fast since March 23, 2026 (CLI usage)
- …pent over $30 in 24 hours so I can keep working. There is a work around but its horrible. You can have all your MD and instruction files updated and put in the project. Then start all new conversations so you don't have…
Found in the thread of #38335 · still open - [BUG] Opus usage limit reached unusually fast with Max 20x plan since Claude Code v2
- I found a workaround by manually setting Opus in plan mode in the settings, which seem to resolved the issue.(opusplan) Well.. i guess i have to contact support now...
Found in the thread of #8449 · resolved - [BUG] Claude Code defaults to 1M context on fresh session with no workaround on Pro plan
- …ars immediately without any prompt or file loaded Attempted workarounds — none resolved it: - — same error - — same error - → with Pro credentials only — same error Expected behavior: Standard context window used by defa…
Found in the description of #62063 · resolved - [BUG] resume flag fails to maintain conversation context after hitting usage/context limits
- …to have this handled with a clean 'pause' given the costs. In the meantime, Telling it got it going again, but it seemed to have lost where it was and had to start over, killing a few extra tokens.
Found in the thread of #3138 · still open - [BUG] Abnormal Usage Consumption on Claude Code Session Resume — Possible Bug
- Adding another data point — seeing the same abnormal consumption after session resume. Usage jumps even when the resumed session is doing lightweight work. What helped my workflow:
Found in the thread of #38029 · still open
Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.
Matching issues 1–100
Ranked by community engagement (reactions weighted over comments).
- [BUG] Claude Max plan session limits exhausted abnormally fast since March 23, 2026 (CLI usage)
- Feature Request: API Fallback for Pro/Max Subscriptions When Limits Are Reached
- [BUG] Opus usage limit reached unusually fast with Max 20x plan since Claude Code v2
- [BUG] Claude Code defaults to 1M context on fresh session with no workaround on Pro plan
- [BUG] resume flag fails to maintain conversation context after hitting usage/context limits
- [BUG] Abnormal Usage Consumption on Claude Code Session Resume — Possible Bug
- [BUG] Insanely rapid usage limit reached!
- [BUG] # Issue: Misleading Cost Command Output in Claude Code
- [BUG] Rate limit 429 errors despite dashboard showing available quota - Two Max accounts, documented inconsistencies
- Usage limit reached repeatedly without active use — Pro plan
- Token usage limit reached significantly earlier than in previous versions
- [BUG] Claude Code shows 'Usage limit reached' despite session at 2% and weekly at 32%
- MAJOR BUG: Claude Code Stuck in Infinite Compaction Loop Making it Basically Useless!
- [Bug] Team Billing: Frequent Unexpected Usage Limit Resets
- [BUG] Claude Code Pro Quota Significantly Reduced: Limit Reached in ~20 Prompts per 5 Hours
- [BUG] claude limit reached in less than one hour on opus 4.1, windows, v2.0.1
- [BUG] Max (20x) weekly limit depletes disproportionately — 51% mid-week, ~17% within minutes of session reset
- Misleading "Usage limit reached" error when selecting Sonnet — actually a 1M context tier gate
- [BUG] Claude usage limit reached. Your limit will reset at 3pm
- Two separate claude accounts [Work, Personal] used for development on two different remote servers, use the same usage limit.
- [BUG] Claude for Windows desktop app does not switch to extra usage when 5-hour limit is reached, while Claude Code CLI on the same account does
- [BUG] /usage command shows only time without day for weekly reset
- [BUG] Max 20x upgrade not reflected in weekly limits — depleting at Max 5x rate or worse (upgraded July 16, 2026)
- [BUG] Usage limit reached in 10 minutes
- Claude AI usage limit reached|1748268000
- [BUG] Claude Code uses entire 5 hour token limit in one prompt with zero feedbacks or results
- [BUG] Usage limit reached - while still having 93% weekly limit and 100% 5-hour limit
- Bug: Desktop app shows "Usage Limit Reached" incorrectly
- Limit reset should indicate timezone
- [BUG]b"Usage limit reached" triggered after weekly usage jumped from ~35% to blocked in ~12 minutes
- [BUG] incorrect timezone name in limit usage message
- [BUG] 5 hour limit reached for claude code extensions visual studio code just with 4 prompts
- Claude AI usage limit reached|1760000400
- [BUG] Team Premium seat weekly limit stuck at 100% after only 102M tokens — other users on same plan consume 757M+ without issues
- [BUG] @agent-explore "Out of Credits" on $100 Max Plan
- Claude AI usage limit reached|1753113600
- Claude AI usage limit reached|1753088400
- [BUG] Max plan usage at 100% with zero requests — claude.ai (not Claude Code)
- [BUG] USAGE BUG, opus drains sonnet usage URGENT FIX NEEDED
- [BUG] Claude Code extension in VS Code is using more tokens than the CLI
- [BUG] Claude Code desktop - Usage limit reached - while session reset
- [BUG] Claude Code shows “Usage limit reached” even though my Usage page shows plenty of allowance remaining.
- [BUG] Max 5x: usage counter increments with zero active sessions — all auth revoked, no Claude Code running
- [BUG] rateLimitTier set to "default_claude_ai" instead of "default_claude_pro" — CLI treating Pro subscription as API token auth, immediate "API Error: Rate limit reached" with zero usage
- [BUG] claude code - Usage Limits Show 0% Daily But 41% Weekly, Rate Limited Despite No Activity — Phantom Usage Consuming Paid Max 20x Quota
- Claude Code Usage limit issue
- Claude AI usage limit reached|1749855600
- Claude AI usage limit reached|1750460400
- [BUG] Usage limit reached despite UI showing low consumption percentages
- [BUG] Claude Code input unresponsive — "Usage limit reached" despite being well under 5-hour (28%) and weekly (16%) limits on Max 20x plan
- [BUG] My claude code usage limit is not reset still.
- [BUG] The conversation is summarized below: Claude AI usage limit reached
- [BUG] 5 hour usage limit reached - but I have not used Claude in over a day
- Bug: Windows Desktop App token loop with Claude Code/MCP causes immediate 100% session lockout
- [BUG] Claude Code shows "Usage limit reached" while all plan limits are well below 100%; new 5-hour session jumped to ~20% immediately after reset
- [BUG] Usage limit discrepancy between VS Code extension and CLI on same Max account
- [BUG] Limits not resetting
- Claude API Usage Limit Exceeded, Blocking Code Generation
- [BUG] No auto-fallback or clear error when Opus 4 limit reached - shows generic "usage limit" error
- Anthropic API Billing: Persistent Model Access Restriction
- Claude AI usage limit reached|1753560000
- [BUG] Claude Code-shared usage limit blocks macOS Desktop Chat while WebChat works
- [BUG] Desktop app Code tab routes Sonnet 4.6 sessions to 1M context, blocking usage on Max plan
- VS Code Claude extension API usage limit reached
- [BUG] API Error / Usage exhausted when I just started and have plenty of usage left.
- [BUG] Opus 4.6 returns "Rate limit reached" mid-session on Claude Pro plan
- [BUG] Visual Studio Code plugin shows incorrect limit when hitting 5 hour limit at end of week
- Claude AI usage limit reached|1755615600
- Agent Context Loss After API Usage Limit Reset
- Conversation Compaction Failure: Summary Generation Error
- Claude AI usage limit reached|1753783200
- [BUG] Massive Token Consumption - 1.67B tokens in 5 hours causing severe cost impact
- Claude AI usage limit reached|1749924000
- [BUG] Fable 5 on Max: "You've hit your monthly spend limit" despite Unlimited spend limit and meters at 5% session / 41% weekly
- Usage-limit gating is invisible to unattended sessions — agent-team orchestrator froze 5h with zero signal in transcript or terminal
- [BUG] Sonnet usage error on CC
- [BUG] Usage limit reached unexpectedly after 429 rate limit errors
- [BUG] This is frustating to get usage limit issue because of Anthropic capacity limitation
- Specific API error silently replaced by generic UI message, hiding actionable remediation
- Desktop app: No way to use Sonnet with standard (200k) context — 1M context is forced, blocks usage when credits unavailable
- [BUG] Usage limit reached, but only in your imagination...
- Daily usage limit exhausted within hours while weekly limit is only 33% — usage tracking bug (Max plan)
- [BUG] Usage limit reached error with 0% usage displayed
- [BUG] HTTP 400 'prompt is too long' is misreported to the user as 'usage limit reached'
- [BUG] Usage limit reached on Max 5x with low usage (4% weekly, 9% session)
- [BUG] [BUG] Switching from Opus 4.7 1M to Sonnet mid-session (~700k tokens) breaks session completely — no recovery possible
- Claude AI usage limit reached and won't reset|1766502000
- Claude AI usage limit reached|1755309600
- [BUG] Running `/compact` when usage limit reached destroys entire context
- Max 200, why is Sonnet also cut off? Claude AI usage limit reached|1752634800
- Claude AI usage limit reached|1752001200
- Claude AI usage limit reached|1750770000 | Not being offered per usage API billing
- Claude AI usage limit reached|1749470400
- Claude Code blocked by "weekly limit reached" (resets Jul 25) while all usage meters show 0% — claude.ai web works on same account
- [BUG] --resume causes massive silent token drain on session restore (Pro, v2.1.193)
- [BUG] /usage stays stuck on Loading usage data on macOS
- [Bug] Model unavailable after usage limit reached in session
- [BUG] Extension shows "usage limit reached" while /usage reports 17% session / 1% weekly
- [BUG] "Usage limit reached" hard-stop fires below the displayed 5-hour ceiling (~95%, not 100%)
- [BUG] Usage limit reached in Claude Code despite 0% usage shown in Settings