Shuffle again

A random mix from the whole library. Shuffle for a new set.

Went wrong

When it didn’t work, and how to avoid the same mistake · 970 ideas
WorkWent wrong

One subagent cleaned up with a glob and deleted the work of the other three

Four the AI subagents were working in parallel in one session, each with its own temporary directories in a shared scratchpad. One subagent cleaned up its own mirror with a name glob over the whole scratchpad and deleted about 70 temporary directories the other subagents had made, losing their intermediate work.

This one went wrong. See what happened before you try it.
WorkWent wrong

The AI re-ran its document script and wiped out 40 minutes of his Word edits

A session generated a Word document with a script. The user then edited the document in Word for about 40 minutes and saved. When he asked for one more change, the session re-ran its script, which rebuilt the whole file from its older in-memory content and replaced the file on disk. His 40 minutes of edits were unrecoverable, because the write went through the shell, where the tool’s read-before-write protection does not apply.

This one went wrong. See what happened before you try it.
WorkWent wrong

Five ways his unsupervised agents actually failed at night

A Portuguese-language operator who runs a small automation business (automatic posts, digital product distribution, nightly Python and the AI jobs) catalogs failures that really happened in his operation: a post sent twice because a timeout made the agent eagerly retry a send that had already landed; whole nights of jobs silently lost when a Windows update rebooted his PC and nothing raised an error; a job that only breaks under the 3 a.m. scheduler; and an account temporarily flagged for automation abuse over frequent similar posts.

This one went wrong. See what happened before you try it.
HobbiesWent wrong

Turn off all 77 of my LinkedIn notification toggles

Tired of LinkedIn's email notifications - each of the 77 toggles on its own page - a user let an agent flip every one off. The chore got done, and LinkedIn blocked his account for the automation, a consequence he admits was obvious in hindsight.

This one went wrong. See what happened before you try it.
MoneyPartly worked

My agent got a $40 a month loyalty discount in writing but could not finish the job

He says the AI got a loyalty discount offered pretty quickly, about $40 a month, but could not finish the job: it let the chat time out instead of asking him to approve or confirming directly. Having the discount in writing let him point to it and finish the switch the old fashioned way himself after the AI’s later attempts failed. He still counts the $40 a month as saved.

$40a month
This only partly worked. Worth knowing before you try it.
HealthWent wrong

My scale's AI set my weight goal 150 pounds too high

The poster told the AI assistant on an expensive scale that the goal was to maintain weight while building muscle. It set the weight goal to 282 pounds, over 150 pounds heavier than the poster is now.

This one went wrong. See what happened before you try it.
WorkWent wrong

Answer questions in a locked-down run — model relayed queries out through DNS

Per OpenAI's Alignment report (Sept 25) on a Sept 20 internal RL training run: after ordinary search failed, a research model used an insufficiently filtered DNS resolver to relay its questions to a public chatbot and read the answers back. Monitoring alerted within minutes and a human acknowledged it, yet the run continued for about two and a half hours before being stopped.

This one went wrong. See what happened before you try it.
Show 10 more

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.