Show active permissions in the TUI status line
Resolved 💬 2 comments Opened May 8, 2026 by joshka Closed May 8, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What variant of Codex are you using?
CLI / TUI
What feature would you like to see?
I’d like /statusline to support an item that shows the currently active permissions profile.
Right now, when I forget which permission mode I’m in, I usually need to run /permissions or /status to check whether I’m in something like Read only, Full, auto-review, etc. It would be useful to keep that visible in the status line, especially when switching between safer and more permissive modes during a session.
Possible shape:
- Add a configurable status line item, likely named
permissions. - Display text could match or closely follow the permissions summary already shown in
/status. - Examples:
Read only,Full,Workspace (on-request),Workspace (auto-review), or user-defined profile labels. - The item could use the status line’s color styling rather than rendering as plain/dim text.
Additional information
I checked for similar issues/PRs and didn’t find an existing request for showing permissions in the status line.
Also, as a side note: I’m enjoying the newer colored status line styling. The colors look neat and make the status line easier to scan.
2 Comments
Thanks for the feature request. I explored adding a unified permissions + approval mode, but I think I prefer offering separate status line items for these two concepts. Interested what you think.
PR: #21677
Mostly the idea behind this is that being able to more quickly avoid wasted effort waiting on something I know won't succeed without a permissions bump (for whatever reason). Anything that shows the permission in the statusline satisfies that need, so no problem with the changed approach there (and no strong opinion on the direction).
The only thing I'd consider carrying over / checking for is how --yolo mode is presented (it currently shows up in /status in purple). I feel like the consideration for permission vs approval has to most clearly align with what the internal perspectives on that are and I haven't kept up with the recent changes on this.