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
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
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_
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
This was fixed in
0.122.0- please let me know if you are still hitting this issue!I'm seeing the issue will follow up
Getting this for 0.128.0 on Ubuntu 24
<img width="1116" height="309" alt="Image" src="https://github.com/user-attachments/assets/0be4d59e-122d-411d-af73-c6409f623c97" />
Distributor ID: Ubuntu
Description: Ubuntu 24.04.4 LTS
Release: 24.04
Codename: noble