Crashes on selecting "Run in WSL"

Resolved 💬 6 comments Opened Nov 6, 2025 by nextonphotos Closed Nov 11, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

VSCode extension version 0.4.35

What subscription do you have?

Plus

Which model were you using?

gpt-5

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I installed WSL and selected "Run in WSL" under "Settings"->"IDE Settings" in the Codex panel in VSCode. This results in a crash with the following:

Codex crashed with the following error: Codex app-server process exited with code 127 and signal null. Most recent error message: /usr/bin/env: ‘/mnt/d/Google’: No such file or directory

I assume the issue is related to the fact that the VSCode workspace I'm using is in a subfolder of a "Google Drive" folder, which contains a space. Changing the file structure isn't viable in this case, so is there a workaround to get this working? In any case, such situations shouldn't crash the extension.

What steps can reproduce the bug?

I selected "Run in WSL" under "Settings"->"IDE Settings" in the Codex panel in VSCode.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 9 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #6068

Powered by Codex Action

hsiktas · 9 months ago

I am seeing a similar issue where running it in WSL2 shows that error if the file path contains a space. In the VSCode settings, I had to uncheck the chatgpt.runCodexInWindowsSubsystemForLinux toggle to get the extension unstuck from this state.

dylan-hurd-oai contributor · 9 months ago

@hsiktas @nextonphotos we've fixed a few bugs here in the latest pre-release 0.5.39. Please let us know if you're still experiencing issues on that version.

hsiktas · 9 months ago

Just switched to the pre-release version of the extension, and I can't reproduce the issue anymore. 👍

dylan-hurd-oai contributor · 9 months ago

Thanks for confirming! This is now shipped to mainline release in 0.4.39.

JQMIND · 9 months ago
Thanks for confirming! This is now shipped to mainline release in 0.4.39.

no,i get this error:Codex crashed with the following error:

Codex process errored: Codex process is not available.