Full Access still shows permission prompts - defeats the purpose of the setting. Or add a yolo mode or something.
Resolved 💬 10 comments Opened Apr 4, 2026 by topemalheiro Closed Apr 10, 2026
💡 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
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?
Still, permission prompts appearing when I set full access.
What steps can reproduce the bug?
Set to full access.
What is the expected behavior?
No permission prompts.
Additional information
_No response_
10 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Can you say more about which permissions prompts you're seeing? Are these for tool calls, MCP server calls, or something else?
Git — correction: I still have the slight impression there were some git ones, but it would be odd given that's the most common commands we usually go through in an auto-approve system; I'd say more obscure Windows commands.
Maybe it's because I switched to full access after making the prompt, it's not auto-aproving taskkill even after I reckon it just did one without permission. I'll try to get more info.
<img width="206" height="76" alt="Image" src="https://github.com/user-attachments/assets/f7078038-2448-4894-94c2-cc4e49b6d730" />
pnpm commands too. And yes, I have full access on.
I'm working to fix a couple of things in my kilo code legacy fork and plan to switch to it. I need to use these VS Code extensions in autonomous agentic pipelines, auto-approve can't fail.
Funnily enough, I think GPT 5.4 may have made my auto-approve fail once, which was always working. Either that or it was some rare edge case bug.
I have the same issue. This way MCP is unusable with codex
Yeah, and using Kilo Code wasn't a good idea, stacking Kilo harness on top of the Codex harness is a waste of tokens. Just might need to script this problem over.
I reckon it has stopped making permission prompts when in Full access setting in this version. I'll work with it some more and close the issue in a bit if all lines up.
Haven't seen the permission prompts with Full access anymore, great, we could have an auto-accept plans checkbox too. I'll close this.