Allow Windows users to run Codex in "no sandbox" mode and explicitly approve/deny commands

Resolved 💬 5 comments Opened Apr 15, 2026 by rwalle Closed Jul 1, 2026

What variant of Codex are you using?

CLI

What feature would you like to see?

Currently, for Windows users, whenever they use Codex with any new folder (workspace), they will be greeted with the sandbox setup screen and have to choose between default sandbox, non-admin sandbox or quit.

<img width="1330" height="252" alt="Image" src="https://github.com/user-attachments/assets/d5556fe2-f283-40b3-ac66-c95f02d8cffa" />

We would like another "no sandbox" option where user explicitly approves/denies commands.

Additional information

The default sandbox is not allowed by IT (due to concerns documented in https://github.com/openai/codex/issues/12343 and elsewhere), while non-admin sandbox carries significant risk and allows running arbitrary command without approval in our testing.

We do notice that if user chooses "quit" and immediate open codex again for the same folder, they can use Codex in a mode where they explicitly approve/deny any potentially risky command. There is no sandbox being applied in this mode.

Could Codex make this "no sandbox" mode an explicit choice in that screen?

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗