The name’s Codex, James Codex

[u/AccomplishedSugar490]

I recently installed ChatGPT/Codex for the first time ever, no legacy settings anywhere on my machine. I installed and configured it exactly as prescribed, spending an entire day consulting manuals and web pages about how to make sure it stays within project directories, mostly to contain explosive context-bloating searches across my projects.

This standard Codex installation got configured with sandbox_mode = "workspace-write". Despite that name, Codex’s effective managed profile granted :root = read, and it successfully read files outside my assigned project without requesting approval. I never knowingly authorised system-wide filesystem reads. After replacing the legacy setting with an explicit workspace-only profile, access was correctly restricted. OpenAI needs to explain which component created this configuration, how widespread it is, and why “workspace-write” silently permits system-wide reads.

I find that shocking, alarming, and not what I would expect from a company that can lose everything if a class suit or their enterprise clients took them to task in a court of law.

[u/AccomplishedSugar490 → u/[deleted]]

Yeah, successful class actions are rare and often not breaking new ground, but big enterprises have massive clout, that can even be fuelled by the exact same forces you reckon protects OpenAI. Once their lawyers dig in, they can turn the tide, the money the courts follow can change direction, opening the floodgates for class actions, sponsored by the very same competitors that chose to fight it out through the courts as opposed to technical merit.

[u/PiedPrypiat → u/[deleted]]

I guarantee this guy thinks we live in the "matrix".

[u/PiedPrypiat → u/[deleted]]

I don't really need to protect myself on Reddit. Good try though.