Add project-scoped “Always allow” to command approval dialogs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
App version: 26.901.51231 (build 8109)
What feature would you like to see?
In an earlier version, command approval dialogs offered an option similar to “Always allow” or “Don’t ask again”. I no longer see this option in the dialogs I encounter. I do not remember the exact wording or the last working version.
As a result, tasks frequently pause for manual command approval while working on the same project.
Additional information
Environment
- ChatGPT desktop app, using Codex
- App version: 26.901.51231 (build 8109)
- Bundled Codex CLI: 0.153.4
- macOS: 26.6.2 (25G83)
- Configuration: workspace-write, approval_policy = "on-request", approvals_reviewer = "user"
Problem
In an earlier version, command approval dialogs offered an option similar to “Always allow” or “Don’t ask again”. I no longer see this option in the dialogs I encounter. I do not remember the exact wording or the last working version.
As a result, tasks frequently pause for manual command approval while working on the same project.
What I have tried
- Persistent command rules, including project-local rules, have not resolved the repeated interruptions.
- Automatic approval review did not improve the workflow; in my experience, it caused more interruptions.
- Full Access is too broad. I want to keep the sandbox and approve specific recurring operations.
Expected behavior
Please restore the persistent approval option where supported. If a command cannot receive persistent approval, explain why in the dialog.
I would also like an “Always allow this command or command prefix for this project” option that:
- Clearly shows what is being allowed.
- Applies across the project’s tasks and worktrees.
- Persists after restarting the app.
- Allows saved permissions to be reviewed and revoked.
- Keeps unrelated operations subject to approval.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the command approval dialogs, persistent command rules, and project-local rules described in the issue across the Codex CLI and desktop app. Done means supported commands can be persistently allowed for a project, the scope is clearly shown, permissions survive app restarts, and saved permissions can be reviewed and revoked without broadening unrelated approvals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- cli, desktop, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100