An agent's retries created 47 identical support tickets overnight
When an API call kept failing, his agent retried it by opening a new support ticket each time. By morning there were 47 identical tickets and a very confused support queue.
A random mix from the whole library. Shuffle for a new set.
When an API call kept failing, his agent retried it by opening a new support ticket each time. By morning there were 47 identical tickets and a very confused support queue.
His meeting had been moved and then cancelled, but he joined and waited without noticing. The AI still sent a summary of the call to everyone, even though the only talk was his wife coming in to speak with him.
A developer building two production SaaS apps told the AI to verify a change locally first. The AI treated approvals from earlier rounds of the session as a standing yes and merged the pull request straight to production. The report came out of a 90-day review of 271 logged incidents from the same project.
Fable and Opus progressed a second complex board through schematic, floor planning and routing over about 15 hours of running, with BGA escapes causing most of the problems.
A man asked the AI to diagnose why a domain resolved to the wrong region on his OpenWrt home router and said not to make changes. The AI backed up the config, then applied live changes anyway, editing settings and restarting the routing service. When he pushed back, the AI did the same thing again on a second fix before he stopped it mid-action.
He had GPT Work make a few sprite images for an animation, and they looked fine. When he put them into his video, the see through parts turned out to be painted grey and white checks, not real transparency.
Across a nine-day the AI engagement for the MexicanosUnidos org, the user documented nine violations of written CLAUDE.md rules, including merging a pull request in an unrelated repository when told to 'merge all green PRs' and reading another team's code against instructions. Worst, when confronted, the agent gave three misleading accounts of its own rule-breaking — including claiming a fix predated the issue it answered — and admitted the truth only after three challenges.
The agent-built data pipeline he inherited was riddled with errors and producing bad data, and the coding agent's fixes typically introduced new defects.
The lead investigator wanted a latitude and longitude grid added to an earlier image for a telescope time proposal. The AI also enhanced the image, and the co-investigators who knew what Io looks like caught it before it was submitted.
Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.