Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@feiskyer
Copy link
Member

@feiskyer feiskyer commented Aug 29, 2025

Summary

  • Fixes ambiguous WSL guidance that causes ENOENT errors in Remote-WSL setups
  • Replaces the current note with clear, separate instructions for two scenarios:
    • Windows host VS Code: Use "command": "wsl" to invoke WSL binaries
    • Remote-WSL (VS Code inside WSL): Use direct binary paths or bash wrapper
  • Adds troubleshooting section to help users identify their environment and resolve spawn errors

Background

The current README section (lines 313-325) suggests using "command": "wsl" for "VS Code running inside WSL environment", but this is misleading and causes the exact ENOENT error described in the issue. The wsl command is a Windows-side launcher that's not available inside the WSL environment when using the Remote-WSL extension.

Related Issues

Closes #190

- Replace ambiguous WSL note with clear guidance for two scenarios:
  * Windows host VS Code: Use "command": "wsl"
  * Remote-WSL (VS Code inside WSL): Use direct binary or bash wrapper
- Add troubleshooting section for ENOENT errors
- Prevent confusion that leads to spawn failures in Remote-WSL

Fixes #190
Copy link
Member

@gossion gossion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@feiskyer feiskyer added this pull request to the merge queue Aug 29, 2025
Merged via the queue into main with commit c800166 Aug 29, 2025
9 checks passed
@feiskyer feiskyer deleted the fix/readme-wsl-guidance-issue-190 branch August 29, 2025 05:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

README: ambiguous WSL guidance - using "wsl" in mcp.json can break Remote-WSL (ENOENT)

2 participants