Add a supported way to disable the edit review/apply confirmation UI for trusted repos
Summary
Please add a supported option to disable the edit review/apply confirmation UI for trusted repos/projects, so Codex can apply file edits automatically in the same way that command approvals can already be reduced or disabled.
Problem
Today, even with repo-scoped config such as:
approval_policy = "never"sandbox_mode = "workspace-write"- optional trusted project config
Codex may still show an edit confirmation flow like:
Would you like to make the following edits? 1. Yes, proceed 2. Yes, and don't ask again for these files 3. No, and tell Codex what to do differently
This appears to be separate from command approval policy and creates friction for trusted repos where the user explicitly wants Codex to edit files without repeated manual confirmation.
Requested feature
Please add a documented config option or mode that disables the edit review/apply confirmation UI for trusted repos/projects.
Desired behavior:
- trusted repo/project
- repo-scoped or user-scoped config
- Codex can apply in-workspace edits automatically
- command/network permissions remain governed by sandbox + approval config
- no repeated y/n/esc edit confirmation for normal file edits
Suggested shape
Possible approaches:
- config flag to disable edit-apply confirmation UI
- project-level trust option for auto-apply edits
- separate setting from command approvals, clearly documented
Why this matters
This would make Codex much more usable for:
- PR-first repo workflows
- docs-heavy repositories
- trusted personal repos
- repetitive multi-slice workflows
It would also better align with the expectation that approval/sandbox config should fully describe the agent’s autonomy level for trusted projects.
Environment
- Repo-scoped
.codex/config.toml approval_policy = "never"sandbox_mode = "workspace-write"- trusted project
- desire to keep normal workspace boundaries without switching to dangerous full-access mode
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗