[BUG] VSCode Extension Doesn't Work Well When on Windows

Status Closed — not planned

Maintainer reply None cached

Activity 13 comments · opened Jul 12, 2025 · closed Jan 4, 2026

Environment

Platform (select one):
[√] Anthropic API
[ ] AWS Bedrock
[ ] Google Vertex AI
[ ] Other:
Claude CLI version: 1.0.51
Operating System: Windows 11
Terminal: Command Prompt/PowerShell

Bug Description

Claude Code fails to open/access Rust source files with a file path encoding error. The error message appears in Chinese, suggesting an encoding issue when handling Windows file paths. The tool cannot parse the file path correctly, resulting in "unable to parse file system provider with relative file path" error.

Steps to Reproduce

Navigate to a Rust project directory: d:\Dev\revm\crates\revm-ssa-graph\src\engine\handler\
Run Claude Code in the project
Attempt to update/edit the file frame.rs
Observe the file path parsing error

Expected Behavior

Claude Code should successfully open and edit the frame.rs file without path encoding issues, regardless of the Windows file path format.

Actual Behavior

Claude Code throws an error:

Error: cannot open _claude_fs_right:d%3A%5CDev%5Crevm%5Ccrates%5Crevm-ssa-graph%5Csrc%5Cengine%5Chandler%5Cframe.rs. Detail: unable to parse file system provider with relative file path "_claude_fs_right:d:\Dev\revm\crates\revm-ssa-graph\src\engine\handler\frame.rs"

The error stack trace shows:

node:internal/process/promises:394
triggerUncaughtException(err, true /* fromPromise */);
Multiple references to @anthropic-ai/claude-code/cli.js

Additional Context

The error message is displayed in Chinese, which may indicate a locale/encoding issue
The file path is being URL-encoded (%3A for :, %5C for \)
This appears to be a Windows-specific path handling issue
The error occurs when Claude Code tries to access files in deeply nested directory structures
Project is a Rust codebase with standard Cargo project structure
The file frame.rs does exist at the specified location and is accessible through other editors

Possible root causes:

Windows path separator handling
URL encoding/decoding of file paths
Locale/encoding settings affecting error message display
File system provider path resolution issues

View original on GitHub ↗

13 Comments

marcous83 · 1 year ago

I'm currently experiencing the exact same issue. This currently keeps me from using Claude-code in VSCode as it constantly crashes.

semih1468 · 1 year ago

I'm encountering this error after installing the Claude Code extension.

ojovirtual · 1 year ago

Same here, it looks something to do with Windows path separator.

raziel5746 · 1 year ago

Exact same issue here

KOP2020 · 1 year ago

itsjmendez · 1 year ago

patrickiel · 1 year ago

Running VSCode as Admin fixes this error for me

kongqy · 1 year ago

Same here, it looks something to do with Windows path separator. Same here, it looks something to do with Windows path separator. 这里也一样，看起来与Windows路径分隔符有关。

Similarly, the situation is the same in a pure WSL environment on Windows systems

MatheusTrinca · 1 year ago

its fixed

kongqy · 1 year ago

its fixed

emmmmm......

It seems there's still an issue here.

@anthropic-ai/claude-code: 1.0.57
Claude Code for VSCode: 1.0.56

After entering claude, execute '/init' after connecting to the ide tool with the '/ide' command

error:

node:internal/process/promises:394
    triggerUncaughtException(err, true /* fromPromise */);
    ^

Error: Failed to construct 'URL': Invalid URL
    at oXB (file:///D:/Tools/NodeJS/node-v22.15.0-win-x64/node_modules/@anthropic-ai/claude-code/cli.js:1361:11459)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Y38 (file:///D:/Tools/NodeJS/node-v22.15.0-win-x64/node_modules/@anthropic-ai/claude-code/cli.js:2735:11206)
    at async J (file:///D:/Tools/NodeJS/node-v22.15.0-win-x64/node_modules/@anthropic-ai/claude-code/cli.js:2735:9917)

Node.js v22.17.1

github-actions[bot] · 8 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

github-actions[bot] · 7 months ago

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.