codex-action now cannot get the git log/diff

[EveGoodEvening]

codex logs:

codex
I hit a sandbox execution issue (`bwrap: loopback ... Operation not permitted`) before git could run.

posted feedbacks by the action:

I can’t review this PR yet because command execution is blocked in this environment (`bwrap: loopback: Failed RTM_NEWADDR: Operation not permitted`), so I can’t run the required `git log/diff` range.

Please paste one of these and I’ll do a precise review immediately:
...

**Findings**
1. **Blocker: unable to inspect PR diff**  
   I could not run `git log`/`git diff` locally because all shell commands fail with `bwrap: loopback: Failed RTM_NEWADDR: Operation not permitted`, and direct GitHub fetches for the commit/compare pages also failed in this environment.  
   Without the actual patch, I can’t provide a reliable review of PR #10 changes.

1. **Blocker:** I can’t access the PR diff in this run, so I can’t produce a reliable review of PR #10 yet.  
   - Every local command fails with: `bwrap: loopback: Failed RTM_NEWADDR: Operation not permitted`
   - GitHub compare/API fetches were also unavailable from this environment.

I keep gettng this, even after I try using unprivileged user following https://github.com/openai/codex-action/blob/main/examples/unprivileged-user.yml

[EveGoodEvening]

it was working good yesterday, so I think it's caused by #74

[bolinfest]

Though were you using main as the tag instead of v1?

[bolinfest]

Because if not, it feels more likely that the https://github.com/openai/codex/releases/tag/rust-v0.115.0 release of the Codex CLI (since the action always takes the latest mainline Codex CLI release by default) is the thing that changed?

[EveGoodEvening]

I wasn't using main, I tried both v1 and v1.5

[EveGoodEvening]

Because if not, it feels more likely that the https://github.com/openai/codex/releases/tag/rust-v0.115.0 release of the Codex CLI (since the action always takes the latest mainline Codex CLI release by default) is the thing that changed?

I guess you make a point. I now add a

sandbox: danger-full-access

and it's now working

[EveGoodEvening]

feel free to close this and #78 if #77 is merged

[bolinfest]

@EveGoodEvening can you verify that v1 works for you now? I just published v1.6 and updated v1 to point to it.

[bolinfest]

Note you should not need danger-full-access anymore.

[EveGoodEvening]

Yeah I could verify that it now works! thank you