[BUG] Claude Code 2.1.53 fails to activate on Windows - hardcoded Linux path in extension.js

Status Fixed / completed
Reported on v2.1.53
Maintainer reply None cached
Activity 5 comments · opened Feb 25, 2026 · closed Feb 25, 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?

Bug: Claude Code 2.1.53 fails to activate on Windows due to hardcoded Linux path

Version: anthropic.claude-code-2.1.53-win32-x64

OS: Windows

Description:
The extension fails to activate on Windows with the following 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'

It appears the extension was built on a Linux CI/CD runner and a hardcoded Linux path (/home/runner/work/...) was embedded into extension.js. This path is invalid on Windows, causing the extension to crash immediately on activation.

As a result, all chat sessions fail to load and the extension is completely non-functional on Windows.

Steps to reproduce:

  1. Install Claude Code 2.1.53 on Windows
  2. Open VSCode
  3. Extension fails to activate

Expected behavior: Extension activates normally.

Actual behavior: Extension crashes with the Linux path error above. All chat sessions show "Error providing chat sessions: Canceled".

What Should Happen?

Expected behavior:
The extension should activate successfully on Windows and all chat sessions should load normally.

Error Messages/Logs

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.53-win32-x64\extension.js:45:4882)

Steps to Reproduce

Install Claude Code 2.1.53 (anthropic.claude-code-2.1.53-win32-x64) on Windows
Open VSCode
Open any Claude chat session
Extension fails to activate – chat sessions never load

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.53

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

5 Comments

shawnm-anthropic · 6 months ago

Hi, thanks for reporting. We just released v2.1.55 which should fix this.

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/28388
  2. https://github.com/anthropics/claude-code/issues/28375
  3. https://github.com/anthropics/claude-code/issues/28387

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

CTJaeger · 6 months ago
Hi, thanks for reporting. We just released v2.1.55 which should fix this.

v2.1.55 still contains the same bug. The hardcoded Linux path is still present in extension.js:
Received 'file:///home/runner/work/claude-cli-internal/claude-cli-internal/build-agent-sdk/sdk.mjs'
at Object.<anonymous> (c:\Users\[USERNAME]\.vscode\extensions\anthropic.claude-code-2.1.55-win32-x64\extension.js:45:4848)
Still broken on Windows.

futuremotiondev · 6 months ago
Hi, thanks for reporting. We just released v2.1.55 which should fix this.

Adding to the pile, still happening on 2.1.55. Need to get work done...

Please re-open and/or fix!

github-actions[bot] · 5 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.