I would love to see your prompt(s) and how you managed to make it do this.
I’ve been using Codex in full access mode constantly for the past couple months on a Pro plan and I haven’t had a single incident like this. I’ve used it across macOS, Linux, and Windows as well, so my usage isn’t limited to a specific setup either.
I never sent any prompts to it, it did all of this during the installation. Here is one related GitHub issue I found for it https://github.com/openai/codex/issues/12343 Looks like they don't intend to change this.
Your earlier post is misleading, since "it" sounds like the model, not the installer. (of course if the latter was created by the former, its basically the same complaint, but I suspect what you are talking about was a deliberate design decision by a human)
The problem doesn't exist when granting codex full access. Codex makes you choose upon first launch to "Set up default sandbox" or to "Use non-admin sandbox". The default option creates two new users and messes with NTFS permissions.
I'm taking the person you are replying to as being snarky. But, I believe OP is right, treat these with zero trust.
> I’ve been using Codex in full access mode constantly for the past couple months on a Pro plan and I haven’t had a single incident like this. I’ve used it across macOS,
That is not how it works: the "but it works for me" is a logical fallacy.
Haven't you followed a bit all the posts about models, for example, escaping their environments?
The "but it works for me" is a random data point: an anecdote.
That there are people / companies where models ran wild and destroyed files / messed up projects is a fact.
When there are documented cases of stuff gone wrong, people must find ways to protect their data.
We literally see posts frontpage, daily, about AI sandboxing and we regularly see posts about AI escapes or AI SNAFUs.
And you come and post "show me your prompt, for it works on my machine"...