Claude usage limit reached — page 2
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 101–173
Ranked by community engagement (reactions weighted over comments).
- [BUG] Sonnet 4.6 incorrectly requires 1M context credits on Pro plan (Desktop)
- False "Extra usage required for 1M context" / "Usage limit reached" error with no actual limits hit
- [BUG] 'Usage limit reached' displayed when extra usage is available
- [BUG] macOS Desktop 1.6608.2 - "Prompt is too long" error triggers persistent "Usage limit reached" state with full quota remaining
- [BUG] Claude Code Sessions input locked after daily usage limit — persists after reset
- [BUG] Usage limit reached prompting upgrade when only 11% usage
- [BUG] Claude Desktop shows "Usage limit reached" with 11% session / 29% weekly usage — CLI works fine, resuming from CLI clears Desktop error
- [BUG] Pro plan CLI blocked with 'usage limit reached' despite 0% quota used on dashboard (689/200k tokens)
- [BUG]
- [BUG] Claude Code "Usage limit reached" with 0% on 5-hour window and 5% weekly usage
- [BUG] Desktop app shows "Out of extra usage" and disables input despite 91% weekly / 61% extra usage remaining
- [BUG] Usage limit reached” in Claude Code Desktop for ~24 hours, but claude.ai and Antigravity work fine
- [Bug] Claude Code usage limit error with discrepant quota metrics across dashboard and CLI
- No notification when Opus usage exhausted and model falls back to Sonnet
- [BUG] Claude for Chrome showed usage limit reached when real Claude Max (20x) showed only 17% used for the current session
- Expose session rate limit usage and reset time in statusLine JSON input
- [BUG] "Stop and wait for limit to reset" after /compact, despite being at 75% of usage limit
- [Bug] Rate limit blocking ignores anthropic-ratelimit-unified-representative-claim header
- [Bug] Anthropic API Error: Usage limit reached despite /usage showing available quota
- [Bug] Usage discrepancy between Claude Code and claude.ai web interface
- Claude API Usage Limit Error Incorrectly Displayed
- Claude AI usage limit reached|1762952400
- [Bug] Context Limit Exceeded Before Full Context Processing
- API Rate Limit Blocking Repeated Claude Code Interactions
- API Usage Limit Blocking Requests After Stated Reset Time
- Bug Report
- Anthropic API Usage Limit Not Resetting After Scheduled Reset Time
- [BUG]
- [Bug] Usage limit shows 6-day reset instead of 5-hour reset (Claude Max 20x, VS Code extension)
- [Bug] Anthropic API Usage Limit Blocking Access Unexpectedly
- [Bug] Anthropic API: Unexpected Usage Limit Error
- [BUG] Limit hits message became my compacted context
- [BUG] Claude does not continue after "Claude usage limit reached. Your limit will reset at 2pm (America/New_York)"
- Claude AI usage limit reached|1754395200
- Claude AI usage limit reached|1754298000
- Claude AI usage limit reached|1753441200
- Claude AI usage limit reached|1753077600
- Claude AI usage limit reached|1752678000
- [BUG] Crash when triggering a prompt provided by MCP
- Claude AI usage limit reached|1750708800
- Claude AI usage limit reached|1750240800
- [BUG] Team Premium weekly usage counter stuck at 100% despite no usage after multiple reset cycles
- Opus-specific rate limit is not reflected in the usage meter — misleading UX
- [BUG] Remote Control "enable for all sessions" preference not honored; quota-limit stops also kill the session
- [BUG] Usage limit pop up appears when the issue was Rate Limited
- VS Code extension: Effort slider disappears (instead of disabling) when usage limit forces model fallback
- Mobile: stuck on stale "usage limit reached" reply after top-up while Extra Usage is active (desktop works)
- [Feature Request] Scheduled Auto-Resume After Usage Limit — Zero-Interruption Agentic Workflows
- [BUG] Sonnet 4.6 stuck on usage limit (Opus works fine)
- [BUG] USAGE limit error on claude CODE, even without using claude
- [BUG] Claude Desktop (Windows) shows "Usage limit reached" with only 3% of 5-hour limit used - enterprise accounts cannot use cache-clear workaround
- [Bug] Desktop App incorrectly reports "Usage Limit Reached" despite available credits
- [BUG] Windows Desktop App freezes after daily token limit — input locked, banner persists after reset
- [BUG] Claude app v. 1.3109.0 Pro plan hit usage limits after just 4 questions, seems to be counting previous chats in current session
- [DOCS] Troubleshooting docs omit server-error guidance and usage-vs-rate-limit distinction
- Kiev is not Kyiv
- [BUG] Reset time formatting issue
- [BUG] Issue: Session (5hr) usage limit exhausted within minutes on a lightweight document-edit task
- [BUG] Research consumes 73% usage in 20 seconds after Pro renewal, web/app desynchronization with false unblock
- Status line: show token limit reset time or remaining time instead of static duration
- [BUG] Subagents (Task/Agent tool) die silently on spend/usage limit hit, with no partial-result handoff or wait-for-reset behavior
- [Bug] CLI doesn't distinguish between insufficient credits and monthly usage limit exceeded
- [BUG]
- [BUG] Claude Code shared usage gate blocks despite /usage showing quota remaining
- [BUG] Rate-limit / usage-limit is emitted as a synthetic assistant turn with terminal stop_reason=stop_sequence, indistinguishable from a clean completion
- [BUG] Claude Code defaults to 1M context on fresh session with no workaround on Pro plan
- [BUG] Usage limit reached at 0% session and 12% weekly; used the in-app support (bot) and they told me to report here as it has persisted across multiple sessions.
- [BUG]
- Rate-limit auto-resume checkbox shown in one session but not in a concurrent session
- [BUG] Claude desktop app opens infinite popup windows and freezes system when usage limit is hit during heavy parallel background tasks
- Session usage limit silently kills background agents and prevents scheduled tasks from firing
- [BUG] Windows desktop app: 'Usage limit reached' persists ~18h while Usage page shows 0% session / 27% weekly / 51% Fable (Max 20x)
- [BUG] : Claude Code CLI "Usage limit reached" while claude.ai and Claude Design work normally