Claude Code / AI Coding Tools

Claude Code VS Code Extension Fails to Activate on Windows — Hardcoded Linux Path

Fix Claude Code VS Code extension that fails to activate with a TypeError about filename path on Windows Includes evidence for Claude Code troubleshooting demand.

Source-backed Last updated May 11, 2026 2 sources Needs local verification

Category: AI Coding Tools
Error signature: 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'
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 11, 2026
Verification status: Source-backed
Evidence: 2 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Claude Code, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

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' is a Claude Code failure pattern reported for developers trying to fix claude code vs code extension that fails to activate with a typeerror about filename path on windows. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Multiple GitHub issues (57503, 57495) report the same activation failure on Windows since v2.1.136. Error traces show hardcoded Linux CI build path leaking into the Windows extension bundle. Multiple users confirm the issue started around 2026-05-08.

Common causes

Developers installing Claude Code v2.1.136+ in VS Code on Windows get an immediate activation failure due to a hardcoded Linux build path (file:///home/runner/work/...) embedded in extension.js. The extension becomes completely unusable, blocking paid subscribers from using the tool in their IDE.
Multiple GitHub issues (57503, 57495) report the same activation failure on Windows since v2.1.136. Error traces show hardcoded Linux CI build path leaking into the Windows extension bundle. Multiple users confirm the issue started around 2026-05-08.

Quick fixes

Confirm the exact error signature matches 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'.
Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match 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' exactly before applying the quick fix.
Compare the failing environment with Claude Code versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does 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' mean in Claude Code?

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' indicates the workflow described by "Claude Code VS Code Extension Fails to Activate on Windows — Hardcoded Linux Path" failed in a AI Coding Tools context. Start by confirming the exact signature and the component that emitted it.

What should I check first for 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'?

Check whether this cause matches your environment: Developers installing Claude Code v2.1.136+ in VS Code on Windows get an immediate activation failure due to a hardcoded Linux build path (file:///home/runner/work/...) embedded in extension.js. The extension becomes completely unusable, blocking paid subscribers from using the tool in their IDE.

Is the 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' guidance source-backed?

The "Claude Code VS Code Extension Fails to Activate on Windows — Hardcoded Linux Path" page is labeled source-backed. It has 2 public source URLs from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for 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'?

For "Claude Code VS Code Extension Fails to Activate on Windows — Hardcoded Linux Path", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging 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'?

For "Claude Code VS Code Extension Fails to Activate on Windows — Hardcoded Linux Path", collect the failing Claude Code command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.