Windows: Extension activation fails with hardcoded Linux path in v2.1.129
Resolved 💬 3 comments Opened May 6, 2026 by bokbrother1 Closed May 6, 2026
Summary
Claude Code VS Code extension v2.1.129 fails to activate on Windows due to a hardcoded Linux CI build path in the bundled code.
Error
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'.
Symptoms
- Clicking the Claude Code logo button in VS Code throws:
command 'claude-vscode.editor.openLast' not found - No Claude Code conversation window opens
- All Claude Code commands are unregistered because the extension never activates
Root Cause
The extension bundle references a hardcoded Linux CI path (file:///home/runner/work/claude-cli-internal/claude-cli-internal/build-agent-sdk/sdk.mjs) that does not exist on Windows. This causes extension activation to fail entirely, leaving all commands unregistered.
Environment
- OS: Windows 11 Home 10.0.26200
- VS Code extension version: 2.1.129 (win32-x64)
- Extension ID: anthropic.claude-code-2.1.129-win32-x64
Workaround
Downgrade to v2.1.128 via Extensions panel > Install Another Version.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗