[Bug] VSCode extension v2.1.53 (win32-x64) fails to activate: hardcoded Linux path in sdk.mjs

Description

The Claude Code VSCode extension (v2.1.53, win32-x64) fails to activate on Windows 11, causing all commands (e.g., claude-vscode.editor.openLast) to be unavailable.

Environment

• OS: Windows 11 Pro (10.0.26200)
• VSCode version: latest
• Extension version: anthropic.claude-code-2.1.53-win32-x64
• Claude Code CLI: working correctly

Error

From VSCode Extension Host log (exthost.log):

2026-02-25 09:52:25.620 [error] Activating extension Anthropic.claude-code failed due to an error:
2026-02-25 09:52:25.620 [error] TypeError: The argument 'filename' must be a file URL object, file URL string, or absolute path string. Received 'file:///home/runner/work/claude-cli-internal/claude-cli-internal/build-agent-sdk/sdk.mjs'
    at Object.<anonymous> (c:\Users\linkp\.vscode\extensions\anthropic.claude-code-2.1.53-win32-x64\extension.js:45:4882)

Root Cause

The extension bundles a hardcoded Linux CI build path (file:///home/runner/work/claude-cli-internal/claude-cli-internal/build-agent-sdk/sdk.mjs) that is not valid on Windows. This causes the extension to fail during activation, leaving all commands unregistered.

Symptoms

• All claude-vscode.* commands show "command not found" error
• Extension icon in title bar is present but non-functional
• Reinstalling the extension does not resolve the issue

Steps to Reproduce

1. Install Claude Code VSCode extension v2.1.53 on Windows 11
2. Open VSCode
3. Observe activation failure in Extension Host logs

Expected Behavior

Extension activates successfully and all commands are available.

Workaround

None currently available. Waiting for a patched release.