VS Code's horrible confirmation work-flow
What version of the IDE extension are you using?
0.4.73
What subscription do you have?
Plus
Which IDE are you using?
VS Code
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What issue are you seeing?
When requesting a complex job, I may be faced with 10-20 approval requests for one action, preventing me from working on other things.
For example, in this screenshot situation where codex is requesting multiple slices of code in a row, and since each request uses a slightly different command line to access different sections of the code in the same file, the "Yes, don't ask me again" simply doesn't work.
<img width="364" height="97" alt="Image" src="https://github.com/user-attachments/assets/b855fe71-50f6-4168-84f1-e65b8bd18144" />
Yes, I can give full access, but I don't want a glitch to accidentally damage to my workstation.
Yes, I can run everything in a virtual machine, but that adds several layers of complexity that I would rather avoid.
Ideally, there would be a third option in between "Default permission" and "Full access", a "Do whatever you want in white-listed folders" option where codex can take any action as long as it's limited to the approved folders.
Or at the very minimum, adapt the "Yes, don't ask again" option to actually not ask again for different code slices read requests in the same file.
What steps can reproduce the bug?
Ask any complex question on a large code base.
What is the expected behavior?
Don't interrupt my flow so many times.
Additional information
_No response_
5 Comments
I agree, this button useless, as workaround I set prefixes manual in ~/.codex/rules/ : https://developers.openai.com/codex/rules/
If you haven't already done so, please enable the experimental Windows sandbox. Without a sandboxing mechanism, we need to be very conservative about which tool calls to allow without user permission.
That adds several layers of complexity I (and probably many others) don't want to deal with.
When running under windows, you can hook into child processes functions, intercepting and block any disk access on the WinAPI level. Should be pretty easy to lock out any reads or writes from unauthorized folders without having to use WSL or any sandboxing.
how the fuck is this closed when codex has never been worse in that regard, im in WSL and i cant let codex do ANYTHING without asking for permission 6 times per single fucking action. its unbearable!
they now have ✋ icon which controls, 2nd option works fine, by default it is 1st option, there is also yolo mode, but you better to jail vscode with codex and single project before run yolo