[BUG] The VS Code plugin version 2.1.3 fails when executing certain compilation commands using Bash.

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?

When using Windows 10 in the VS Code plugin, if the model executes the project's compilation command through Bash, it will prompt that the path cannot be found, but in fact, the file path exists. Here is the error prompt when executing:

Error Message: Path not found. At file: e:\project\test\entry

* Try the following:
  > Please check field: modules in file: e:\project\test\build-profile.json5.

Using the latest CLI will also have this problem.
It also worked fine when I used the previous version of the VS Code plugin.
It is initially judged that the problem is caused by the plugin's incorrect handling of \ and / in Bash.

What Should Happen?

Hope the Bash of the plugin can work properly.

Error Messages/Logs

Steps to Reproduce

1. In Windows 10, use the VS Code plugin of version V2.1.3
2. Let the model execute a compilation command or other files that involve the / in Windows paths
3. The execution result reports an error, similar to the following result:

• Try the following:

> Please check field: modules in file: e:\project\test\build-profile.json5.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.3

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_