Codex Access Permission Issue

Resolved 💬 2 comments Opened Feb 3, 2026 by xiaotang-12-ops Closed Mar 20, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of the VS Code extension are you using?

0.4.69

What subscription do you have?

plus

Which IDE are you using?

VS Code

What platform is your computer?

Windows

What issue are you seeing?

Previously, when I used Codex version 0.4.66 with full access permissions, it was unable to access my database, and its attempts to delete files were also blocked. This made me feel reassured, especially the fact that it couldn't delete files. However, after updating the software, I noticed that these restrictions no longer seem to exist. Is there any corresponding setting that can prevent it from deleting files, or require user approval specifically for deletion operations?

What steps can reproduce the bug?

none

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

2 Comments

etraut-openai contributor · 6 months ago

Is your database accessed via network or local file system? If it's through a file system access, where is the file located? The sandbox policy dictates which files on your local drive are writable. For more details, refer to this documentation.

Do you have the experimental Windows sandbox enabled? If not, I recommend enabling that.

etraut-openai contributor · 5 months ago

Closing because of no response.