[VS Code Extension] v2.1.129 fails to activate on Windows — hardcoded Linux CI path in extension.js

Resolved 💬 6 comments Opened May 6, 2026 by greentourn Closed May 6, 2026

Bug Report

Extension version: 2.1.129 (win32-x64)
Platform: Windows 11 (win32-x64)
VS Code version: Latest
CLI version: 2.1.129 (npm-global)

Description

The Claude Code VS Code extension v2.1.129 fails to activate on Windows. The extension host throws a TypeError because extension.js attempts to load a file using a hardcoded Linux CI build path instead of a resolved Windows path.

Error (from VS Code Extension Host log)

2026-05-06 11:17:18.233 [error] Activating extension Anthropic.claude-code failed due to an error:
2026-05-06 11:17:18.233 [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 Object.<anonymous> (c:\Users\Acer\.vscode\extensions\anthropic.claude-code-2.1.129-win32-x64\extension.js:102:5407)

Impact

  • The extension does not activate at all on Windows
  • No Claude Code log appears in the Extension Host output (unlike all other extensions)
  • The command claude-vscode.terminal.open is never registered, so any attempt to open Claude Code from VS Code shows: command 'claude-vscode.terminal.open' not found
  • CLI (claude command) works fine — this is purely a VS Code extension packaging issue

Root Cause

extension.js contains a reference to a Linux CI build path:

file:///home/runner/work/claude-cli-internal/claude-cli-internal/build-agent-sdk/sdk.mjs

This path is only valid in the GitHub Actions runner environment and is not resolved to an absolute Windows path in the packaged extension.

Workaround

Downgrading to v2.1.119 (the previous stable version) resolves the issue.

Steps to Reproduce

  1. Install or auto-update to Claude Code VS Code extension v2.1.129 on Windows
  2. Open VS Code
  3. Try to open Claude Code chat/terminal
  4. Observe: command 'claude-vscode.terminal.open' not found
  5. Check Extension Host log → see the TypeError above

Additional Info

  • claude doctor shows CLI is healthy (v2.1.129, npm-global)
  • The .obsolete file in the extensions directory confirms the pattern of frequent Claude Code extension updates
  • Extension was released approximately 3 hours before this bug was reported

View original on GitHub ↗

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