Sandboxes on WSL don't allow you to run VScode remote
Open
Nobody has claimed this yet.
area:permissions
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
Describe the bug
When I try to run ! code . with the /sandbox enable I get:
Shell code . (sandboxed) 2 lines
/mnt/c/Users/user/AppData/Local/Programs/Microsoft VS Code/bin/code: 42: wslpath: not found
/mnt/c/Users/user/AppData/Local/Programs/Microsoft VS Code/bin/code: 62: /mnt/c/Users/user/AppData/Local/Programs/Microsoft VS Code/Code.exe: not found
I then added that path to the sandbox configuration via /sandbox config and it still fails.
If I run /sandbox disable it works.
Affected version
GitHub Copilot CLI 1.0.81-6
Steps to reproduce the behavior
/sandbox enable
! code .
Expected behavior
I should be able to run VScode after configuring additional filesystem code
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with /sandbox enable followed by ! code . in WSL, then compare the sandbox configuration from /sandbox config with the VS Code code launcher errors for wslpath and Code.exe. Done means ! code . launches VS Code successfully while the sandbox remains enabled after the required filesystem configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell, vscode
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100