Codex CLI v0.141.0 crashes on Intel macOS x86_64 during first interactive file/shell tool action.

Open 💬 1 comment Opened Jun 19, 2026 by littlerebel85

What version of Codex CLI is running?

Codex CLI v0.141.0

What subscription do you have?

Plus

Which model were you using?

GPT-5.5

What platform is your computer?

macOS Intel x86_64

What terminal emulator and version are you using (if applicable)?

Terminal Version 2.14 (455.1)

Codex doctor report

not possible

What issue are you seeing?

Codex CLI v0.141.0 crashes on Intel macOS x86_64 during first interactive file/shell tool action.

Uploaded feedback thread:
019ee185-487e-7523-bbab-b08b22a9b452

Environment:

  • macOS Intel x86_64
  • Codex CLI v0.141.0
  • Account authenticates successfully
  • Chat-only prompts work
  • /status works
  • /hooks shows 0 installed, 0 active
  • MCP appears clean
  • Reproduced with standalone install and npm install

Repro:

  1. Launch codex
  2. Send a chat-only prompt like “Say hello only”
  3. It works
  4. Send a file/tool prompt like “List the files in this folder only”
  5. Codex crashes with zsh: trace trap codex

Additional diagnostics:

  • codex sandbox --log-denials -- /bin/ls -la "$HOME" works
  • Sandbox denials: none found
  • codex --sandbox danger-full-access --ask-for-approval untrusted still crashes on the first file listing request

Expected:
Codex should execute the file listing or ask for approval.

Actual:
Codex exits to zsh with trace trap.

What steps can reproduce the bug?

Uploaded thread: 019ee185-487e-7523-bbab-b08b22a9b452

What is the expected behavior?

Expected behavior:
When I ask Codex CLI to list files in the current folder, Codex should either execute the file listing successfully or ask for permission if approval is required. The interactive CLI should remain open and should not crash or exit to zsh.

Actual behavior:
Codex exits immediately with zsh: trace trap codex on the first local file/shell tool action.

Additional information

Uploaded feedback thread:
019ee185-487e-7523-bbab-b08b22a9b452

This started immediately after accepting the upgrade to Codex CLI v0.141.0.

Environment:

  • macOS on Intel x86_64
  • Codex CLI v0.141.0
  • uname -m returns x86_64
  • command -v codex pointed to /Users/heatherpratt/.local/bin/codex with the standalone install
  • The binary was Mach-O 64-bit executable x86_64
  • I also reproduced the crash after switching to the npm install at /Users/heatherpratt/.npm-global/bin/codex

What works:

  • Codex opens
  • Authentication works
  • Chat-only prompts work
  • /status works
  • /hooks shows 0 installed and 0 active
  • codex sandbox --log-denials -- /bin/ls -la "$HOME" works
  • Sandbox denials reported: none found

What fails:

  • The first interactive local file/shell tool action crashes Codex
  • Reproduced in a normal folder and in a clean empty folder
  • Reproduced even with:

codex --sandbox danger-full-access --ask-for-approval untrusted

Crash message:
zsh: trace trap codex

This does not appear to be project-specific, MCP-specific, hook-related, or caused by sandbox denials.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗