TUI Full Access permission picker selects rejected :danger-no-sandbox profile

What version of Codex CLI is running?

codex-cli 0.140.0

What subscription do you have?

ChatGPT subscription. This appears to be a local TUI/config regression rather than an account-specific issue.

Which model were you using?

gpt-5.5

What platform is your computer?

Darwin 25.5.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Warp v0.2026.06.10.09.27.stable_01

Codex doctor report

codex doctor --json is available, but I am omitting the full report because the current local report includes unrelated state database warnings and local absolute paths. The relevant config checks are included below.

What issue are you seeing?

In the TUI, selecting Full Access from the permissions menu fails with:

Failed to set permission profile `:danger-no-sandbox`: Failed to rebuild config for permission profile :danger-no-sandbox

This does not appear to be a local config problem. The current CLI rejects :danger-no-sandbox, while accepting the canonical :danger-full-access.

Local repro:

codex --strict-config -c 'default_permissions=":danger-no-sandbox"' doctor --summary
# fails: config could not be loaded

codex --strict-config -c 'default_permissions=":danger-full-access"' doctor --summary
# succeeds: unrestricted fs + enabled network

Upstream source also appears inconsistent on current main (a5229e06867b83b2cf331c852cebfcc74828bd24):

• codex-rs/tui/src/chatwidget/permissions_menu.rs still uses :danger-no-sandbox for the Full Access item.
• codex-rs/protocol/src/models.rs defines the canonical full-access built-in profile as :danger-full-access.
• codex-rs/core/src/config/config_tests.rs explicitly rejects the legacy :danger-no-sandbox id.
• codex-rs/tui/src/chatwidget/tests/permissions.rs still expects the legacy id for the Full Access selection.

What steps can reproduce the bug?

1. Start Codex CLI TUI.
2. Open the permissions menu.
3. Select Full Access.
4. Observe the error:

Failed to set permission profile `:danger-no-sandbox`: Failed to rebuild config for permission profile :danger-no-sandbox

A command-line equivalent of the rejected profile is:

codex --strict-config -c 'default_permissions=":danger-no-sandbox"' doctor --summary

What is the expected behavior?

Selecting Full Access in the TUI should select the canonical built-in profile :danger-full-access and rebuild config successfully.

Additional information

This looks like a missed TUI call site after PR #22624 renamed the built-in full-access permission profile from :danger-no-sandbox to :danger-full-access.

Likely minimal fix: update the Full Access selection item in codex-rs/tui/src/chatwidget/permissions_menu.rs to use :danger-full-access, preferably via the shared built-in profile constant or the existing full-access preset metadata, and update the corresponding TUI test expectation.