/permissions

Controls which actions Codex may perform without asking (approval mode).

/permissions is the successor to /approvals and controls the approval mode of the running session. It sets how much Codex may do on its own before asking for confirmation — comparable to the startup flags --ask-for-approval/--approval-mode and --sandbox (e.g. workspace-write or danger-full-access).

✅ WHEN TO USE IT?

Temporarily grant more freedom for riskier steps

/permissions — loosen the sandbox/approval mode before Codex needs to install dependencies or run migrations

Restrict again after a sensitive action

/permissions — switch back to a stricter mode after Codex has had filesystem access

⛔ WHEN NOT TO?

Approvals should be fixed for the whole session from the start

Manually switching mid-session is unnecessary if the desired mode is already clear before starting.

Better: Set the mode directly at startup, e.g. with --full-auto or --sandbox workspace-write

SOURCES

Codex CLI Doku: Slash Commands ↗ developers.openai.com