Cmd. /permissions
Change Codex approval and permission policy during a session.
Key takeaways
- Change Codex approval and permission policy during a session.
- Check the input surface and availability before using the examples below.
Purpose
Change Codex approval and permission policy during a session.
/permissionsAvailability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Built-in |
| Status | Current reference |
| Aliases | /approvals |
| Documented minimum | Not specified |
| Reviewed against | 2026-09-22 · Codex CLI 0.155.1 |
The installed command menu and account or organization settings determine availability.
Examples
/permissionsWhen to use it
- Start a risky refactor in a stricter mode, then move to a more autonomous mode after the plan is clear.
- Use
/statusbefore and after the change to confirm the effective approval policy.
Choosing related commands
| Command | Difference | Choose It When |
|---|---|---|
/permissions | Changes approval and permission behavior | You need to change autonomy mid-session |
/approvals | Legacy alias | You are handling an older playbook or habit |
/status | Inspects current state | You need to confirm the active policy |
Effects and persistence
Applies the chosen permission policy or rules to later tool calls. Managed organization settings can restrict the available choices.
/permissions adjusts what Codex can do without asking first. Use it to tighten or relax approval
requirements while the session is still running.
Cautions
- Treat
/permissionsas part of the safety boundary, not as a convenience toggle. - Re-check policy after side conversations, resumed sessions, or remote app-server flows.
Official sources
Complete command list · Verification scope · History for this command