Repository navigation
Codex is again asking for permission for every single file read command #13117
Description
What version of the IDE extension are you using?
0.4.79
What subscription do you have?
Plus
Which IDE are you using?
VS Code
What platform is your computer?
Windows 25H2
What issue are you seeing?
The bug where Codex would ask for permission for every single file read/grep command is back. Codex will ask several dozen of permissions to simply read files.
This bug used to exist quite a while ago but was eventually solved. It has now returned in v0.4.79
What steps can reproduce the bug?
- Prompt the Codex to inspect wider codebase (such as "Can you look around the project and find all usages of foo".
- Select the "Yea and don't ask again" on every "Do you want to run this command" prompt.
- Codex will still ask again.
What is the expected behavior?
The codex will browse the code base and return the information it gathered without need to confirm several dozens of "Do you want to run this command" prompts. Only write access prompts should require confirmation, not read ones.
Additional information
In this particular case, I had to confirm about ~40-50 GetContent commands:
No response
Reacted by Olivier Supplisson, Josh Hayden, Albert, Ma-XX-oN, Krasnoslabodtsev, Alexey Klimkin, Matthew Costello, Andreas Titan, TeamDman and Alexis Pomares
Activity
github-actions commentedon Feb 28, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
etraut-openai commentedon Mar 1, 2026
This is likely because the Windows sandbox is not enabled or failed to install at startup.
Does the problem go away if you downgrade to a previous version of the extension? I'm trying to determine if this is a regression in the Codex extension or is caused by some other change on your system.
Rawalanche commentedon Mar 2, 2026
It seems solved by enabling "Run Codex in Windows Subsystem for Linux" setting.
However I am pretty sure earlier equivalent of this setting must have been enabled before somehow (I think the option to do it used to exist directly in the cogwheel settings menu before) because codex hasn't bothered me with approve prompts for past ~2 months.
Possibly something in 0.4.79 caused the WSL sandbox setting to reset to default.
I could try to downgrade to test it again, but I am a bit reluctant to do it now that the extension once again magically works well. This extension is very fragile and buggy, so any state/setup that has relatively no problems is rare and I'd like to enjoy it while it lasts.
god-boat commentedon Mar 3, 2026
also seeing this issue. super annoying every get content command needs approval. feels like a regression since last week this was not the case, get content did not require approval. Issue persists across app reloads and system restarts V 0.5.79, vs code
EricGT commentedon Mar 5, 2026
Would you consider this a valid way to check?
Using Windows Task Manager search for
codexFor each Codex session there should be a
codex-windows-sandbox. So if three instances of VSCode are running and using Codex there should be threecodex-windows-sandbox, e.g.Or to see the command line using Windows Task Manager details tab
Rawalanche commentedon Mar 5, 2026
It happened to me again when I opened different VSCode project:
WSL is enabled in VSCode Codex settings, but no, there's no codex-windows-sandbox.exe running.
Of course "Yes and don't ask again...." doesn't do anything
kell18 commentedon Mar 5, 2026
Same problem and it's extremely annoying :(
Rawalanche commentedon Mar 15, 2026
It's extremely frustrating because it appears to have nothing to do with VSCode/Codex configuration. It simply happens randomly in some projects/repos while doesn't happen in others at all whatsoever.
Mujtaba-Abbasi commentedon Mar 17, 2026
I am facing the same issue but on Ubuntu, extremely annoying.
empyriumz commentedon Mar 21, 2026
same issue here. it seems project dependent.
0tii commentedon Apr 25, 2026
still happening, default permissions asking for permission with every single change, even if you hit "yes and dont ask again". The fact this keeps regressing over and over again (together with the tons of other regressions in every update) just shows how betting on agentic AI to do the majority of your development inevitably affects your product quality. man am i looking forward to the software landscape in the future, where its normal to push out features by the metric ton but subsequently make the whole product more and more brittle.
0tii commentedon May 14, 2026
Still happening, the golden age of AI is really just the golden age of regressions that never get fixed because "too busy introducing new unstable features while breaking existing functionality". actually infuriating.
Ciriak commentedon May 27, 2026
Still happening
luisjdtt commentedon May 31, 2026
Any updates on this?
It is very annoying that happens with every command despite pressing the dont ask again.
i am on macbook.
TeamDman commentedon Jun 1, 2026
still happening.
nischalj10 commentedon Jun 20, 2026
still happening on macbook
CheesyBiscuits commentedon Jun 24, 2026
Oh my god this is infuriating. Since the latest update I have had to approve everything even with Full Access turned on.