Overeager assumption of sandbox error

Resolved 💬 4 comments Opened Oct 7, 2025 by corrylc Closed Oct 9, 2025

What version of Codex is running?

codex-cli 0.45.0

Which model were you using?

gpt-5-codex high

What platform is your computer?

Darwin 25.0.0 arm64 arm

What steps can reproduce the bug?

Ask codex to "run bash -c false"

What is the expected behavior?

Command is interpreted as "failing" (i.e. returns an error code) but isn't attributed to the sandbox.

What do you see instead?

• Ran bash -c false
  └ failed in sandbox:

Additional information

This is a reduction of the more complicated case I see, where some testing triggers this behavior. I tried to come up with the most basic test case that plainly can't be caused by the sandbox/seatbelt.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗