Repository navigation
Model permission UI shows Full Access, but runtime remains restricted with no escalation path #19356
Description
What version of Codex CLI is running?
codex-cli 0.124.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.5
What platform is your computer?
Darwin 25.3.0 arm64 arm
What terminal emulator and version are you using (if applicable)?
iTerm2
What issue are you seeing?
Title: Model permission UI shows Full Access, but runtime remains restricted with no escalation path
Observed:
The UI showed:
3. Full Access (current) - Codex can edit files outside this workspace and access the internet without asking.
But the model/runtime context still reported:
sandbox_mode = workspace-write
network access = restricted
approval policy = never
Impact:
The agent could not bind a local Vite dev server socket or kill/restart a local process.
npm run dev failed with:
Error: listen EPERM: operation not permitted ::1:5173
The agent also could not request escalation because approval_policy was never.
After switching to:
2. Auto-review
The runtime exposed an escalation path, and the same dev-server action succeeded via require_escalated.
Vite started at http://localhost:5174/.
Expected:
Full Access should either actually provide unrestricted execution, or the runtime context should match the UI state. It should not be less capable than Auto-review.
Actual:
Full Access appeared selected in UI, but the runtime behaved like restricted/no-approval mode.
Likely area:
Permission state propagation between UI selection and model tool runtime, possibly after model/session switch.
What steps can reproduce the bug?
Re-run the run dev
What is the expected behavior?
3 full access works.
Additional information
No response
Activity
github-actions commentedon Apr 24, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
/permissionschanges do not propagate to the active session incodex-cli 0.124.0#19256Powered by Codex Action
Asentrixx commentedon Apr 24, 2026
Exacct same thing happening to me, cant do shit, stck in sandbox
onlynextstep commentedon Apr 24, 2026
+1 same
derspotter commentedon Apr 24, 2026
fix this please!
-0.1 of global gdp lol
Choimoe commentedon Apr 24, 2026
I encountered the same issue on Ubuntu 22.04.5 with Kernel version 5.15.0-176-generic, after the update. When using grpc and brpc, both fail to start sockets with the errors:
127.0.0.1:18080: Operation not permitted/Fail to create socket: Operation not permittedManually running the program works without issues.
derspotter commentedon Apr 24, 2026
configure the config.toml then it works again
viyatb-oai commentedon Apr 25, 2026
Can you try
0.125.0and see if this fixes the issue?xukl commentedon Apr 26, 2026
Fixed for me in 0.125.0. Also was good in 0.123.0. Only broken in 0.124.0.
I believe it's a duplicate of #19256 ?
inshell-art commentedon Apr 26, 2026
Confirmed fixed for me in codex-cli 0.125.0.
Full Access now reports the expected runtime permissions:
The issue was reproducible for me in 0.124.0 and no longer reproduces after upgrading. Closing as fixed / likely duplicate of #19256.
/permissionschanges do not propagate to the active session incodex-cli 0.124.0#19256