Codex tip: Do yourself a favor and switch to using "Approve for me" by default
You should not let your coding agent run free without any checks but also approving each tool call isn't the way
"Approve for me" is a good middle ground as it let codex review each tool call and only escalate when needed
Particularly godsend for long running tasks
Positive users praise Codex's 'Approve For Me' default for agent tool calls because it eliminates repetitive approvals and improves workflow, while negative users report it blocks CLI commands and forces a return to full access.
read more in the docs here:
https://developers.openai.com/codex/concepts/sandboxing/auto-review
Codex tip: Do yourself a favor and switch to using "Approve for me" by default
You should not let your coding agent run free without any checks but also approving each tool call isn't the way
"Approve for me" is a good middle ground as it let codex review each tool call and only escalate when needed
Particularly godsend for long running tasks
@reach_vb This too easily blocks CLI calls for e.g. @trycua and tells me that it can't do shell commands. So back to full access setting.
@reach_vb this is still auto-review right? just renamed to make it easier for users to understand
@reach_vb that’s legalese
full access the only way
@reach_vb I don't know how anyone functions without this.
I remember back in the stone ages (i.e. April) when you had to risk Codex ransomwaring your machine in YOLO mode to avoid constant approvals. And it was worth it.
"Approve for me" by contrast is a no-brainer.
@reach_vb am i the only one still using ‘—yolo’ since cli 0.27.0 👀
@reach_vb can you flag some difference between full access and "Approve for me"
@reach_vb Yeah just tried it last week, cant go back to manually approving now, it does surface unnecessary ones every now and then and def the balance we need from manual to full approval
@reach_vb auto feels right when i dont know the repo yet. once the repo is boxed in and trusted, yolo is fine. every extra review layer still has a token cost
@reach_vb ngl clicking approve for every lil thing feels like im just the agent's receptionist
approve for me is the only way i stay sane and it still catches the dumb stuff
@reach_vb Favor accepted
@reach_vb This is such a brilliant feature.
After using it, it’s hard to go back to tools where every single command needs manual approval.
The difference in flow is huge. You stay focused on the task instead of constantly babysitting the agent.
@reach_vb I love the approve for me feature, but it’s annoying to still get sandbox blockers all the time
We need yolo mode but with auto approvals
I tried making custom config, but I still get the constant “I couldn’t do that because of the sandbox let me try again” thinking messages
@reach_vb Just curious, does the auto review use my codex usage?
@tobitege @reach_vb @trycua interesting.. we might introduce a cua-driver launch codex profile
@reach_vb YOLO mode all the time for me
@reach_vb 🫡
@reach_vb I've been using it recently and I love it.
@reach_vb It costs extra tokens, i assume.
@divyanshkul @reach_vb Yes, I believe so, incredibly useful feature. I used to do "Full Access" lol
Codex tip: Do yourself a favor and switch to using "Approve for me" by default
You should not let your coding agent run free without any checks but also approving each tool call isn't the way
"Approve for me" is a good middle ground as it let codex review each tool call and only escalate when needed
Particularly godsend for long running tasks