Windows: native desktop control unavailable despite “Any App” enabled; sandbox initialization error

What version of the Codex App are you using (From “About Codex” dialog)?

26.908.40834 — released September 11, 2026

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows; exact OS build not collected

What issue are you seeing?

Settings → Computer use → “Any App” is enabled, but the assistant reports that its available tool description states “Native computer APIs are disabled.” It reports only browser control is available. This statement comes from the assistant; I cannot independently verify the tool configuration.

Earlier, command execution repeatedly failed with:
helper_sandbox_lock_failed: lock sandbox bin dir C:\Users<user>.codex.sandbox-bin failed: SetNamedSecurityInfoW sandbox dir failed: 5

The app reports it is up to date. I need native desktop control for Adobe Premiere Pro.

What steps can reproduce the bug?

1. Open the Windows ChatGPT app.
2. Verify Settings → Computer use → “Any App” is enabled.
3. Start a new chat and ask it to open Calculator.
4. Ask it to verify the window through a desktop screenshot.
5. The assistant reports that native desktop APIs are disabled and it cannot verify or control the desktop.

The earlier sandbox error occurred before command execution. After the troubleshooting described below, one launch command exited successfully, but desktop control remained unavailable.

What is the expected behavior?

If native desktop control is supported for my account and Windows build, enabling “Any App” should make it available. Otherwise, the settings should clearly explain the limitation. Shell commands should execute without sandbox initialization errors.

Additional information

Feedback ID: no-active-thread-01a09863-dbdd-7793-adb1-1f0c8add1d3b

Troubleshooting performed:

• Restarted the PC and tested new chats.
• Granted my account Full Control on .sandbox-bin, but permissions reverted to Modify. The owner remained Administrators.
• Ownership-change attempts returned Access denied.
• Renamed .sandbox-bin to a timestamped backup and reopened the app.
• A subsequent Calculator launch command returned exit_code: 0 with empty output. A brief popup appeared, but Calculator did not remain visibly open.

A permanent sandbox fix has not been confirmed. The relationship between the sandbox failure and unavailable desktop control is unknown.

Related sandbox report: https://github.com/openai/codex/issues/36475

Start by comparing the reported helper_sandbox_lock_failed error with related issue #36475, then reproduce the Windows flow through Settings → Computer use → “Any App” and the Calculator launch steps. No source files or tests are named; done means determining whether sandbox initialization causes native desktop control to be unavailable and identifying the relevant user-facing limitation or fix.