Classification and Application Scenarios of Approval Models
Codex CLI balances automation and security through a hierarchical approval mechanism:
| paradigm | trigger method | Applicable Scenarios | risk level |
|---|---|---|---|
| suggest (suggest mode) | Default mode, need to confirm each change manually | Critical production environments, sensitive code changes | ★☆☆☆☆ |
| auto-edit | Document changes are applied automatically, commands need to be confirmed | Daily development, batch file operations | ★★☆☆☆☆ |
| full-auto | Apply all changes unconditionally | CI/CD pipeline, trusted script execution | ★★★★☆ |
Special warning: fully automated mode triggers warnings in non-Git directories.--no-project-docparameters are used. The modes can be interchanged with the--approval-modeParameter dynamic switching.
This answer comes from the articleOpenAI Codex CLI: Terminal Command Line AI Coding Assistant Released by OpenAIThe
May not be reproduced without permission:AI productivity tools " What are the three file modification approval modes provided by Codex CLI? What scenarios are they suitable for?
