[BUG] VS Code extension fails to activate on Windows - hardcoded Linux path

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

VS Code extension fails to activate on Windows.
Developer Tools console shows:

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 path is hardcoded as a Linux path and does not work on Windows.

What Should Happen?

The VS Code extension should activate successfully on Windows and the Claude Code panel should be usable.

Error Messages/Logs

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'

Steps to Reproduce

  1. Install Claude Code VS Code extension (v2.1.129) on Windows 11
  2. Install Claude CLI via npm
  3. Open VS Code
  4. Open Developer Tools (Help > Toggle Developer Tools)
  5. See error in Console tab

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.101 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

VS Code version: 1.118.1
Extension version: 2.1.129
Claude CLI version: 2.1.101

Claude CLI works fine from command line (claude --version outputs correctly).
The extension panel shows "CLAUDE CODE" tab but displays "No active session".
Changing "Claude Process Wrapper" setting to the npm path did not resolve the issue.

View original on GitHub ↗

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