Cost and usage issues on VS Code — page 3
Issues the maintainers labelled both platform:vscode and area:cost.
203 issues · 40 open · 163 resolved (80%) · first seen Feb 26, 2026
Is this getting better or worse?
This class of problem is converging. 79 new reports in the last 90 days vs 119 in the 90 before — -34%. The open backlog peaked at 65 in 2026-04 and sits at 40 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
155 of these reports name the Claude Code build they were running, spanning 81 releases. Heaviest reporters:
- Claude Code v2.1.123
- Claude Code v2.1.92
- Claude Code v2.1.87
- Claude Code v2.1.104
- Claude Code v2.1.158
- Claude Code v2.1.126
- Claude Code v2.1.121
- Claude Code v2.1.119
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 35 days across 163 closures. Of the 163 closures with a recorded reason, 9% were closed as completed and 148 as not-planned or duplicate. The most recent completed fix landed in 2026-08.
Workarounds reported by the community
19 of these issues post a workaround someone says worked. The highest-engagement ones:
- [BUG] Abnormal rate limit consumption — 1-2 prompts exhausting 5-hour window
- 1-2 prompts exhausting the limit sounds like the cache creation bug others have reported in 38350. The token accounting seems broken. While waiting for a fix, multi-model routing h
Found in the thread of #38345 · 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 - Max plan: usage exhausted abnormally fast, twice in one day (March 31)
- …o dropped to 4.3% (effectively ~20x token inflation). After workarounds it recovered to 89–99% . Full analysis + workarounds: Important caveat: All my testing was done in the CLI environment ( in terminal, Linux). Since…
Found in the thread of #41504 · still open - [BUG] Usage credits required for 1M context - Pro plan blocked despite 17% usage
- …ses, making --model flag and CLAUDE CODE DISABLE 1M CONTEXT workarounds ineffective. Versions tested: 2.1.104 (WinGet), 2.1.6 (npm), 2.0.0 (npm) — all produce the same error. To use Claude Code at all, I was forced to pu…
Found in the description of #65514 · still open - 93% rate limit consumed in ~3 minutes on fresh session (Max plan, v2.1.85)
- ….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 #39938 · resolved
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–203
Ranked by community engagement (reactions weighted over comments).
- [BUG] Too faxt usage
- You've hit your session limit · resets 8pm (America/Mexico_City)
- You've hit your session limit · resets 4:30pm (Africa/Nairobi)