Cost and usage issues on Windows — page 3
Issues the maintainers labelled both platform:windows and area:cost.
415 issues · 90 open · 325 resolved (78%) · first seen Jul 26, 2025
Is this getting better or worse?
This class of problem is converging. 132 new reports in the last 90 days vs 226 in the 90 before — -42%. The open backlog peaked at 125 in 2026-04 and sits at 90 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
264 of these reports name the Claude Code build they were running, spanning 110 releases. Heaviest reporters:
- Claude Code v2.1.126
- Claude Code v2.1.87
- Claude Code v2.1.119
- Claude Code v2.1.123
- Claude Code v2.1.114
- Claude Code v2.1.81
- Claude Code v2.1.247
- Claude Code v2.1.104
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 37 days across 325 closures. Of the 325 closures with a recorded reason, 12% were closed as completed and 286 as not-planned or duplicate. The most recent completed fix landed in 2026-08.
Workarounds reported by the community
50 of these issues post a workaround someone says worked. The highest-engagement ones:
- [BUG] Extremely rapid token consumption. There appears to be a critical issue with token calculation and quota management. Users, including myself, are experiencing an unusually high rate of token consumption
- ….3% , meaning ~20x token inflation per turn. After applying workarounds it stabilized at 89-99% . Full analysis with per-request measured data, safe workarounds, and community references (including [cc-cache-fix](
Found in the thread of #38239 · still open - [BUG] Error: Error during compaction: API Error: Usage credits required for 1M context · turn on usage credits at claude.ai/settings/usage, or use --model to switch to standard context
- …runs /clear. This is a new behavior as of a day or so ago. Workaround Running /clear restores the session. The error message suggests using --model to switch to standard context, but this requires hardcoding a model nam…
Found in the description of #63896 · still open - Claude Code changed default model to 1M context without notifying Pro users
- …overnight. I lost hours trying to debug the issue, applying workarounds (environment variables, settings.json), and ultimately had to downgrade to a smaller context model — losing functionality I was already using and pa…
Found in the description of #62199 · still open - Add --max-context flag to cap context window usage
- …access to current context token count, so can't build this as a workaround Environment - Claude Code on Windows (MSYS2/Git Bash) - Opus 4.6 with 1M context - Previously worked well with 200K limit
Found in the description of #34650 · resolved - Opus 1M context on Max plan requires extra usage despite docs saying 'included with subscription'
- …t yesterday. Upgraded from Max 5x → Max 20x today to try to work around this. Still rate-limited at 0% usage. Total spend now exceeds £300 across plan upgrades and erroneous extra-usage charges. /bug report submitted — F…
Found in the thread of #39841 · 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 201–300
Ranked by community engagement (reactions weighted over comments). Listing the top 300 of 415 matches; the statistics above cover all 415.
- [Bug] Excessive token consumption on Claude 3.5 Sonnet model
- [BUG] Account suspension triggered by abnormal usage likely caused by Claude Code extension background activity
- [BUG] - Endless loop and excessive tool calls by sub agents contributing to massive spike in token consumption (Max plan user)
- [Bug] Anthropic API Error: Rate limit persists after logout/login and cache clear
- [BUG] /clear accumulates session cost in status line instead of resetting to $0.00
- [BUG]
- Claude in Chrome shows '5-hour limit reached' when actual usage is only 8% session/52% weekly (Pro plan)
- Repeated context compaction drains weekly token budget — 9 consecutive compactions in a single session
- [FEATURE] Auto-compact currently triggers mid-execution of CLI commands, causing unnecessary token re-reads and increased costs.
- [BUG] File modifications not syncing between Claude Code terminal and VS Code editor, causing credit waste
- [BUG] 5-Hour Limit Not Renewed - Usage Shows New Session But Access Delayed by 2 Hours
- You've hit your session limit · resets 1:40pm (Pacific/Auckland)
- [BUG] Prompt suggestions send a second full-context model call per turn, ~doubling token usage
- [BUG] A 13 hour 5-hour limit issue
- [BUG] Possible Usage Credits Re-enabling and Runaway Usage/Billing After Claude Code Update and Commit Action
- [BUG] Subagent output discarded when spend limit terminates fanout — tokens billed, zero results returned
- Desktop: ~3.9k tokens of built-in MCP tool schemas load non-deferred with no opt-out; built-in server instructions exceed the documented 2KB cap
- Malformed tool calls leaking into chat + disproportionate usage-limit consumption on Opus (regression, ~1 week)
- Fable 5 autonomous session destroyed user's main app via unverified assumption, verified its own breakage as green, burned ~75% weekly quota — 150 itemized failures
- [BUG] Model chosen via /model silently reverts to default when session continues from another device (quota still billed to pinned model)
- [BUG] --resume causes massive silent token drain on session restore (Pro, v2.1.193)
- Agent ignores user prohibitions, wastes 96% weekly token limit with zero results
- Billing-header nonce (`cch`) in system prompt breaks prompt caching on third-party providers
- [BUG] Extreme quota consumption (here we go again)
- [BUG] API Error: Usage credits required for 1M context · turn on usage credits at claude.ai/settings/usage, or use --model to switch to standard context
- [BUG] [BUG] Pro plan blocked by "Usage credits required for 1M context" — workarounds don't work
- Multi-lane Workflow agents re-create shared prompt cache per lane (no cross-sibling sharing), causing excessive token usage
- [BUG] Abnormal Session Limit Drain Since Opus 4.8 Rollout (May 28, 2026) — VSCode Extension, Pro Plan, Windows
- [BUG]
- [BUG] Sonnet 4.6 incorrectly requires 1M context credits on Pro plan (Desktop)
- [BUG] 5-hour limit triggers just by launching the CLI (zero messages sent)?
- [BUG] Review crashed before producing findings
- Ultrareview crashes before producing findings (2 consecutive failures)
- [BUG] unable to use ultrareview
- [BUG] cost.total_cost_usd underreports ~66% on Bedrock — cache tokens seems to be not counted for Opus 4.7 via eu.anthropic.* inference profile
- [BUG]
- [BUG] /ultrareview crashes at Dedupe step after successful Verify — findings unrecoverable
- [DOCS] Misleading messages in the Claude Code tab of Windows 11 Claude app
- You've hit your org's monthly usage limit
- [Bug] Anthropic API Error: Dedup stage crash on /ultrareview with no findings and misleading billing
- [BUG] Extra usage isn't working correctly - it's using up tokens for the next 5-hour session
- 🐛 [Bug] Follow-up to #29108 — Systemic billing failure corroborated by multiple issues — Credit restoration requested
- [Feature Request] CLAUDE.md re-injection deduplication for nested contexts
- [BUG] Regression: Cost/status dialog data no longer visible to Claude in conversation context
- [BUG] Account suspended after Claude Code CLI usage — appeal pending 3+ weeks with no response
- [Bug] Anthropic API Error: Token Exhaustion and Inconsistent Model Behavior
- [MODEL] Claude Code generated code that makes unnecessary Anthropic API calls, consuming user credits without clear disclosure
- [Bug] Excessive token usage during reasoning phase
- [BUG] Usage reset date shifted unexpectedly from Tuesday to Friday after mid-cycle reset.
- [Bug] Session limit consumed by non-API commands
- Token usage increased significantly — same 00 budget does far less work
- [Bug] Excessive token consumption with Sonnet 4.6/Opus 4.6 models
- [BUG] Claude Code terminal ignores account currency and shows `$` while web correctly shows `€`
- Session continuation consumes excessive tokens - 23% budget for trivial continue message
- Max plan: fast mode incorrectly billing to extra usage at low plan utilization
- [Bug] Anthropic API Error: Rate limit reached with Claude Max model
- [BUG] Session restarts burn user credits — agents ignore CLAUDE.md, run in circles
- unusually fast 30 minute token burn in Claude pro
- [BUG] Title: File modification system-reminders consume excessive context
- [Feature Request] Rate limiting feedback: Sonnet token consumption appears disproportionate to query complexity
- Context usage warnings not appearing when using slash commands
- [BUG] [FEATURE REQUEST] Automatic Refund for Unintended Auto-Reload Charges
- Limit reached · resets Dec 20, 9am (America/New_York) · contact an admin to increase limits
- [Bug] Model override to different model despite Sonnet configuration causes excessive token usage
- Inconsistent usage percentage display between VS Code extension and claude.ai
- [BUG] Fable 5 model-switch dialog says "billed separately from your plan" — contradicts documented plan inclusion
- [BUG] Fable 5 usage-credits gate blocks session while weekly usage limit shows plenty of headroom (Pro plan)
- Usage-limit message states a reset time ~3.5h later than when access actually returns ("session limit" vs "5-hour limit")
- Browser automation in near-1M-token sessions silently burns extreme token volume (~43M cache-read tokens / 5 min) with no warning
- [BUG] /usage: 5h block and weekly limit percentages rise in lockstep (should scale very differently)
- Session (5-hour) rate limit surfaces as 'You've hit your monthly spend limit' — wrong error message
- [BUG] Usage Limit Jumps from ~80% to 100% (with proof)
- [BUG] Repeated incorrect bug diagnosis led to ~$94 wasted over 2 days on the same root cause
- [BUG] Weekly usage meter resets ~4 days early (overnight) despite /usage stating "Resets Sat 5:00 AM" -- Max (20x)
- [BUG] "Usage credits required for 1M context" error persists after plan recharge on VS Code extension
- [BUG] Opus 4.7 cache hit rate collapse after May 27 incident — Messages 1.1k→88.9k in 9 minutes, $630/session
- Subagents on Pro 1M tier: trivial probes pass, real workloads fail at first tool call (probe-vs-workload divergence)
- [BUG] Sonnet 4.6 stuck on usage limit (Opus works fine)
- [BUG] Claude Code (non-interactive/headless, OAuth) requires usage credits enabled even when well within plan limits; usage credits toggle turns itself off spontaneously
- [ultrareview] silently returns empty findings on large branch diffs (no scope warning, burns free quota)
- Deferred MCP tool schemas inflate cache reads and per-turn token counts unnecessarily
- [Bug] Claude Code Terminal CLI not applying efficiency improvements correctly
- [BUG] VS CODE LIMITES RANGES VS CLAUDE CODE
- You're out of extra usage · resets May 11, 10pm (Asia/Bangkok)
- [Bug] Anthropic API Error: Extra usage required for 1M context window
- [Feature Request] Clarify rate limits and quota transparency for Pro plan users
- [Bug] Resume session unexpectedly consumes tokens from new billing period
- [Bug] Ultrareview quota decremented on API rate limit failure
- [BUG] /ultrareview consumed free credit on timeout without producing any output
- Limit reached · resets 3:50pm (Asia/Baghdad) · contact an admin to increase limits
- [Feature Request] Team account usage limits insufficient compared to personal plan
- [BUG] Cowork token burn rate forces subscription upgrades; root causes are file-read failures + connector instability + scheduler stalls
- [BUG] "Out of Extra Usage" message even though I have plan usage left
- Desktop app silently creates settings.json with effortLevel: high on first launch, causing unexpected API cost spike
- You've hit your limit · resets 7:10am (Australia/Sydney) - while I just barely started work after 1 day break
- You've hit your limit · resets 1:30am (Asia/Dhaka)
- [Feature Request] Add token-to-latency trade-off configuration for agentic operations
- [BUG] consumo está desproporcional ou com bug
- [BUG] Pro Session Limit Drains to 100% Instantly After Reset (Catch-22: CLI Locked)
- You've hit your org's monthly usage limit