openai
Windows approval “Allow for this session” isn’t remembered
What version of Codex is running?
codex-cli 0.41.0
Which model were you using?
affects all models
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What steps can reproduce the bug?
- Start Codex on Windows.
- Trigger any non–auto-approved command, e.g. a git init.
- In the approval modal choose “Always” / “Approve for this session.”
- Let the tool run, then issue the same command again.
- Codex asks for approval every time.
What is the expected behavior?
Once I approve “for this session,” any equivalent invocation during that session should run without another prompt.
What do you see instead?
Codex repeats the approval prompt because the stored command vector only matches the PowerShell-wrapped version that actually ran, not the original bash -lc … the UI shows and the model reuses.
Additional information
Bug reproduces reliably on Windows because exec command translation swaps the command vector before caching. Broad fix is to store both the displayed command and the executed command when the user approves “for this session.”
I have the same problem with MacOS and Win10, I'm sshing to a Linux computer.
i have same problem to..always clikc "aprove this session" every time. when forget use fullaccess
same issue, even after clicking 'approve this session', it's asking again and again
It is not normal that we have either to click on "allow this sessions" several times per prompt and grant access to the current project or to grant full access to our file system.
this is not an acceptable choice !
click on "Allow this session" should grant access to the current project only !
(just posted this here also - https://github.com/openai/codex/issues/3325#issuecomment-3433510602 )
Hello,
I am also having this issue. Click Allow every time....just pops back up. I am using Local, Agent Mode, gpt-5-codex (medium). Have not tested this so far with other combinations.
I might be wrong, but I presumed the intended functionality was, in my head 'Allow the Agent permission to edit as required, for this session, within the repo root and subdirectories, without having to click Allow again'.
That makes sense to me, in terms of risk. So any potential carnage is confined to my local version, and only within the folders for that project.
I'd prefer that, rather than having to give 'Full Access' to Codex Agent for this to work, ("When Codex runs with full access, it can edit any file on your computer and run commands with network, without your approval."). That sounds a bit scary to me ;-)
Windows 10 OS Name Microsoft Windows 10 Pro Version 10.0.19045 Build 19045
VScode Version: 1.105.1 (user setup) Commit: 7d842fb85a0275a4a8e4d7e040d2625abbf7f084 Date: 2025-10-14T22:33:36.618Z Electron: 37.6.0 ElectronBuildId: 12502201 Chromium: 138.0.7204.251 Node.js: 22.19.0 V8: 13.8.258.32-electron.0 OS: Windows_NT x64 10.0.19045
Github Actions extension Auto Update on, v0.28.0
Codex extension Auto Update on, v0.4.21
This issue affects all operating systems — Windows, macOS, and Linux — not just Windows as currently labeled.
Bump. Same issue. I feel like there should be a way of letting codex edit any file in my workspace without approvals. I have a git repo so I can clearly see what it changed and if I dont like it, I just roll back. It makes no sense in this case to have to approve every step as it works, just let me see the final product!
Pleeeeease fix it! Would make this tool 1000% more usable. As it is now, I cant do anything else while its working, because I have to be switching back just to approve.
p.s. dont want to use agent (full access).
Would make this tool 1000% more usable. Agreed. I completely stopped using it because of this behavior, while I really, really would like to use it.
I also get this issue and it makes me NOT want to use Codex, while the performance is overall good, having to approve simple edits in agent mode?
Same as @jfbosch not usable like that, only get the pull request review benefit out of codex right now.
0.4.43 macosx 15.6.1 (24G90)
For me this has been fixed for a couple of weeks now. I don't know why some people are saying it's still not fixed. Since moving to WSL it is now very, very usable, and never asks for permissions. I am using 0.4.43 of the VSCode Codex extension.
Yes, this should work fine if you're using WSL. It's still a problem with native Windows (without WSL). We're working on fixing that.
What about MacOSX?
On Tue, Nov 18, 2025 at 1:09 AM Eric Traut @.***> wrote:
etraut-openai left a comment (openai/codex#4212) https://github.com/openai/codex/issues/4212#issuecomment-3544599964
Yes, this should work fine if you're using WSL. It's still a problem with native Windows (without WSL). We're working on fixing that.
— Reply to this email directly, view it on GitHub https://github.com/openai/codex/issues/4212#issuecomment-3544599964, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABHXAAZXASUCFV7LNLO2BT35JWUNAVCNFSM6AAAAACHOHRMOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNBUGU4TSOJWGQ . You are receiving this because you commented.Message ID: @.***>
project is in WSL while vscode is in windows. experiencing the same.
edit: resolved on my end as of nov 24, 2025 10:06 PM utc
I have the same issue, VScode running on Windows with remote SSH to a Linux Box. NAME="Rocky Linux" VERSION="9.4 (Blue Onyx)"
Guys this is a really bad user experience effecting a LOT of users, can we please get this fixed? otherwise I'll just go back to Windsurf frankly.
