Windows: latest sandbox ignores "allow this session" permission

[rudivs]

What version of the VS Code extension are you using?

0.4.49

What subscription do you have?

Pro

Which IDE are you using?

VS Code

What platform is your computer?

Windows

What issue are you seeing?

After being prompted and agreeing to use the latest Windows sandbox, the Codex extension now prompts me to accept every change. Clicking on the "Allow this session" option has no effect, it will continue to prompt me every time.

What steps can reproduce the bug?

Install Codex extension and use latest Windows sanbbox. Prompt for edits. Select "Allow this session" - the next edit will also trigger a prompt, regardless of whether it's making another edit to the same file or a different file.

What is the expected behavior?

Selcting "Allow this session" should allow the agent to continue without my involvement.

Additional information

No response

[iceweasel-oai]

@rudivs thanks for reporting this. The behavior leads me to believe that the sandbox did not get properly enabled, because when Codex has a sandbox, it should not need to prompt at all for edits in your workspace.

Do you have a file on your machine (located in CODEX_HOME/ ) called sandbox_commands.rust.log? If so, would you mind sharing it?

[bASEstr]

@rudivs thanks for reporting this. The behavior leads me to believe that the sandbox did not get properly enabled, because when Codex has a sandbox, it should not need to prompt at all for edits in your workspace.

Do you have a file on your machine (located in CODEX_HOME/ ) called sandbox_commands.rust.log? If so, would you mind sharing it?

I have the same issue, and I have found this log but it is huge, filled with calls to powershell.exe and codex.exe . Anything specific you're looking for that I can "ctrl+F" in the file?

[nubpro]

how can I contribute? I am facing the same silly issue here on windows, I have to always press approve on each file even though I am on agent mode

[blkot]

this issue bothers me so much

[etraut-openai]

@blkot, please refer to our Windows documentation. Have you tried enabling the experimental Windows sandbox?

[nubpro]

@blkot, please refer to our Windows documentation. Have you tried enabling the experimental Windows sandbox?

he is right, this will resolves the issue

[blkot]

@blkot, please refer to our Windows documentation. Have you tried enabling the experimental Windows sandbox?

Thanks for the guide, i quickly did a test with disable the sandbox and re-enable it in the settings, also tried running vsc as admin, but still. now i moved to macOS and everything works fine, i'll try again when i get access to my winpc.

[blkot]

@blkot, please refer to our Windows documentation. Have you tried enabling the experimental Windows sandbox?

he is right, this will resolves the issue

thanks for the feedback, i'll test later.