[BUG] VS Code extension v2.1.51 fails to activate on Windows due to hardcoded Linux path

Resolved 💬 4 comments Opened Feb 24, 2026 by 3110saito-t Closed Feb 24, 2026

Preflight Checklist

  • [ ] 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?

VS Code extension v2.1.51 fails to activate on Windows, causing command 'claude-vscode.terminal.open' not found when clicking the Claude icon.

The extension cannot activate because a Linux build path is hardcoded in the win32-x64 build of the extension.

What Should Happen?

The extension should activate successfully on Windows and open Claude Code when clicking the Claude icon.

Error Messages/Logs

2026-02-24 12:16:04.803 [error] Activating extension Anthropic.claude-code failed due to an 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:1915:13)
    at Object.<anonymous> (c:\Users\<username>\.vscode\extensions\anthropic.claude-code-2.1.51-win32-x64\extension.js:45:4602)

Steps to Reproduce

  1. Install Claude Code VS Code extension v2.1.51 on Windows 11
  2. Click the Claude icon in VS Code
  3. Error: command 'claude-vscode.terminal.open' not found appears
  4. Open Developer: Show Logs → Extension Host to confirm the activation error above

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.49

Claude Code Version

2.1.51

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Downgrading the extension to a previous version resolves the issue.
Extension can be downgraded via: Extensions panel → Claude Code → Install Another Version

View original on GitHub ↗

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