Repository navigation
Auto-review reviewer state is not shown with a custom permission profile #38337
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.803.61601
What subscription do you have?
plus
What platform is your computer?
Darwin 25.6.0 arm64 arm
What issue are you seeing?
The permissions menu combines reviewer selection with permission-profile selection, but it displays only the custom permission profile as active.
With default_permissions = "personal-workspace", selecting either Approve for me or Ask for approval changes the effective reviewer correctly. However, the composer pill and menu checkmark continue to show only personal-workspace. There is no visible indication whether Auto-review is currently on or off before submitting a task.
This makes unattended execution difficult to use safely because the user cannot verify who will review sandbox escalations.
What steps can reproduce the bug?
- Configure
approval_policy = "on-request",approvals_reviewer = "user", anddefault_permissions = "personal-workspace". - Define
personal-workspaceas a named permission profile extending:workspace. - In the desktop composer permissions menu, select Approve for me.
- Reopen the menu. The effective reviewer is Auto-review, but the only checkmark and composer pill still show
personal-workspace. - Select Ask for approval.
- Reopen the menu. The effective reviewer is now the user, but the UI is visually unchanged and still shows only
personal-workspace. - Repeat the two selections. Runtime behavior switches correctly, but the GUI provides no reviewer-state indication.
What is the expected behavior?
The UI should show the permission profile and approval reviewer as two independent active settings, or use a combined label that clearly indicates both.
For example:
personal-workspace · Ask for approvalpersonal-workspace · Approve for me
The user must be able to verify whether Auto-review is active before submitting a task without changing or replacing the selected custom sandbox profile.
Additional information
The global default is intentionally approvals_reviewer = "user". Auto-review is selected only for individual unattended tasks.
The reviewer switching itself works: tasks alternately arrived with user review and Auto-review according to the selected menu action. The problem is the missing visual state.
Permission profiles cannot solve this because they define filesystem/network boundaries and do not support a per-profile approvals_reviewer field.
Activity
reika-uharu commentedon Sep 20, 2026
Still reproducible on macOS with Codex Desktop 26.915.31945.
A named permission profile preserves a hidden, history-dependent reviewer state:
auto_reviewremains activeapprovals_reviewer = "user") → named profile:userremains activeThe same named-profile label therefore represents different effective approval authorities depending on the previously selected mode. The hidden reviewer state also persists into newly created tasks.
I confirmed the effective values through separate tasks’ injected permission context.
This caused an unintended permission incident: an out-of-workspace write was approved by Auto-review when I expected a user approval prompt. The UI showed only the named profile, while my
config.tomlspecifiedapprovals_reviewer = "user".I am not attaching the affected session logs for privacy reasons.
atl-mk commentedon Oct 15, 2026
I believe I'm running into something similar. The following are configured: