nixos/slop-cannon: Fix Codex procfs fallback
Update docs / update (push) Successful in 1m0s
CI / Check, build and cache nixfiles (push) Successful in 48m35s

Restore the bubblewrap diagnostic expected by Codex so its existing
container fallback handles nspawn procfs restrictions.

Verified workspace writes succeed and outside writes are denied.
`check-system slop-cannon` passes.
This commit is contained in:
2026-11-16 01:01:18 +00:00
parent 9c508caeb5
commit 1f4d058ba4
2 changed files with 13 additions and 4 deletions
@@ -125,9 +125,9 @@ unprivileged user and the approval broker in front of the deploy key.
- Claude's managed settings (`/etc/claude-code/managed-settings.json`) repeat the `deny` rules and
disable bypass mode; agents can edit `~/.claude` but not `/etc`. The app still lists Bypass, but
choosing it fails.
- Codex stores its credentials in a file. Its command sandbox does not work inside nspawn yet:
bubblewrap can't mount a fresh `/proc` in the container, so every Codex command fails outside
full-access mode.
- Codex stores its credentials in a file. A bubblewrap diagnostic compatibility override enables
its existing nspawn fallback; deployed and verified directly and through a fresh Paseo session.
See [Codex sandbox in nspawn](../../../../../agents-remote.md#codex-sandbox-in-nspawn).
- Deploys and `ssh-machine` access are meant to go through an approval broker, which is not built
yet; until then agents can't deploy.