How-toOfficialSelected

Codex network proxy filters requests against permission profile domains

Why we picked it

The non-obvious point is that sandbox network policy in Codex is now domain-scoped and portable across platforms, so a single permission profile can govern builds on any OS rather than relying on ad hoc approvals. Teams running Codex in CI or on locked-down machines should codify registry domains like npmjs.com into their profiles to avoid interactive prompts. Compared with blanket network flags in other agent CLIs, this per-rule proxy gives security teams a clearer audit surface.

OpenAI's Codex CLI now ships with a default permission profile that disables network access, prompting users or routing requests to auto-review whenever a command tries to reach the internet. Teams whose builds regularly download dependencies can allowlist a package registry's domain in a permission profile with the network proxy enabled, removing the need for separate network approval on each request.

Body

The proxy checks each outgoing request against the profile's domain rules to decide whether to forward it. The request-handling and policy logic is shared across Linux, macOS and Windows, while proxy setup and sandbox integration remain OS-specific. On Linux, a command inside the sandbox connects to a listener in its isolated namespace, and a process outside the sandbox relays those connections to the configured proxy.

The design reflects a broader shift toward default-deny sandboxing for coding agents that execute shell commands. Per-domain rules instead of blanket approvals give teams a middle ground between fully offline isolation and unrestricted agent access, which matters for CI pipelines and security-conscious enterprises adopting agents that modify code and fetch dependencies.

Original · @OpenAIDevs

The default permission profile disables network access. When a command requests access, Codex may prompt the user directly or route the request to auto-review. If your build regularly downloads from a package registry, you can allow the registry’s domain in a permission profile with the network proxy enabled. The proxy checks each request against the profile’s domain rules to decide whether to forward it. Matching requests don’t need separate network approval each time. The network proxy’s core request-handling and policy logic is shared across all three major operating systems. Proxy setup and sandbox integration are OS-specific. On Linux, the command connects to a listener inside its isolated namespace. A process outside the sandbox relays those connections to the configured proxy.📊 5 ⚡

Industry Coordinates & Source Verification

This report is categorized under AITOP's "How-to" desk, focusing on US frontier AI labs and Silicon Valley technology leaders. Within our cross-regional analytical framework, it directly maps to AI developer toolchains, coding agents, and engineering workflows. Key entities and technical topics under continuous tracking include Codex, OpenAI, MCP and tools, coding assistants.

Primary source verification: published directly by @OpenAIDevs with first-party authority. Cross-source corroboration: 11 independent sources have covered this development (including 歸藏(guizang.ai), OpenAI Blog, Vaibhav Srivastav), confirming industry-wide signal strength.