claude-code - 💡(How to fix) Fix [BUG] VS Code extension left behind on a severe, already-fixed bug and it cost real money

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Earlier, a similar error ate roughly half of my $100 credit.

Error Messages/Logs

Root Cause

The #60334 thread is full of the same story, people draining their limit in minutes and losing their whole $100 credit. Losing that to a known, already-fixed bug just because the extension wasn't updated feels unfair, and I'd appreciate a refund.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

The image-processing loop from #60334 was a serious bug: it could drain a full usage window in minutes. It's now fixed and closed (with #60221, #60702 and #61065 marked as duplicates). But the fix never reached the VS Code extension. The CLI is already on 2.1.150, while the extension only offers up to 2.1.145 (marked "current") — so there's nothing newer to install. Extension users are stuck on a build that still has the bug, with no way to upgrade.

That's the real problem here:

when a bug is this severe and this costly, the extension shouldn't be left lagging days behind the CLI. A fix that drains people's money should be pushed to the extension fast, not whenever it happens to catch up.

It cost me real money: About $50 of paid extra usage gone before I could react. Earlier, a similar error ate roughly half of my $100 credit.

The #60334 thread is full of the same story, people draining their limit in minutes and losing their whole $100 credit. Losing that to a known, already-fixed bug just because the extension wasn't updated feels unfair, and I'd appreciate a refund.

Versions: CLI 2.1.150 · VS Code extension 2.1.145 (latest available) OS: macOS

What Should Happen?

critical fixes should reach the extension on the same timeline as the CLI. At minimum, when the CLI is ahead, a matching extension version should be installable so users aren't locked onto a stale, buggy build.

Error Messages/Logs

Steps to Reproduce

Open the Claude Code VS Code extension Check the version: 2.1.145 is the newest installable ("current"), while the CLI is already on 2.1.150 The image-processing loop bug fixed in a newer CLI build is therefore still present in the extension, with no way to upgrade

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Extension 2.1.145 (latest available) · CLI 2.1.150

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING