approval_policy = "untrusted" is not respected by vscode extension

Resolved 💬 5 comments Opened Oct 21, 2025 by wiegell Closed Nov 4, 2025

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

Extension - Version 0.4.21

What subscription do you have?

Business

Which model were you using?

gpt-5-codex

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

If i put approval_policy = "untrusted" in ~/.codex/config.toml it is not respected by the agent. It can still run e.g. mkdir whatever. When you ask the agent what policy it has currently, it says on-request.
The policy is respected when running codex directly as a cli though, but _not_ via the extension

What steps can reproduce the bug?

See above

What is the expected behavior?

Should ask for any shell command

Additional information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 10 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#3545

Powered by Codex Action

lichenometry · 10 months ago

I'm seeing the same issue with approval_policy = "never"

linear[bot] · 10 months ago

from shijie.rao:

We are currently working on custom mode which will allow the extension to use approval and sandbox polices from config.toml.

linear[bot] · 9 months ago

from shijie.rao:

Hi! Just a quick update that we have added custom mode to our latest VSC extension which will let you use polices defined in your config.toml if you wish to. Please let us know if there is any questions. Thanks!

wiegell · 9 months ago

@linear i don't see any new modes in the extension? is this released?