VS Code extension fails to activate on Windows — hardcoded /home/runner path in packaged sdk.mjs

The Claude Code VS Code extension fails to activate on Windows 11 with the following error in the Developer Tools console:

Activating extension 'Anthropic.claude-code' failed: 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'.

The path file:///home/runner/work/claude-cli-internal/... looks like a GitHub Actions runner path that got baked into the packaged extension, so activation tries to load sdk.mjs from a Linux CI path that doesn't exist on the user's machine.

Environment

• OS: Windows 11 Home Single Language (10.0.26200)
• VS Code: stable
• Claude Code CLI: installed via npm (claude.ps1 shim at %APPDATA%\npm\)
• Affected extension version: latest as of 2026-05-06
• Working version after downgrade: v2.1.128

Repro

1. Install the latest Claude Code extension on Windows
2. Click the sidebar icon — panel renders completely blank
3. Open DevTools Console (Help → Toggle Developer Tools) — see the error above
4. The "Claude Code" output channel never appears in the Output panel dropdown, confirming the extension never activates

Impact

Extension is unusable on Windows on the latest version — users only see a blank panel with no error surfaced in the UI itself.

Workaround

Downgrade via Extensions panel → gear icon → "Install Another Version..." → select v2.1.128.