Desktop Codex command runner fails for all shell commands with exit code 134, while Codex CLI works normally

Resolved 💬 0 comments Opened Jun 19, 2026 by scottgallant Closed Jun 20, 2026

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

26.616.32156

What subscription do you have?

Pro

What platform is your computer?

Darwin 23.4.0 arm64 arm

What issue are you seeing?

In Codex Desktop, shell commands fail immediately with exit code 134 and no stderr output. File editing still works, but the command runner appears broken.

The same project works correctly in Codex CLI.

What steps can reproduce the bug?

  1. Open Codex Desktop (version 26.616.32156).
  2. Open any workspace
  3. Ensure sandbox mode is workspace-write.
  4. Start a fresh chat/session.
  5. Prompt: Run pwd
  6. Observe that the command runner fails: pwd failed in the tool with exit code 134 and no output.

What is the expected behavior?

_No response_

Additional information

  1. Open Codex Desktop (version 26.616.32156).
  2. Open any workspace
  3. Ensure sandbox mode is workspace-write.
  4. Start a fresh chat/session.
  5. Prompt: Run pwd
  6. Observe that the command runner fails:

pwd failed in the tool with exit code 134 and no output.

View original on GitHub ↗