codex sandbox help still describes Windows as restricted-token only
Resolved 💬 2 comments Opened Jun 1, 2026 by bar-d Closed Jun 8, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What happened?
The local codex sandbox docs/help still describe Windows as using a restricted-token sandbox.
Examples:
codex-rs/README.mdsays Windows support runs commands under a restricted token.- The CLI help for the Windows sandbox command says the command runs under a Windows restricted token sandbox.
The current debug sandbox implementation switches to an elevated backend when [windows].sandbox = "elevated", so the docs/help text no longer describes the full set of Windows sandbox modes.
Expected behavior
The docs/help text should mention the elevated Windows sandbox mode or otherwise describe Windows sandboxing in terms of the configured backend rather than restricted-token-only behavior.
Additional context
I searched open issues and PRs for terms including codex sandbox, Windows, restricted-token, elevated backend, and help/docs, and did not find an existing open item that appears to cover this specific local docs/help mismatch.
2 Comments
I can confirm this mismatch in the local docs/help wording.
The stale wording appears to describe Windows sandboxing as restricted-token-only, while the current implementation/configuration supports multiple Windows sandbox backends, including elevated mode. A minimal docs/help-only fix could avoid describing Windows sandboxing as restricted-token-only and instead refer to the configured Windows sandbox backend, with restricted-token wording reserved for the unelevated backend.
Suggested scope:
codex-rs/README.mdwording from “Windows restricted token” to “configured Windows sandbox backend.”codex sandbox windowshelp text similarly, so it does not imply all Windows sandbox runs use a restricted token.I’m happy to open a very small docs/help PR for this if a maintainer would like one.
Thanks for pointing this out. Most of the documentation in this README was out of date. The correct fix is to delete most of the contents, since our official Codex documentation no longer lives in this repo. I'll work on fixing that.