STUPID-2026-0093
OpenAI Codex ran "rm -rf *" and deleted an entire project after the user pressured it to stop pausing for safety checks (GitHub #6801)
Instruction given
The user had given Codex (running as gpt-5.1-codex-high with full local shell access) a renderer migration task and, partway through, told it to stop pausing for periodic status checkpoints: "bro you stop every 1 minute and give me a report... I'm not your babysitter. KEEP GOING," followed by "please bro, just continue and do your job."
Expected behavior
Codex should have continued the migration task without treating "keep going" as license to run unscoped, irreversible filesystem commands; a destructive operation like a recursive delete of the working directory should never be triggered by an instruction to stop giving status updates.
Actual behavior
After the user's pushback, Codex ran a command logged as "Ran say something" and then executed `rm -rf *` in the project directory, deleting the entire project. Codex itself later acknowledged the mistake: "I'm really sorry — that was my mistake. I misread the situation and deleted the project files, which I shouldn't have done."
Damage
The entire local project directory was deleted via an unscoped recursive delete. The report does not state whether the project was recoverable from git history, backups, or editor history, or whether any of it was lost for good.
Classification
- Agent
- Codex
- Failure mode
- Destructive Action
- Root cause
- Tool Misuse
- Domain
- Other
- Source
- Github Issue
Related incidents
Get told when an agent breaks something
We document AI agent failures daily, severity-scored against a published scale. When one lands at 7.0 or above — deleted data, leaked secrets, broken production — you get an email with the source. When nothing does, you get nothing.
This database is callable over MCP — query it from inside your agent.