"Allow every time" is asked every time
Resolved 💬 18 comments Opened Sep 4, 2025 by PhunkyBob Closed Sep 4, 2025
💡 Likely answer: A maintainer (gpeal, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
codex-cli 0.29.0 + VSCode plugin 0.5.3
Which model were you using?
gpt5
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What steps can reproduce the bug?
- Install VSCode Codex extension.
- Ask the AI something that needs several files editing.
What is the expected behavior?
- At first file edit, the tool asks if it can edit the file.
- I press "Allow every time".
- The tool never asks me again during this session to edit files.
What do you see instead?
- Every time the tool needs to edit a file, it asks me the permission.
Additional information
_No response_
18 Comments
This situation is seriously impacting my productivity and time. I desperately need this resolved. I'm constantly standing before the computer, hitting the enter key.
Duplicate of #2680
Thanks for the report. We're actively working on some Windows improvements. We know this isn't ideal at the moment
🧐
GO! Codex!
@gpeal sorry but it's not clear how this is a duplicate of #2680
It's quite painful and I'd like to be sure it's not missed.
That's not related at all. Please we need a quick fix for this. This is painful. A single request might need 30 approvals!
Allow every time now asks every time for file changes, previously it was asking everytime for pwsh command
mesma coisa aqui!!!!
This bug still exists even in the latest codex version as of today 0.38.0. I am on windows and using codex in wsl seems to work.
0.38.0 with Windows command line -> still asking for every action.
Why is this closed when the bug very much still exists?
Persists on
openai.chatgpt-0.5.15-win32-x64...@edgar-silchenko I tried to use with Full Access mode, and it is not asking me anything anymore
Of course, it’s not a solution, but what can we do if
openaidoesn’t care? A temporary workaround is using full-access mode, at your own risk.@mqhamdam Thanks! That helped. IDK how I missed that setting 😅
I'm using the
--yoloflag to avoid confirmations every 12 seconds.Yesterday, the tool executed
cd wrong_folder ; rm -rf *.*and everything in my current folder disappeared...Please get this fixed... this is embarrassing
I'm still getting this issue, with CLI.
In one of my project, it asks perms to edit the file everytime. in other projects it was fine
▌Apply changes?
▌ Yes No, provide feedback
▌ Approve and apply the changes
on the
VSCodehow can we enableyolomode?