Codex "always allow" choice on Codex CLI begs improvement

Codex
,
1

There should be an option to edit what codex should be always allowed when presented with the question allow / always allow / refuse. The command is usually tediously long and detailed in most real work contexts, so simply always allowing specific commands tends to be futile.

Please consider this as a productivity enhancement:

  • Let the user edit the command and apply “always allow” to the editted prefix, while allowing the specific command at the same time, or:
  • Let the user apply “always allow” to a user editted prefix, outside the said prompt itself, yet within the same CLI session itself; perhaps as an affordance after first allowing the specific command, to decopule work exeuction from future allow-list.

I didn’t find an in-session affordance for this so far myself.

2

Hey, thanks for sharing this feedback!

I agree that the “Always allow” flow in the Codex CLI could be more flexible and intuitive, especially when managing repeated approvals during development workflows.

I'll surface this feedback to the product team for consideration.

To keep feature requests consolidated, I'll be closing this topic. Thanks again for sharing!

Avinash

4

Hi @matanox!

Codex has an experimental Rules feature that you can use to define exactly which commands can be executed outside the sandbox.

I have been using the auto-review mode for several months now and ultimately that’s the easy solution, IMO.