-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Open
Labels
CLIIssues related to the Codex CLIIssues related to the Codex CLIbugSomething isn't workingSomething isn't workingsandboxIssues related to permissions or sandboxingIssues related to permissions or sandboxing
Description
Summary
In Codex on macOS with sandboxing enabled, Playwright browser tests fail due to environment restrictions before app logic runs.
I see two failures:
- Chromium startup crash:
FATAL:base/apple/mach_port_rendezvous_mac.cc:155
Check failed: kr == KERN_SUCCESS.
bootstrap_check_in org.chromium.Chromium.MachPortRendezvousServer.<pid>: Permission denied (1100)
- Local server bind failure:
Error: listen EPERM: operation not permitted 127.0.0.1
The same tests pass on the same machine outside the Codex sandbox.
Repro
This kind of command fails in sandbox:
npx playwright testExpected
Either:
- browser-backed tests can run, or
- Codex clearly reports that sandbox policy blocks Chromium startup / localhost binding
Actual
The failure looks like a repo/test regression even though it is a sandbox restriction.
Why this matters
This can cause agents to:
- misdiagnose healthy repos as broken
- modify working code to work around sandbox-only failures
- waste time debugging Playwright/app logic unnecessarily
Request
Please document or surface these sandbox limitations more explicitly on macOS:
- Chromium startup restrictions
- loopback bind restrictions (
127.0.0.1)
Additional context
I have a local repro and internal notes with the exact failure signatures if that would help.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
CLIIssues related to the Codex CLIIssues related to the Codex CLIbugSomething isn't workingSomething isn't workingsandboxIssues related to permissions or sandboxingIssues related to permissions or sandboxing