Codex keeps asking "retry without sandbox" even when the file edit already succeeded

Resolved 💬 5 comments Opened Apr 16, 2026 by psvmhw Closed Apr 22, 2026

What version of Codex CLI is running?

Codex CLI 0.121.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.4-codex

What platform is your computer?

_No response_

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

PowerShell to wsl

What issue are you seeing?

I saw the sandbox retry confirmation, but the file had already been updated.

What steps can reproduce the bug?

From the user point of view, the message says the command failed.

But the actual result is the opposite:

  • the command succeeded
  • the file changed
  • Codex still asked for confirmation as if it had failed

That makes the confirmation confusing and misleading.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

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