We're using codex:review as part of an automated code review pipeline. It works great in interactive claude sessions, but fails when invoked from claude --print (headless/non-interactive mode).
The issue is that the Codex sandbox (bwrap) requires namespace creation permissions that aren't available in containerized environments (Docker, Kubernetes). In interactive mode this can be worked around, but in --print mode there's no way to configure or bypass the sandbox.
Use case: We run claude --print in a Docker container to automate PR reviews. The pipeline calls codex:review to get a second opinion on diffs. Everything works except the sandbox step fails with a permissions error.
Ask: Could codex:review support running in environments where bwrap isn't available? For example, an option to skip sandboxing when the host is already sandboxed (running inside a container).
We're using codex:review as part of an automated code review pipeline. It works great in interactive claude sessions, but fails when invoked from claude --print (headless/non-interactive mode).
The issue is that the Codex sandbox (bwrap) requires namespace creation permissions that aren't available in containerized environments (Docker, Kubernetes). In interactive mode this can be worked around, but in --print mode there's no way to configure or bypass the sandbox.
Use case: We run claude --print in a Docker container to automate PR reviews. The pipeline calls codex:review to get a second opinion on diffs. Everything works except the sandbox step fails with a permissions error.
Ask: Could codex:review support running in environments where bwrap isn't available? For example, an option to skip sandboxing when the host is already sandboxed (running inside a container).