Agent edits resulting in "command failed; retry without sandbox?"

Not sure if the thread id was automatically added here, but it's 019c995e-593d-7b13-bd39-b97a9f7409c9

Looks like the github issue link I was given by codex does not set the template to bug report and include the thread Id like it should have: When I enter this link I just get a blank template
• Feedback uploaded. Please open an issue using the following URL:

https://github.com/openai/codex/issues/new?template=2-bug-report.yml&steps=Uploaded%20thread:%20019c995e-593d-7b13-bd39-b97a9f7409c9

Or mention your thread ID 019c995e-593d-7b13-bd39-b97a9f7409c9 in an existing issue.
<img width="1086" height="132" alt="Image" src="https://github.com/user-attachments/assets/2c40c78e-28bd-4be0-9008-58639addf0b6" />

Is this a known issue?

Update: The issue mas magically and mysteriously dissapeared. I won't close this issue because I still think it should have logged a clearer error message as to why it failed, so I would have been able to resolve this myself without a miracle.

"command failed" is not a clear enough error message.

I have this exact issue. Codex CLI on Windows 11. It keeps failing to edit a file and asks permission to try without sandbox. Every time I select Always and it still asks again for the same file next edit.

This is happening for me in Ubuntu 24.04 cli since today's update. using full permission via /permissions does not help
Downgrading to v0.114.0 solved this issue for me. I believe there are some degrations in 0.115.0.

Edit: v0.116.0 fixed this issue for me. but this version requires bubblewrap to be enabled (it is now enabled default if /usr/bin/bwrap is available).

Agree with comment above. It is happening for me too, in Ubuntu 24.04 since 0.115.0

Exact same issue since Ubuntu 24.04 0.115.0

Got the same issue on Ubuntu 25.10 starting with 0.115.0 - this makes Codex pretty much unusable right now.

Yes, Ubuntu has also recently experienced sandbox failures

Same on Ubuntu 24.04 0.116.0

Also encountering this and downgrading to v0.114.0.

I encountered the same issue in a docker container (ubuntu 22.04) without privileged mode. Resolved by setting:

[features]
use_legacy_landlock = true

This should be fixed in 0.117.0.

Works great in my setup now (Ubuntu 25.10), thanks @etraut-openai!

I tried on 0.117 and it was still asking for approval for each command on Kubuntu for me. Maybe even more approval requests because it started to ask approval to run Chrome MCP, which was not like that on 0.116.
Checking the /status, I've noticed │ Permissions: Custom (workspace-write, on-request) │, which I never changed and I used /permissions to set │ Permissions: Default │
.
However, even after restarting the codex cli it asks for a permission to edit files in the same workspace. I tried using 'yes and don't ask again', but it didn't help

Same here 0.117 doesnt work ootb (works with use_legacy_landlock)
(reopen?)

it is not fixed, on 0.117. It only works with the use_legacy

This issue still appears to be reproducible on my setup with a newer version.

Version

codex-cli 0.117.0

Environment

Linux Ubuntu 24.04.3 LTS
Kernel: 6.14.0-37-generic
bwrap: 0.9.0

Behavior

With `codex --sandbox workspace-write`

• File creation/edit fails
• Shell commands fail before execution
• Error:

`• I couldn’t modify test.txt because the workspace sandbox is failing before any edit command runs. Both shell and patch attempts are blocked with bwrap:
loopback: Failed RTM_NEWADDR: Operation not permitted, so no changes were made. `

With `codex --sandbox danger-full-access `

→ Everything works normally (file writes, edits, commands)

Still the same problem, on 0.117. Xubuntu 24.04. I had to downgrade to 0.114 again @etraut-openai

FYI I also still have the same problem, @etraut-openai (on Ubuntu 24.04)

Its broken since 0.115, @etraut-openai please reopen.

I'm going to close this issue (and lock it) because it's conflating a bunch of different issues. If you're experiencing this, please look for other active bug reports or open a new one and provide the information requested in the bug template.