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

Environment

• Platform (select one):
• [√] Anthropic API
• [ ] AWS Bedrock
• [ ] Google Vertex AI
• [ ] Other: <!-- specify -->
• 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

1. Navigate to a Rust project directory: d:\Dev\revm\crates\revm-ssa-graph\src\engine\handler\
2. Run Claude Code in the project
3. Attempt to update/edit the file frame.rs
4. 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