Cost and usage issues on Windows

Issues the maintainers labelled both platform:windows and area:cost.

548 issues · 171 open · 377 resolved (69%) · first seen Jul 26, 2025

Is this getting better or worse?

This class of problem is holding steady. 183 new reports in the last 90 days vs 223 in the 90 before — -18%. The open backlog peaked at 171 in 2026-10 and sits at 171 today.

0 43 86 128 171 2025-072025-122026-052026-10
2025-07 — First reports2026-04 — Most new reports (108)2026-10 — Peak backlog (171 open)

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

375 of these reports name the Claude Code build they were running, spanning 144 releases. Heaviest reporters:

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 1–100

Ranked by community engagement (reactions weighted over comments). Listing the top 300 of 548 matches; the statistics above cover all 548.

Related aggregations

  1. Cost and usage issues on macOS

    1,206 issues
  2. Cost and usage issues on Linux

    341 issues
  3. Cost and usage issues on VS Code

    248 issues
  4. The desktop app issues on Windows

    2,230 issues
  5. Terminal UI issues on Windows

    1,760 issues
  6. Core CLI issues on Windows

    1,413 issues
  7. Model behaviour issues on Windows

    1,301 issues
  8. Cowork issues on Windows

    1,071 issues