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

Open
#37,594 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
macos, rust
Domain
cli, desktop

Research direction

Reproduce the failure in the macOS Codex Desktop app using a trivial exec command such as echo ok, then inspect ~/.codex/logs_2.sqlite for the execution error and authentication context. Compare the Desktop app behavior with the installed codex-cli and verify that shell commands execute successfully without the unified exec process error.

Written by the indexing model from the issue text.

Description

app bug tool-calls
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

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.