[BUG] VS Code extension v2.1.136 fails to activate on Windows: hardcoded Linux CI path regression
Resolved 💬 3 comments Opened May 8, 2026 by cjaramilla1 Closed May 9, 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?
The VS Code extension v2.1.136 fails to activate on Windows 11, making all claude-vscode.* commands unavailable. This is a regression of the same hardcoded Linux CI path bug previously reported and fixed, now reintroduced in v2.1.136.
Related closed issue: #56555
Environment
| Field | Value |
|---|---|
| Claude Code Extension | v2.1.136 (anthropic.claude-code) |
| OS | Windows 11 Pro |
| VS Code | 1.118.1 |
What Should Happen?
Extension activates correctly on Windows and all claude-vscode.* commands are available.
Error Messages/Logs
2026-05-08 13:38:26.697 [error] Activating extension Anthropic.claude-code failed due to an error:
2026-05-08 13:38:26.697 [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 Module.createRequire (node:internal/modules/cjs/loader:1922:13)
at Object.<anonymous> (c:\Users\crist\.vscode\extensions\anthropic.claude-code-2.1.136-win32-x64\extension.js:103:5579)
Steps to Reproduce
- Install Claude Code extension v2.1.136 on VS Code 1.118.1 (Windows 11 Pro)
- Open any project
- Open Command Palette and type
Claude - Observe: error
command 'claude-vscode.terminal.open' not found
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.133
Claude Code Version
2.1.136
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗