codex in vscode does not respect any change to config.toml

Resolved 💬 4 comments Opened Dec 13, 2025 by orazdow Closed Dec 13, 2025

What version of Codex is running?

0.64.0-alpha.10

What subscription do you have?

pro

Which model were you using?

5.1-codex-max

What platform is your computer?

windows

What issue are you seeing?

I need codex to make edits only with approval, not automatically, so I edited config.toml to: approval_policy = "untrusted".
Even after creating a new agent and rebooting windows codex in vscode will always make edits without asking for approval. It reports that its approval policy is still "on-request", and any advice asked of it leads to hallucinated vscode settings that are not available. Shouldn't it be possible to change such an important setting?

What steps can reproduce the bug?

Use of the vscode extension. The exe used directly outside of vscode does respect the config.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗