Codex permission profiles: config.toml examples for safe agent runs

Codex permission profiles are named policies in config.toml that control what commands can read, write, and reach on the network. A profile is selected with default_permissions and can start from a built-in base such as :read-only, :workspace, or :danger-full-access, then add read, write, and deny paths along with allowed domains. The guide provides ready-to-use config examples, including one for API work that lets an agent run Apidog CLI tests against specific hosts without opening full internet access. Codex enforces these policies locally using Seatbelt on macOS, bubblewrap with seccomp on Linux and WSL, and MXC on Windows. The permissions feature is still labeled Beta, so key names may change between versions. Profiles must not be combined with legacy sandbox settings such as sandbox_mode, which cause default_permissions to be ignored.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in