claude-vscode.editor.openLast not found — extension fails to activate on Windows due to hardcoded Linux CI path

Preflight Checklist

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

What's Wrong?

The Claude Code VS Code extension (v2.1.129, win32-x64) fails to activate on Windows with Node.js 22, causing all commands to show "command not found".

Root cause: extension.js contains a hardcoded Linux CI build path passed to module.createRequire():

var y20 = Ai.createRequire("file:///home/runner/work/claude-cli-internal/claude-cli-internal/build-agent-sdk/sdk.mjs")

Node.js 22 rejects this URL on Windows, preventing the extension from activating.

Workaround: Replace with Ai.createRequire(__filename)

Environment: Windows 11, VS Code 1.118.1, Node.js 22.22.1, Claude Code extension 2.1.129

What Should Happen?

The extension should activate successfully on Windows with Node.js 22 without hardcoded Linux CI paths.

Error Messages/Logs

Steps to Reproduce

a1. Install Claude Code VS Code extension v2.1.129 on Windows 11

1. Open VS Code 1.118.1
2. 3. Attempt to use any Claude Code command
3. 4. All commands show "command not found"
4. 5. Check VS Code extension logs — extension fails to activate with error related to module.createRequire() and the hardcoded path: file:///home/runner/work/claude-cli-internal/claude-cli-internal/build-agent-sdk/sdk.mjs

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.129 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_