OpenAI Details Codex Sandbox: OS-Level Isolation Over Containers
On November 19, an OpenAI developer account published a series of long posts detailing the Codex sandbox design: instead of moving computation into separate containers, Codex constrains command execution directly in the user's existing environment with OS-level sandboxes — Seatbelt on macOS, bubblewrap on Linux. The company also shared details of the default permission profile: network access is disabled, with commands requesting network triggering a user prompt or routing to auto-review; when a Git repository is the workspace, source files can be edited without approval, but writes to the root-level .git and .codex folders are blocked, broad filesystem reads are allowed, and all subprocesses inherit the sandbox.
Confirmed
- The sandbox is OS-level isolation (macOS Seatbelt, Linux bubblewrap), distinct from container-based approaches
- The default permission profile disables networking; a network proxy can be enabled for build processes that periodically download from package registries
- Default Git workspace profile: source code editable, .git and .codex write-protected, broad filesystem reads allowed, subprocesses inherit the sandbox
- The network proxy's core request handling and policy logic are shared across the three major operating systems, while proxy setup and sandbox integration are implemented per OS; on Linux, commands connect to a listener relayed inside an isolated network namespace (e.g., 127.0.0.1)
Why it matters
- The company explained the key reason for dropping Docker: when developing iOS apps with Codex on a Mac, the iOS toolchain and simulators can't run inside a container sandbox, whereas an OS-level sandbox constrains commands directly in the user's environment, avoiding this limitation
- The design illustrates the engineering trade-offs of "a model doing controlled work on your machine," offering direct reference value for understanding Codex's security model and the prompts and network behavior seen in everyday use
2026-11-19 ~ 2026-11-19 · 5 related posts
Primary sources
- OpenAI explains how Codex sandbox uses OS-level isolation and a domain-rule network proxy instead of containers — OpenAIDevs ·
- Codex defaults to no network access, with prompts, auto-review, and a domain-rule proxy for exceptions — OpenAIDevs ·
- Why Codex skips Docker: container sandboxing breaks native iOS toolchains and simulators — OpenAIDevs ·
- [source] OpenAI explains how Codex sandbox uses OS-level isolation and a domain-rule network proxy instead of containers — OpenAIDevs · 2026-11-19
- Codex's Git-workspace default profile: free source edits, .git write-blocks, inherited sandbox for all descendants — OpenAIDevs · 2026-11-19
- [source] Why Codex skips Docker: container sandboxing breaks native iOS toolchains and simulators — OpenAIDevs · 2026-11-19
- Codex network proxy shares policy logic across OSes, relays Linux sandbox connections via in-namespace listener — OpenAIDevs · 2026-11-19
- [source] Codex defaults to no network access, with prompts, auto-review, and a domain-rule proxy for exceptions — OpenAIDevs · 2026-11-19