Cmd. /approvals
Legacy alias for the /permissions command.
Key takeaways
- Legacy alias for the /permissions command.
- Legacy alias. Use /permissions in the current menu and new documentation.
Purpose
Legacy alias for the /permissions command.
/approvalsAvailability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Alias |
| Status | Renamed |
| Aliases | — |
| Documented minimum | Not specified |
| Reviewed against | 2026-09-22 · Codex CLI 0.155.1 |
Legacy alias. Use /permissions in the current menu and new documentation.
Examples
/permissionsWhen to use it
- Use
/approvalsonly when following old notes or muscle memory. - Rewrite team playbooks to point users to
/permissions.
Choosing related commands
| Command | Difference | Choose It When |
|---|---|---|
/approvals | Legacy alias | You need compatibility with old usage |
/permissions | Current primary command | You are writing new docs or training |
/status | Shows current policy | You need confirmation after changes |
Effects and persistence
Applies the chosen permission policy or rules to later tool calls. Managed organization settings can restrict the available choices.
/approvals still works as an alias, but the official slash popup no longer lists it. Prefer
/permissions in new documentation.
Cautions
- Do not teach
/approvalsas the primary command in new material. - Use
/permissionsfor clearer alignment with current docs.
Official sources
Complete command list · Verification scope · History for this command