Permission dropdown reverts to Local dev after send, while runtime remains full access #29586

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

Version 26.616.71553

What subscription do you have?

$200

What platform is your computer?

Windows 10 Pro

What issue are you seeing?

Codex Desktop remembers “Full access” in the permission dropdown before sending a message, but immediately after pressing Send the dropdown visually changes to “Local dev”. The agent runtime still receives full access (danger-full-access, unrestricted filesystem, approval policy never). I disabled the Chrome browser extension, restarted Codex, and tested in a new chat; the issue still occurs. This appears to be a send-time UI state/profile-label mismatch rather than an actual permission downgrade.

What steps can reproduce the bug?

1. Open Codex Desktop on Windows.
2. Start a new chat in any project.
3. Select “Full access” from the permissions dropdown.
4. Confirm the dropdown displays “Full access” before sending.
5. Send any message.
6. Observe that immediately after sending, the dropdown visually changes to “Local dev”.
7. Ask the agent what runtime permissions it sees.
8. The agent still reports full-access runtime settings: danger-full-access, unrestricted filesystem, approval policy never.

I also disabled the Chrome browser extension, restarted Codex Desktop, and repeated the test in a new chat. The same behavior still occurred.

What is the expected behavior?

The permissions dropdown should continue to display “Full access” after sending a message when the active runtime permissions are full access.

If the runtime remains danger-full-access / unrestricted filesystem / approval policy never, the UI should not visually revert to “Local dev”. The displayed permission mode should match the actual active runtime permission profile.

Additional information

No response