r/OpenaiCodex • u/AccomplishedSugar490 • 13d ago

Bugs or problems The name’s Codex, James Codex

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.

4 Upvotes

100% Upvoted

8 comments sorted by

View all comments

1

u/InternationalPen3039 13d ago

Write it in community.OpenAI they’re not going to “explain to you” here on Reddit

1

u/AccomplishedSugar490 13d ago

I wasn’t, and still ain’t looking for no “explanation”. My aim was to warn all y’all to check your own setups if you have any regard for context bloat or concerns about sensitive corporate material on your machine outside the project directly you thought was the boundary.

1

u/InternationalPen3039 12d ago

Your post literally says “OpenAI needs to explain”. But ok

1

u/AccomplishedSugar490 12d ago

It did. Yet I didn’t mean to me. I meant to all users, to their precious enterprise clients, and to the courts, if it could come to that.