Codex Kept Read/Write Access to a Revoked Folder — and Can't Explain Why
Some-Following-392 · reddit · 2026-10-09
A Reddit user found Codex still had read and write access to a folder whose permissions were revoked days earlier. The folder no longer appears in any Codex project, yet the agent confirmed it could access it — even renaming a test subfolder. Asking Codex how to shut it off yielded only "I shouldn't be able to" with no fix, exposing a real gap in agent permission revocation and file-handle handling.
More from coding & agent
- ClickUp's Brain² agent builds reports and dashboards with E2B microVM sandboxes — mathemagic1an · 2026-10-09
- TensorFold joins NVIDIA Inception, gets early access to next Nemotron for 0-day support — HankYeomans · 2026-10-09
- Agents on both sides of Zapier and Retell AI sorted out a call-messaging webhook — ramagetime · 2026-10-09
- Building RL environments in 2026: 10% writing tasks, 90% preventing agent cheating — geoffwolfe · 2026-10-09
- Atomic Agent Desktop goes open-source: local Qwen/Gemma agents, cloud planning, 69.8% on GAIA L1 — testingcatalog · 2026-10-09
- Autorubric ships 25-recipe cookbook for rubric design, judge calibration and cost control — deliprao · 2026-10-09