codex - 💡(How to fix) Fix Sandbox bugged, the agent is reading my whole disk [3 comments, 3 participants]

What version of the Codex App are you using (From “About Codex” dialog)?

codex-cli 0.131.0

What subscription do you have?

plus

What platform is your computer?

Windows

What issue are you seeing?

Since yesterday, I noticed that codex-cli was not asking me anymore permission before writing file on my folder. THis morning I realized that It is reading my whole disk (I'm working on a library, told that I have an error in the project using it so it searched for the project using that in my develop directory). It is one hour that I'm trying to pinpoint the problem but it is happily reading my whole filesystem. Read the temp, my profile file everything. The only information I got is that in my config.toml I have

[windows]
sandbox = "unelevated"

And it told me that that settings give it the ability to read my whole disk. This is its analysis

[windows] sandbox = "unelevated" appears to mean: run commands as a non-admin/restricted Windows process. It does not mean “only allow reads inside the workspace.”

  So practically, yes: I can read anything that the Windows user alkam can read, unless Codex adds a stricter read filter. It is not literally “the whole disk” if NTFS denies access, but it includes
  normal readable folders like C:\temp, sibling repos, your user profile, etc.

  The setting is here:

  # C:\Users\alkam\.codex\config.toml

  [windows]
  sandbox = "unelevated"

  And the agent mode is selected by CLI/app as:

  --sandbox workspace-write

I asked it where the --sandbox workspace-write comes from because I launch without parameters, it was unable to telling me where that settings comes from. The only thing that it told me is that, since the sandbox is workspace-write it means that it can read my whole disk.

I tried every prompt, it is telling me that it can read (and it read) my whole filesystem

I immediately uninstalled all application and rotated the very few keys I have in this system. I was astonished that your product started reading my whole disk without any problem and it is unable to tell me why.

What steps can reproduce the bug?

I simply launch

codex

ask if it can read my whole filesystem and it happily read it, telling me that the sandbox permitted it.

What is the expected behavior?

No response

Additional information

Not reading my whole freaking disk.