WSL agent commands fail to spawn

“However, the Codex agent cannot execute commands in the same workspace.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/11099/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Fading. No reports and thumbs-up in the last 7 days and 1 the week before, down from 44 a week at the late-September peak. A workaround is known.

Agent commands fail to spawn in WSL agent environment. Every command, even pwd or shell builtins, fails before execution on Windows desktop while the integrated WSL terminal works.

Is this your bug?

File my report

Where: Windows desktop app
Error text: Failed to create unified exec process: No such file or directory (os error 2)Pasted in 4 reports
exec_command failed: CreateProcess { message: "Rejected(\"Failed to create unified exec process: No such file or directory (os error 2)\")" }Pasted in 5 reports
message: "Rejected(\"Failed to create unified exec process: No such file or directory (os error 2)\")"Pasted in 3 reports
Versions: 0.159.2 to 26.1007.71326
Platforms: Windows
How bad: Some reports say it used to work. Some reports say it blocks them completely.

Part of: WSL agent cannot run commands3 bugs

node_repl rejects Linux cwd3 people
exec_command fails with os error 216 people

Not quite your bug?

Project creation fails in WSL5 people
Sandbox fails on WSL UNC paths4 people

Original reports18, newest first

Oct 14, 2026Windows/WSL: missing codex-linux-sandbox still blocks commands in Desktop 26.1007.71326 after #49731 was closedOn GitHub#54063
Oct 14, 2026Codex Desktop for Windows: WSL execution failureOn GitHub#54005
Oct 13, 2026Windows ChatGPT Codex App: WSL agent exec_command fails with CreateProcess os error 2On GitHub#53716
Oct 12, 2026Codex Desktop WSL2 agent fails to spawn any command — OS error 2, while native WSL worksOn GitHub#53289
Oct 10, 2026Windows/WSL: agent commands fail with ENOENT and existing chats cannot resume (missing source rollout)On GitHub#52961
Oct 10, 2026ChatGPT Desktop (Windows) regression: Codex chat command runner fails in WSL2 projects opened via \\wsl$ (CreateProcess os error 2)On GitHub#52841
Oct 3, 2026Windows desktop + Arch Linux WSL2: multiple chats lose codex-linux-sandbox arg0 helperOn GitHub#50689
Oct 2, 2026WSL sandbox blocked by missing arg0 launcher, then missing bubblewrap (verified recovery)On GitHub#50347
Oct 1, 2026Windows/WSL2: sandboxed execution fails because temporary codex-linux-sandbox launcher is missingOn GitHub#50078
Oct 1, 2026WSL2 sandbox commands fail with “No such file or directory”On GitHub#50025

Show all 18Show only the newest 10

Oct 1, 2026Windows/WSL: Agent tools fail with process creation and workspace URI errorsOn GitHub#49980
Oct 1, 2026Windows + WSL: agent shell execution fails with os error 2 after desktop app updateOn GitHub#49904
Oct 1, 2026Windows app: shell and Node REPL tools fail with a WSL workspace pathOn GitHub#49897
Sep 30, 2026Windows app 26.928.21956: WSL sandbox fails with No such file or directory (os error 2)On GitHub#49789
Sep 30, 2026[Windows][WSL2] Desktop tools fail to spawn processes despite a working WSL environment and standalone Codex CLIOn GitHub#49777
Sep 30, 2026Windows app with "Run agent in WSL": every command fails with "Failed to create unified exec process: No such file or directory" (arg0 helper dir deleted by Windows exec-server)On GitHub#49731
Sep 30, 2026Codex desktop on Windows cannot execute agent commands in a WSL repositoryOn GitHub#49630
Sep 29, 2026Windows desktop with WSL selected: exec_command cannot create any process after restart; node_repl rejects WSL cwdOn GitHub#49400