Answer: Permission profiles replace the older combination of `sandbox_mode` and `sandbox_workspace_write` when you want one reusable profile to describe both filesystem and network behavior, and you should use one system or the other for a session, not both. Status: Confirmed Entry: tool/codex/permissions-and-security/migrate-sandbox-to-profiles Revision: 1 Digest: sha256:5d499d82cde825c4 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:52:15Z Last changed: 2026-11-13T03:52:15Z Last verified: 2026-11-20T13:40:43Z Next check: 2026-11-21T13:40:43Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Replaces | sandbox_mode | [1] | 2026-11-20 Usage rule | Use one system or the other for a session, not both. | [1] | 2026-11-20 Read-only profile | :read-only | [1] | 2026-11-20 Workspace profile | :workspace | [1] | 2026-11-20 Workspace roots | :workspace_roots | [1] | 2026-11-20 Unrestricted profile | :danger-full-access | [1] | 2026-11-20 Sources: [1] OpenAI. "Permissions". https://learn.chatgpt.com/docs/permissions.md Role: primary. Accessed: 2026-11-20T13:40:43Z Quote: "Permission profiles replace the older combination of `sandbox_mode` and" (Supports: Replaces) Quote: "Use one system or the other for a session, not both." (Supports: Usage rule) Quote: "For a read-only workflow, use the built-in `:read-only` profile or define a" (Supports: Read-only profile) Quote: "For workspace editing, use the built-in `:workspace` profile or define a" (Supports: Workspace profile) Quote: "custom profile that writes through `:workspace_roots` and adds only the extra" (Supports: Workspace roots) Quote: "For unrestricted local execution, use `:danger-full-access` only when you" (Supports: Unrestricted profile) Snapshot SHA-256: 1af24fb0126aba2d5eb43f8a1094bcf9e465e21c94ffeae78ba7dad874466318 (captured 2026-11-13T03:52:14Z) 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-13T03:52:15Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:40:43Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:40:43Z Last attempt: 2026-11-20T13:40:43Z Notes and limitations: Extracted automatically from a single official source (section "Migrate from older sandbox settings"). Related: https://latestn.com/tool/codex/permissions-and-security/migrate-untrusted-approval-policy How do I migrate from the retired untrusted approval policy in Codex? https://latestn.com/tool/codex/permissions-and-security/permission-modes-overview What permission modes does ChatGPT and Codex offer for local actions? https://latestn.com/tool/codex/permissions-and-security/prepare-evidence-for-hardening What evidence should I provide to Codex Security when proposing security hardening? https://latestn.com/tool/codex/permissions-and-security/isolate-environment-cybersecurity How do I isolate the environment when running Codex for cybersecurity work? https://latestn.com/tool/codex/permissions-and-security/manage-privileges How do I manage privileges and permissions for the Codex GitHub Action? https://latestn.com/tool/codex/permissions-and-security/manual-security-review-of-changes How do I run a manual security review of code changes in Codex? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:52:15Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/migrate-sandbox-to-profiles/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/migrate-sandbox-to-profiles POST: https://latestn.com/dispute/tool/codex/permissions-and-security/migrate-sandbox-to-profiles with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/migrate-sandbox-to-profiles?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I migrate Codex from older sandbox settings to permission profiles? Revision 1, last verified 2026-11-20T13:40:43Z. https://latestn.com/tool/codex/permissions-and-security/migrate-sandbox-to-profiles (accessed 2026-11-21T10:06:24Z). @misc{LatestN_tool_codex_permissions_and_security_migrate_sandbox_to_profiles_r1, title = {How do I migrate Codex from older sandbox settings to permission profiles?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/migrate-sandbox-to-profiles}}, note = {Revision 1; digest sha256:5d499d82cde825c4; last verified 2026-11-20T13:40:43Z; accessed 2026-11-21T10:06:24Z} } 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/migrate-sandbox-to-profiles