›_ Claude Code Issues
Claude Code Issues / #56613

Extension fails to activate on Windows — hardcoded Linux path in sdk.mjs

Resolved 💬 2 comments Opened May 6, 2026 by anandhaprabhuark 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?

---
Title:
Extension fails to activate on Windows — hardcoded Linux path in sdk.mjs

Body: ## Bug Report
### Description
The Claude Code VS Code extension fails to activate on Windows. All extension commands
(sidebar, new tab, openLast, etc.) throw "command not found" errors because the extension
never finishes activating.

### Error (from 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 extension appears to have a hardcoded Linux build path baked into it that does not
exist on Windows machines.

### Steps to Reproduce

  1. Install Claude Code VS Code extension v2.1.129 on Windows
  2. Open VS Code
  3. Open Developer Tools Console (Ctrl+Shift+P → Developer: Toggle Developer Tools)
  4. See activation failure error above
  5. All Claude commands fail with "command not found"

### Environment

  • OS: Windows 11 Pro 10.0.26200
  • VS Code Version: 1.118.1 (034f571d, x64)
  • Claude Code CLI Version: 2.1.129
  • Extension Version: 2.1.129 (win32-x64)
  • Shell: PowerShell (VS Code integrated terminal)

### Expected Behavior
Extension activates successfully and Claude panel/sidebar/terminal work inside VS Code.

### Actual Behavior

  • Extension stuck on "Activating" in Running Extensions list
  • All commands throw: Error: command 'claude-vscode.editor.openLast' not found
  • Sidebar, new tab, and all UI features non-functional

### Workaround
Claude CLI works fine outside VS Code (Windows Terminal / Git Bash).

What Should Happen?

err unable use claude

Error Messages/Logs

Steps to Reproduce

---
Title:
Extension fails to activate on Windows — hardcoded Linux path in sdk.mjs

Body: ## Bug Report
### Description
The Claude Code VS Code extension fails to activate on Windows. All extension commands
(sidebar, new tab, openLast, etc.) throw "command not found" errors because the extension
never finishes activating.

### Error (from 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 extension appears to have a hardcoded Linux build path baked into it that does not
exist on Windows machines.

### Steps to Reproduce

  1. Install Claude Code VS Code extension v2.1.129 on Windows
  2. Open VS Code
  3. Open Developer Tools Console (Ctrl+Shift+P → Developer: Toggle Developer Tools)
  4. See activation failure error above
  5. All Claude commands fail with "command not found"

### Environment

  • OS: Windows 11 Pro 10.0.26200
  • VS Code Version: 1.118.1 (034f571d, x64)
  • Claude Code CLI Version: 2.1.129
  • Extension Version: 2.1.129 (win32-x64)
  • Shell: PowerShell (VS Code integrated terminal)

### Expected Behavior
Extension activates successfully and Claude panel/sidebar/terminal work inside VS Code.

### Actual Behavior

  • Extension stuck on "Activating" in Running Extensions list
  • All commands throw: Error: command 'claude-vscode.editor.openLast' not found
  • Sidebar, new tab, and all UI features non-functional

### Workaround
Claude CLI works fine outside VS Code (Windows Terminal / Git Bash).

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

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

---
Title:
Extension fails to activate on Windows — hardcoded Linux path in sdk.mjs

Body: ## Bug Report
### Description
The Claude Code VS Code extension fails to activate on Windows. All extension commands
(sidebar, new tab, openLast, etc.) throw "command not found" errors because the extension
never finishes activating.

### Error (from 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 extension appears to have a hardcoded Linux build path baked into it that does not
exist on Windows machines.

### Steps to Reproduce

  1. Install Claude Code VS Code extension v2.1.129 on Windows
  2. Open VS Code
  3. Open Developer Tools Console (Ctrl+Shift+P → Developer: Toggle Developer Tools)
  4. See activation failure error above
  5. All Claude commands fail with "command not found"

### Environment

  • OS: Windows 11 Pro 10.0.26200
  • VS Code Version: 1.118.1 (034f571d, x64)
  • Claude Code CLI Version: 2.1.129
  • Extension Version: 2.1.129 (win32-x64)
  • Shell: PowerShell (VS Code integrated terminal)

### Expected Behavior
Extension activates successfully and Claude panel/sidebar/terminal work inside VS Code.

### Actual Behavior

  • Extension stuck on "Activating" in Running Extensions list
  • All commands throw: Error: command 'claude-vscode.editor.openLast' not found
  • Sidebar, new tab, and all UI features non-functional

### Workaround
Claude CLI works fine outside VS Code (Windows Terminal / Git Bash).

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗