[BUG] v2.1.129 - VS Code extension fails to activate on Windows - hardcoded Linux path
Resolved 💬 3 comments Opened May 6, 2026 by waqar424 Closed May 6, 2026
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?
After auto-update to v2.1.129, the Claude Code extension completely fails to activate on Windows. The icon disappears from the Activity Bar and all commands return "not found" error.
What Should Happen?
The extension should activate normally and show the Claude Code icon in the Activity Bar.
Error Messages/Logs
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 Module.createRequire (node:internal/modules/cjs/loader:1922:13)
at Object.<anonymous> (c:\Users\waqar\.vscode\extensions\anthropic.claude-code-2.1.129-win32-x64\extension.js:102:5407)
Steps to Reproduce
- Have Claude Code extension on Windows
- Extension auto-updates to v2.1.129
- Reload VS Code window
- Extension fails to activate - icon missing, all commands not found
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.123
Claude Code Version
2.1.129 (Claude Code)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
The extension.js contains a hardcoded Linux build path which breaks on Windows. VS Code version: 1.118.1 x64
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗