Answer: To set approval and execution permissions for Codex using requirements.toml, use the allowlists `allowed_approval_policies` and `allowed_sandbox_modes` (or, for Codex 0.138.0 or later, `allowed_permission_profiles` with managed `default_permissions`). For example, `allowed_approval_policies = ["untrusted", "on-request"]` and `allowed_sandbox_modes = ["read-only", "workspace-write"]` blocks `--ask-for-approval never` and `--sandbox danger-full-access`. Status: Confirmed Entry: tool/codex/permissions-and-security/set-approvals-execution-permissions Revision: 3 Digest: sha256:04475899de823fe2 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:50:11Z Last changed: 2026-11-20T13:38:20Z (Legacy sandbox mode guidance: — → allowed_sandbox_modes) Last verified: 2026-11-20T13:38:20Z Next check: 2026-11-21T13:38:20Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Approval policies key | allowed_approval_policies | [1] | 2026-11-20 Sandbox modes key | allowed_sandbox_modes | [1] | 2026-11-20 Permission profiles key | allowed_permission_profiles | [1] | 2026-11-20 Default permissions key | default_permissions | [1] | 2026-11-20 Minimum version for permission profiles | 0.138.0 | [1] | 2026-11-20 Legacy sandbox mode guidance | allowed_sandbox_modes | [1] | 2026-11-20 Sources: [1] OpenAI. "Managed configuration". https://learn.chatgpt.com/docs/enterprise/managed-configuration.md Role: primary. Accessed: 2026-11-20T13:38:20Z Quote: "allowed_approval_policies = ["untrusted", "on-request"]" (Supports: Approval policies key) Quote: "allowed_sandbox_modes = ["read-only", "workspace-write"]" (Supports: Sandbox modes key) Quote: "Use `allowed_permission_profiles` to control which built-in and custom" (Supports: Permission profiles key) Quote: "default_permissions = ":workspace"" (Supports: Default permissions key) Quote: "Permission-profile allowlists require Codex 0.138.0 or later." (Supports: Minimum version for permission profiles) Quote: "Use `allowed_sandbox_modes` only for legacy deployments that still configure `sandbox_mode`." (Supports: Legacy sandbox mode guidance) Snapshot SHA-256: 9b65f67238c730cfdf6788d0714b3be227e2e6963d8a9ed0d184d6e118f241ff (captured 2026-11-19T13:28:45Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T13:28:47Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:38:20Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:38:20Z Last attempt: 2026-11-20T13:38:20Z Notes and limitations: Extracted automatically from a single official source (section "Set approvals and execution permissions"). Related: https://latestn.com/tool/codex/permissions-and-security/set-token-expiration-limit How do I set an expiration limit for Codex access tokens? https://latestn.com/tool/codex/permissions-and-security/set-up-daybreak How do I set up Daybreak Defense Factory to scan a GitHub repository with Codex Security? https://latestn.com/tool/codex/permissions-and-security/shell-wrappers-compound-commands How does Codex handle shell wrappers and compound commands when matching rules? https://latestn.com/tool/codex/permissions-and-security/sandbox-restrictions What does the Codex sandbox restrict the agent from doing on my machine? https://latestn.com/tool/codex/permissions-and-security/sandbox-vs-approvals How do sandbox permissions and approval policies work together in Codex? https://latestn.com/tool/codex/permissions-and-security/security-review-prerequisites What do I need before I can configure Codex Security Review? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:38:20Z | changed | Legacy sandbox mode guidance: — → allowed_sandbox_modes | [1] 2026-11-20T13:38:20Z | changed | Legacy sandbox key: sandbox_mode → — | [1] 2026-11-18T13:32:14Z | changed | Legacy sandbox key: — → sandbox_mode | [1] 2026-11-18T13:32:14Z | changed | Default permissions key: — → default_permissions | [1] 2026-11-18T13:32:14Z | changed | Permission profiles key: — → allowed_permission_profiles | [1] 2026-11-18T13:32:14Z | changed | Sandbox modes key: — → allowed_sandbox_modes | [1] 2026-11-18T13:32:14Z | changed | Approval policies key: — → allowed_approval_policies | [1] 2026-11-18T13:32:14Z | changed | Legacy sandbox mode key: allowed_sandbox_modes → — | [1] 2026-11-18T13:32:14Z | changed | Managed default permissions: default_permissions = ":workspace" → — | [1] 2026-11-18T13:32:14Z | changed | Permission profile allowlist: allowed_permission_profiles → — | [1] 2026-11-18T13:32:14Z | changed | Sandbox mode allowlist: allowed_sandbox_modes = ["read-only", "workspace-write"] → — | [1] 2026-11-18T13:32:14Z | changed | Approval policy allowlist: allowed_approval_policies = ["untrusted", "on-request"] → — | [1] 2026-11-13T03:50:11Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/set-approvals-execution-permissions/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/permissions-and-security/set-approvals-execution-permissions POST: https://latestn.com/dispute/tool/codex/permissions-and-security/set-approvals-execution-permissions with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/set-approvals-execution-permissions?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I set approval and execution permissions for Codex using requirements.toml? Revision 3, last verified 2026-11-20T13:38:20Z. https://latestn.com/tool/codex/permissions-and-security/set-approvals-execution-permissions (accessed 2026-11-21T10:03:31Z). @misc{LatestN_tool_codex_permissions_and_security_set_approvals_execution_permissions_r3, title = {How do I set approval and execution permissions for Codex using requirements.toml?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/set-approvals-execution-permissions}}, note = {Revision 3; digest sha256:04475899de823fe2; last verified 2026-11-20T13:38:20Z; accessed 2026-11-21T10:03:31Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/permissions-and-security/set-approvals-execution-permissions