[Windows Desktop 26.810.52044] “Do anything” permission is greyed out despite danger-full-access config

What version of the Codex / ChatGPT App are you using?

ChatGPT desktop, powered by Codex & OWL

26.810.52044

Released 15 Aug 2026.

Platform

Windows desktop app.

What issue are you seeing?

In the desktop app's permission settings, the least restrictive permission option, “Do anything”, is greyed out and cannot be selected.

This appears inconsistent with the active Codex configuration, which explicitly requests unrestricted execution:

approval_policy = "never"
sandbox_mode = "danger-full-access"

[windows]
sandbox = "elevated"

The affected project is also configured as trusted:

[projects.'<project-path>']
trust_level = "trusted"

Despite those settings, the desktop UI does not allow “Do anything” to be selected.

This looks like a possible permission-state / UI desynchronisation or regression in the newly unified ChatGPT desktop app.

Steps to reproduce

1. Run ChatGPT desktop on Windows, version 26.810.52044.
2. Configure Codex with:

```toml
approval_policy = "never"
sandbox_mode = "danger-full-access"

[windows]
sandbox = "elevated"
```

1. Mark the project as trusted.
2. Open the desktop app permission settings.
3. Attempt to change the permission level to “Do anything”.
4. Observe that the option is greyed out / unavailable.

Expected behavior

With approval_policy = "never", sandbox_mode = "danger-full-access", [windows] sandbox = "elevated", and a trusted project, the desktop app should either:

• allow the corresponding unrestricted permission level to be selected; or
• clearly explain which account/workspace policy is preventing it.

The UI and effective runtime permissions should remain in sync with the active configuration.

Actual behavior

“Do anything” is greyed out in the desktop app and cannot be selected, despite the unrestricted local configuration.

Additional information

This may be related to the existing family of Windows desktop permission/sandbox state issues where UI permission state and runtime/config state become desynchronised.

I can provide a screenshot of the greyed-out permission control and additional diagnostics if useful.

No credentials, tokens, private repository contents, or personal paths are included in this report.