Cost and usage issues on Windows — page 3
Issues the maintainers labelled both platform:windows and area:cost.
549 issues · 172 open · 377 resolved (69%) · first seen Jul 26, 2025
Is this getting better or worse?
This class of problem is holding steady. 182 new reports in the last 90 days vs 223 in the 90 before — -18%. The open backlog peaked at 172 in 2026-10 and sits at 172 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
376 of these reports name the Claude Code build they were running, spanning 144 releases. Heaviest reporters:
- Claude Code v2.1.126
- Claude Code v2.1.87
- Claude Code v2.1.296
- Claude Code v2.1.119
- Claude Code v2.1.263
- Claude Code v2.1.247
- Claude Code v2.1.123
- Claude Code v2.1.260
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 377 closures. Of the 377 closures with a recorded reason, 11% were closed as completed and 337 as not-planned or duplicate. The most recent completed fix landed in 2026-10.
Workarounds reported by the community
59 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 549 matches; the statistics above cover all 549.
- [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] I have recorded a video of the Claude Code limit bug.
- [BUG] All tokens and the limit are spent in a couple of seconds
- [BUG] Review crashed before producing findings
- You're out of extra usage · resets May 18, 6am (Europe/Kiev)
- [BUG] Claude Code silently uses project ANTHROPIC_API_KEY from .env instead of Max plan OAuth, causing unexpected API charges
- [BUG]
- [BUG] claude -p headless: no spend visibility/cap for orchestrated workloads -- $313 burned in 8.5h on a single retry-stuck item; support routing loop with 3 Fin contradictions
- [BUG] Usage limit reached error with 0% usage displayed
- You've hit your limit · resets 1:40pm (America/Sao_Paulo)
- [Bug] Excessive token consumption due to infinite thinking loops blocking progress
- [Bug] Session limit exceeded causes unexpectedly high token consumption rate
- desktop is freezing and the weekly limit is not logging i chatted and making me wait 10 days vs 7 each week
- Used up 1 Ultrareview credit, but claude crashed and threw error API Error: Server is temporarily limiting requests (not your usage limit) · Rate limited
- [BUG] Abnormal compute consumption: 5-hour Max Plan quota exhausted in 7 minutes during minor refactor
- [BUG] Usage limit reached on Max 5x with low usage (4% weekly, 9% session)
- Usage allowance shared across two separate Anthropic accounts in parallel VS Code Claude Code sessions
- [BUG]
- [Bug] Token usage spike with non-Opus models after Opus 4.7 release
- [BUG]
- [Bug] System-injected tools and schemas consume excessive tokens without user control
- [MODEL]
- [BUG] Account suspended after Claude Code CLI usage — appeal pending 3+ weeks with no response
- Usage budget consumed in ~15 minutes starting April 20, no workload change
- Read tool injects unconditional malware-warning system-reminder, wasting tokens, polluting attention, and causing premature task termination
- [Bug] Session restoration causes incorrect token usage reporting after auto-compact
- [Bug] Agents waste excessive token budget on permission checks without early validation
- [Bug] Claude Code hangs during file review consuming API quota without output
- [BUG] Promotional Extra Usage credits show remaining balance but system blocks as if /usr/bin/bash — billing enforcement/display parity
- [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
- [Bug] Agents consume excessive tokens without producing results
- [BUG] Paid Max 5x, weekly limit still enforced at Pro size (2nd paid week, support escalation unanswered for 5 days)
- Session reconnect silently discards an explicit `/model` choice and falls back to the global default
- You've hit your session limit · resets 2:50pm (America/Sao_Paulo)
- You've hit your session limit · resets 6:10pm (Europe/Paris)
- [Bug] Usage limit not enforced - allows spending beyond configured credit limit
- 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] Fable 5 usage-credits gate blocks session while weekly usage limit shows plenty of headroom (Pro plan)
- [BUG]
- [BUG] Subagent output discarded when spend limit terminates fanout — tokens billed, zero results returned
- 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
- 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] Repeated incorrect bug diagnosis led to ~$94 wasted over 2 days on the same root cause
- [BUG] "Usage credits required for 1M context" error persists after plan recharge on VS Code extension
- [BUG]
- [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 incorrectly requires 1M context credits on Pro plan (Desktop)
- 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] 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
- [BUG] Claude launched a 137-agent Workflow for a single-file audit, against a standing "no multi-agent" instruction (~53% of weekly usage in 1 hour)
- [BUG] stream-json result: after a mid-stream API error and the non-streaming retry, usage counts both calls but modelUsage and total_cost_usd count only the retry
- [MODEL] Orchestrating session ignored the project's written agent and batch limits, then retried its own load-caused timeouts for 2 hours: ~12% of a weekly Max allowance spent, nothing merged