Desktop app: all exec commands fail with "Failed to create unified exec process: No such file or directory (os error 2)"

Open 💬 0 comments Opened Aug 8, 2026 by tommywang0113

What version of the Codex App are you using (From “About Codex” dialog)?

Environment: - macOS, Codex Desktop app - Auth: API key in ~/.codex/config.toml (not ChatGPT login) - codex-cli 0.147.0 also installed via npm - System shell confirmed working: /bin/zsh -c 'echo ok' → ok Issue: Every exec_command fails with: Failed to create unified exec process: No such file or directory (os error 2) Even trivial commands fail (echo, date, ls, cat). Model chat works fine; only the command execution component is broken. Tried /bin/zsh, /bin/sh, login/non-login shells — same error. Reproduction: 1. Start a new thread in the desktop app 2. Ask the agent to run any shell command (e.g. "run: echo ok") 3. Error above appears immediately Tried and still broken: - Cmd+Q and reopen - Full uninstall (rm -rf /Applications/Codex.app), delete ~/Library/Application Support/Codex, ~/Library/Caches/Codex, ~/Library/LaunchAgents/codex - rm -rf ~/.codex/ipc/ (IPC sockets) - Fresh install + new thread Logs: Stored in ~/.codex/logs_2.sqlite (sqlite). No file-based logs at ~/.codex/log/. Note: logs show repeated INFO "remote control requires ChatGPT authentication; API key auth is not supported" — likely unrelated, but flagging since we use API key auth.

What subscription do you have?

Environment: - macOS, Codex Desktop app - Auth: API key in ~/.codex/config.toml (not ChatGPT login) - codex-cli 0.147.0 also installed via npm - System shell confirmed working: /bin/zsh -c 'echo ok' → ok Issue: Every exec_command fails with: Failed to create unified exec process: No such file or directory (os error 2) Even trivial commands fail (echo, date, ls, cat). Model chat works fine; only the command execution component is broken. Tried /bin/zsh, /bin/sh, login/non-login shells — same error. Reproduction: 1. Start a new thread in the desktop app 2. Ask the agent to run any shell command (e.g. "run: echo ok") 3. Error above appears immediately Tried and still broken: - Cmd+Q and reopen - Full uninstall (rm -rf /Applications/Codex.app), delete ~/Library/Application Support/Codex, ~/Library/Caches/Codex, ~/Library/LaunchAgents/codex - rm -rf ~/.codex/ipc/ (IPC sockets) - Fresh install + new thread Logs: Stored in ~/.codex/logs_2.sqlite (sqlite). No file-based logs at ~/.codex/log/. Note: logs show repeated INFO "remote control requires ChatGPT authentication; API key auth is not supported" — likely unrelated, but flagging since we use API key auth.

What platform is your computer?

_No response_

What issue are you seeing?

Environment:

  • macOS, Codex Desktop app
  • Auth: API key in ~/.codex/config.toml (not ChatGPT login)
  • codex-cli 0.147.0 also installed via npm
  • System shell confirmed working: /bin/zsh -c 'echo ok' → ok

Issue:
Every exec_command fails with:
Failed to create unified exec process: No such file or directory (os error 2)

Even trivial commands fail (echo, date, ls, cat). Model chat works fine;
only the command execution component is broken. Tried /bin/zsh, /bin/sh,
login/non-login shells — same error.

Reproduction:

  1. Start a new thread in the desktop app
  2. Ask the agent to run any shell command (e.g. "run: echo ok")
  3. Error above appears immediately

Tried and still broken:

  • Cmd+Q and reopen
  • Full uninstall (rm -rf /Applications/Codex.app), delete ~/Library/Application Support/Codex, ~/Library/Caches/Codex, ~/Library/LaunchAgents/codex
  • rm -rf ~/.codex/ipc/ (IPC sockets)
  • Fresh install + new thread

Logs:
Stored in ~/.codex/logs_2.sqlite (sqlite). No file-based logs at ~/.codex/log/.
Note: logs show repeated INFO "remote control requires ChatGPT authentication; API key auth is not supported" — likely unrelated, but flagging since we use API key auth.

What steps can reproduce the bug?

Environment:

  • macOS, Codex Desktop app
  • Auth: API key in ~/.codex/config.toml (not ChatGPT login)
  • codex-cli 0.147.0 also installed via npm
  • System shell confirmed working: /bin/zsh -c 'echo ok' → ok

Issue:
Every exec_command fails with:
Failed to create unified exec process: No such file or directory (os error 2)

Even trivial commands fail (echo, date, ls, cat). Model chat works fine;
only the command execution component is broken. Tried /bin/zsh, /bin/sh,
login/non-login shells — same error.

Reproduction:

  1. Start a new thread in the desktop app
  2. Ask the agent to run any shell command (e.g. "run: echo ok")
  3. Error above appears immediately

Tried and still broken:

  • Cmd+Q and reopen
  • Full uninstall (rm -rf /Applications/Codex.app), delete ~/Library/Application Support/Codex, ~/Library/Caches/Codex, ~/Library/LaunchAgents/codex
  • rm -rf ~/.codex/ipc/ (IPC sockets)
  • Fresh install + new thread

Logs:
Stored in ~/.codex/logs_2.sqlite (sqlite). No file-based logs at ~/.codex/log/.
Note: logs show repeated INFO "remote control requires ChatGPT authentication; API key auth is not supported" — likely unrelated, but flagging since we use API key auth.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗