Rank, 14 days: 247 on the Codex sheet
81 people reported
All time, since Sep 29, including 60 thumbs-up on GitHub.
WSL agent cannot run commands
“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/themes/122/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
3 bugs in this theme
- WSL agent commands fail to spawnHas a workaround70 people
- exec_command fails with os error 2Has a workaround16 people
- node_repl rejects Linux cwdNo workaround yet3 people
What's included
- exec_command fails with "Failed to create unified exec process: No such file or directory (os error 2)", even for pwd
- WSL terminal and standalone CLI work while the desktop agent fails
- node_repl/js tool rejects the Linux working directory: "sandboxCwd is not a local file URI"
- Missing codex-linux-sandbox helper under the Windows-backed .codex path
Not included
- Creating a project fails when WSL mode is on
- Windows-native agent failing on a WSL UNC workspace during sandbox setup
Original reports22, newest first
- Windows/WSL: missing codex-linux-sandbox still blocks commands in Desktop 26.1007.71326 after #49731 was closedOn GitHub#54063
- Codex Desktop for Windows: WSL execution failureOn GitHub#54005
- Windows ChatGPT Codex App: WSL agent exec_command fails with CreateProcess os error 2On GitHub#53716
- Codex Desktop WSL2 agent fails to spawn any command — OS error 2, while native WSL worksOn GitHub#53289
- [Windows/WSL] node_repl rejects Linux sandboxCwd on Desktop 26.1007.21434 after shell launcher recoveryOn GitHub#53288
- Windows + WSL: node_repl rejects Linux cwd, primary runtime catalog mismatch and slow chat initializationOn GitHub#53190
- Windows/WSL: agent commands fail with ENOENT and existing chats cannot resume (missing source rollout)On GitHub#52961
- ChatGPT Desktop (Windows) regression: Codex chat command runner fails in WSL2 projects opened via \\wsl$ (CreateProcess os error 2)On GitHub#52841
- Windows desktop + Arch Linux WSL2: multiple chats lose codex-linux-sandbox arg0 helperOn GitHub#50689
- WSL sandbox blocked by missing arg0 launcher, then missing bubblewrap (verified recovery)On GitHub#50347
Show all 22Show only the newest 10
- Windows/WSL2: sandboxed execution fails because temporary codex-linux-sandbox launcher is missingOn GitHub#50078
- WSL2 sandbox commands fail with “No such file or directory”On GitHub#50025
- Windows/WSL: Agent tools fail with process creation and workspace URI errorsOn GitHub#49980
- Windows Desktop WSL unified_exec_startup fails with ENOENT even with valid Linux-native cwd and bashOn GitHub#49969
- Windows + WSL: agent shell execution fails with os error 2 after desktop app updateOn GitHub#49904
- Windows app: shell and Node REPL tools fail with a WSL workspace pathOn GitHub#49897
- Windows app 26.928.21956: WSL sandbox fails with No such file or directory (os error 2)On GitHub#49789
- [Windows][WSL2] Desktop tools fail to spawn processes despite a working WSL environment and standalone Codex CLIOn GitHub#49777
- Windows 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
- Codex desktop on Windows cannot execute agent commands in a WSL repositoryOn GitHub#49630
- Windows desktop with WSL selected: exec_command cannot create any process after restart; node_repl rejects WSL cwdOn GitHub#49400
- Codex Desktop: exec_command fails in WSL-style session with os error 2, including pwd in /tmp, after restartOn GitHub#49365