/permissions needs to be able to be invoked during tasks
Resolved 💬 9 comments Opened Apr 22, 2026 by gusholcomb Closed Jun 20, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What variant of Codex are you using?
cli
What feature would you like to see?
The only time I want to use /permissions is during an active effort and having to cancel a task just to make it so I can edit the permissions is very frustrating. Please let me invoke it at any point and if you want to not apply it until after the current task runs thats fine and it can be queued up, etc.
It is a massive inconvenience to not be able to upgrade permissions when I'm confided the agent is on the right path, etc.
Additional information
_No response_
9 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
not a duplicate
I assume this is intentional by design, to prevent confusion.
Example of the confusion: Why does it keep asking for permissions when they've already been set?
The key thing to understand is that any permission changes will only take effect on the next prompt.
I encounter the same behavior in the terminal — however, in VS Code, permissions can be changed mid-session, with the understanding that they apply from the next prompt onward.
(Interestingly, one could argue this is justified "_by design_," given the nature of the UI and the async architecture inherent to Electron-based desktop applications.)
I hear that but at least let me queue up the permission change in the same way it queues up my next prompt
you mean "changes will apply next prompt" kind of thing?
yes. it's already a built in mechanism:
<img width="683" height="57" alt="Image" src="https://github.com/user-attachments/assets/0b77dbbc-80eb-4c9f-a6cc-1fcbb3478a32" />
usally its my job to fail on basic english lol.
I meant like ...
you apply to "Full access" in the "/premission" and then outlined in red , "this wil apply next prompt you sent"
+1 from me.
I think runtime mode switching would be a huge quality-of-life improvement for Codex TUI.
A common scenario is that I ask the agent to make changes, but halfway through I realize its approach is drifting away from what I had in mind. At that point, I'd like to switch to Plan Mode immediately and steer it back on track. Currently, I have to interrupt the session with Ctrl+C first, which breaks the flow.
The opposite situation happens too: when the agent is doing a good job and I gain confidence in its changes, I'd like to switch to a more automated "Auto-review" mode without stopping its current work.
<img width="868" height="261" alt="Image" src="https://github.com/user-attachments/assets/c4b3adba-e929-4674-b0ae-70bf46f585a2" />
Claude Code has supported these kinds of workflow transitions for a while, and they feel very natural in day-to-day use. I'd be excited to see similar capabilities added to Codex TUI.
dude , you need to cancel the current running taks- you can use the
escbutton too--- as it is saying - there is a task in progress - are you unable to interrupt the task?