VSCode Codex doesn't respect sandbox_workspace_write.writable_roots in config.toml

Resolved 💬 4 comments Opened Dec 15, 2025 by yiteng-guo Closed Dec 16, 2025

What version of Codex is running?

codex-cli 0.72.0

What subscription do you have?

azure foundry

Which model were you using?

gpt-5.2

What platform is your computer?

_No response_

What issue are you seeing?

I think vscode-codex overwrites the sandbox_workspace_write.writable_roots with the current project dir so it doesn't respect the one in config.toml

What steps can reproduce the bug?

In vscode-codex extension (version 0.4.51), asking codex

> what's your sandbox_workspace_write.writable_roots value?

sandbox_workspace_write.writable_roots is:
- /path/to/the_current_project_opened_in_vscode

even if in config.toml, I set

[sandbox_workspace_write]
writable_roots = ["/path/to/my_other_project"]

If you run codex cli in the current project dir and ask them the same question, it responds

• writable_roots is:
  - /path/to/my_other_project

What is the expected behavior?

vscode-codex should behave in the same way as codex cli.

Additional information

_No response_

View original on GitHub ↗

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