OpenAI explains how Codex sandbox uses OS-level isolation and a domain-rule network proxy instead of containers
OpenAIDevs · x · 2026-11-19
OpenAI's dev account published a detailed explainer on the Codex sandbox, which constrains commands running in the user's existing environment rather than a separate container.
- OS-level sandboxing per platform: macOS Seatbelt, Linux bubblewrap + seccomp, Windows MXC. Child processes inherit sandbox constraints across the whole process tree.
- Rationale: sandboxing Codex in Docker on a Mac would break the native iOS build toolchain and iPhone simulator.
- Default permission profile allows source file edits without approval but blocks writes to root .git/.codex folders; filesystem reads follow existing OS permissions.
- Network access is disabled by default; requests trigger a user prompt or auto-review. A network proxy enforces per-domain rules so package registries can be allowlisted without repeated approvals.
- Proxy request-handling logic is shared across OSes; on Linux, connections inside the isolated namespace are relayed to the proxy by a process outside the sandbox.
Related event: OpenAI Details Codex Sandbox: OS-Level Isolation Over Containers(5 posts)→
More from coding & agent
- Dev Builds "PowerPoint for Agents": Plain English In, Real .pptx Out, Free — kristoph · 2026-11-19
- CocoIndex Solves the Agent Task-Tree Trilemma: Recursion, Concurrency Caps, No Deadlock — CShorten30 · 2026-11-19
- Factory expands Microsoft partnership: Droids on Azure, delegation via Teams — annbordetsky · 2026-11-19
- shadcn ships UI SDK for Solid 2.0 with agent-first docs and install prompts — shadcn · 2026-11-19
- Personal Agents Hackathon hits SF Nov 20 with $9,000+ in prizes, Meta and Cursor judges — code_star · 2026-11-19
- NVIDIA post-trained Nemotron with Factory entirely inside its air-gapped network — kuchaev · 2026-11-19