Sandbox leaves ACLs and ownership

“This is not just cosmetic ACL noise: Python/pytest can create owner-only temp directories which the normal user then cannot access.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/15235/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Fading. No reports in the last 7 days and 1 the week before, down from 2 a week at the late-September peak. A workaround is known.

Windows elevated sandbox leaves ACL changes and sandbox-owned files. Writable roots keep added ACEs after the run ends, and files made by the sandbox account are inaccessible to the normal Windows user.

Is this your bug?

File my report

Where: Windows sandbox
Versions: 0.157.0 to 0.164.0
Platforms: Windows
How bad: Breaks a normal workflow.

Not quite your bug?

Sandbox ACL refresh fails2 people
Windows sandbox setup access denied2 people
Nested folder writes denied2 people

Original reports3, newest first

Oct 27, 2026Codex CLI Windows elevated sandbox — project source inaccessible to normal Windows userOn GitHub#57521
Sep 27, 2026Windows elevated sandbox leaves permanent ACEs and sandbox-owned 0o700 dirs; need cleanup (and consider MXC default)On GitHub#48743
Sep 27, 2026Windows workspace-write sandbox persistently mutates project ACLs/ownership; MXC avoids itOn GitHub#48721