[FEATURE] vscode-extension version vs npm cli claude code version is not match the stable tagged

Resolved 💬 1 comment Opened Apr 17, 2026 by purushothammuktha-commits Closed May 25, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

vscode-extension version vs npm cli claude code version is not match the stable tagged

vscode extension when set the allowed extension setting to "stable" its always picked from microsoft vscode market place - latest (2.1.112) instead of stable npm cli claude code (2.1.97) where staged
Its misleading the claude code npm package cli version vs vscode extension.

Proposed Solution

https://www.npmjs.com/package/@anthropic-ai/claude-code?activeTab=versions

Claude code stable version must be in vscode-extension as well alongside with cli version and vscode-extension should be unique.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

In our Organisation Claude code npm package cli version where stable tagged version is installed across apple devices (https://www.npmjs.com/package/@anthropic-ai/claude-code?activeTab=versions)
for example : 2.1.97 (ason 17th April'26)
In vscode extension anthropic claude code installed stable version always pointed to latest version i.e, 2.1.112v

Enterprise use case here is to stable version suppose to be used across device. when subscribed to claude teams and max plan to roll it out for developers. Claude code settings to be managed across devices uniform.

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗