Open in Cursor/VSCode from a WSL folder should invoke cursor / code from wsl
Open 💬 4 comments Opened Mar 6, 2026 by kendonB
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
26.304.1528.0
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Windows 11 x64
What issue are you seeing?
Clicking "open in" for VS Code (and descendants) from a WSL project should open the text editor from WSL, not from Windows. This will cause the text editor to use the WSL remote system.
What steps can reproduce the bug?
Click 'Open in' Cursor
What is the expected behavior?
_No response_
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
still not fixed
I’m also hitting this in Codex Desktop on Windows with WSL2 Ubuntu enabled.
Codex is running against a WSL workspace on the Linux filesystem. The top-bar “Open in VS Code” action opens the project in Windows VS Code instead of opening it in the Remote-WSL context.
VS Code Remote-WSL itself is configured correctly. Opening the same kind of workspace with a Remote-WSL folder URI works:
Start-Process code -ArgumentList '--folder-uri','vscode-remote://wsl+Ubuntu/home/<user>/<project>'
So the issue seems to be specifically Codex Desktop’s open-target behavior. For WSL workspaces, the VS Code target should launch a
vscode-remote://wsl+<distro>/...folder URI, or use an equivalentcode --remote wsl+<distro> ...invocation, instead of opening the folder as a Windows/local path.still not fixed