[BUG] Extension fails to activate on Windows - hardcoded Linux path in sdk.mjs (v2.1.129)

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

Version: 2.1.129 (win32-x64)
OS: Windows 11

Extension fails to activate with 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/bui
ld-agent-sdk/sdk.mjs'

The extension.js references a hardcoded Linux CI build path that
doesn't exist on Windows.
Fix: downgrading to 2.1.128 resolves the issue.

What Should Happen?

The extension should activate successfully on Windows without errors.
What happens instead: Extension fails to activate with a hardcoded
Linux CI build path that doesn't exist on Windows.

Error Messages/Logs

TypeError: The argument 'filename' must be a file URL object, file   
  URL string, or absolute path string. Received 'file:///home/runner/wo
  rk/claude-cli-internal/claude-cli-internal/build-agent-sdk/sdk.mjs'

Steps to Reproduce

  1. Install Claude Code VS Code extension version 2.1.129 (win32-x64)

on Windows

  1. Reload VS Code
  2. Extension fails to activate

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

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Downgrading to version 2.1.128 resolves the issue.

View original on GitHub ↗

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