-
Notifications
You must be signed in to change notification settings - Fork 8k
Description
What version of Codex CLI is running?
0.101
What subscription do you have?
plus
Which model were you using?
gpt-5.3-codex
What platform is your computer?
macOS
What terminal emulator and version are you using (if applicable)?
Terminal.app
What issue are you seeing?
In recent updates the approval mode called “read-only” either no longer appears in the CLI selectors. When selecting what used to be read-only, I observe that read-only mode no longer triggers on-demand approvals for edits — commands execute without prompting or force the CLI to use auto mode. This differs from historical behavior where every edit in read-only mode would explicitly ask for user approval. I expect to be prompted for approval before any file change when in read-only mode.
What steps can reproduce the bug?
- Run
codex --versionand confirm 0.101 - Start CLI in a directory with files
- Run
/approvalsand try selecting “Read Only” - Request a file edit (e.g. some simple change)
→ CLI either does not prompt for approval or defaults to auto mode. Older behavior used to require approval.
What is the expected behavior?
Read-only/approval mode should explicitly ask for permission before any write or command that modifies files.
Additional information
Multiple similar issues have been reported on GitHub regarding approval and read-only interactions not working as intended.