You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Not accepting all permissions when setting Full access after doing the first/initiating prompt #17653
After making the initiating prompt, setting to Full access doesn't work; the safe way is to set it before the prompt.
This starts being a nuisance since when we switch accounts, Full access setting doesn't stay. As well as it being on the right corner makes it harder to notice (I prefer it on the left like before, and I fully support the chat width being 100% of the side panel for the record, that's not in question).
What steps can reproduce the bug?
Make a prompt and set the Change permissions setting to Full access.
changed the title [-][BUG] Not accepting all permissions when setting Full access after doing the first prompt[/-][+][BUG] Not accepting all permissions when setting Full access after doing the first/initiating prompt[/+]on Apr 13, 2026
The first issue is my complaint about Full access, which, for the most part, is fixed except for this problem.
The second is about command permissions not staying over account switches, I reckon, and some other settings. It's asking for certain settings to be account-agnostic, and to be associated with the Codex instance, I presume.
Activity
[-][BUG] Not accepting all permissions when setting Full access after doing the first prompt[/-][+][BUG] Not accepting all permissions when setting Full access after doing the first/initiating prompt[/+]github-actions commentedon Apr 13, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
topemalheiro commentedon Apr 13, 2026
The first issue is my complaint about Full access, which, for the most part, is fixed except for this problem.
The second is about command permissions not staying over account switches, I reckon, and some other settings. It's asking for certain settings to be account-agnostic, and to be associated with the Codex instance, I presume.
mtfelian commentedon Apr 24, 2026
Now many things like using playwright became completely unusable because of this with constant asking for permissions. Solution with
in config.toml works but that's not a good practice