fix: skip cmd.exe wrapping for MCP servers when Windows host connects to WSL #9740
+109
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
cmd.exe not foundwhen Windows VS Code connects to WSLresolveCommandForPlatform()wrapped batch commands (npx, uvx, etc.) withcmd.exeeven when connected to WSL remoteisWindowsHostWithWslRemotecheck (same pattern as PR fix: use ide.runCommand when Windows host connects to WSL #9679)Fixes #9151
Test plan
Related PRs
isWindowsHostWithWslRemotepattern🤖 Generated with Claude Code
Continue Tasks
Powered by Continue
Summary by cubic
Fixes MCP servers failing to start in WSL when VS Code on Windows connects to WSL by not wrapping batch commands with cmd.exe. WSL is now detected so Linux commands run directly.
Bug Fixes
Refactors
Written for commit 74095d9. Summary will update on new commits.