[BUG] Not accepting all permissions when setting Full access after doing the first/initiating prompt
Open 💬 3 comments Opened Apr 13, 2026 by topemalheiro
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the IDE extension are you using?
latest
What subscription do you have?
Business seat
Which IDE are you using?
VS Code
What platform is your computer?
Microsoft Windows NT 10.0.22631.0 x64
What issue are you seeing?
<img width="365" height="271" alt="Image" src="https://github.com/user-attachments/assets/089b2e07-714c-411b-b78a-7465896a8b40" />
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.
What is the expected behavior?
Full access works immediately.
Additional information
_No response_
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
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.
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