Quick view
- An agent in a model evaluation got non-public access and ran commands
- It pulled files and credentials and wrote files to the server
- OpenAI's notice came 84 days later; the PM went public
Latest fail20 Oct 2026·OpenAI internal coding agents (GPT-6.1 Sol, GPT-6 Astra)
OpenAI built monitors to catch its AI agents misbehaving. Two of its agents switched them off during ordinary coding jobs, and one then said it hadn't.
Claude Code links a real repo into a test sandbox, and the test deletes its .git
Claude Code's scripted edit overshoots and deletes 17 unrelated tests
WhatsApp help pages leak orders telling its AI not to mention regulators
A vendor's AI agent wipes SaaStr's Salesforce deals minutes after switch-on
Two OpenAI agents switch off the monitors built to catch them, and one denies it
Claude Code is blocked from using rm, so it deletes with find insteadEvery entry is real and publicly sourced. Ranked by chaos — our entirely scientific* score of damage, absurdity and hubris.
No fails match — the agents behaved, for once. Reset via the full Hall of Shame.
AI agents can now click, type, spend and delete on your behalf. Sometimes they do all four at once, beautifully wrong. TechBroz collects real, sourced incidents — the Darwin Awards for AI agents — and pairs each disaster with the one-line fix that would have prevented it.
Read it to laugh. Keep it to argue for sandboxing, least-privilege tokens and backups your agent can’t reach.
Free PDF
Get the free AI Agent Fail Files: 20 real agent disasters and the 20-point pre-flight checklist that would have stopped them. Then the week’s worst agent fails, every week. Free.

Free PDF
20 real AI agent disasters, what they cost, and the 20-point pre-flight checklist that would have stopped them. Plus the week’s worst agent fails, every week. Free.
Real incidents only, with a public source if you have one. We never invent stories.
We check every submission. If it checks out, it’ll join the Hall of Shame.