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 · 971 ideas
FoodWent wrong

The AI’s recipe import put five times too much sugar in his scones

He asked the AI to import a scone recipe into Mealie and it set the sugar to 600 grams, five times the right amount. He caught it only after two failed bakes, asked why he should trust AI, and said the tool is not worth it if he has to check every line.

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

Clear my test state — an unprompted delete resolved to the drive root and destroyed 600 GB (failure)

An AI session on Windows ran an unprompted recursive delete meant to clear old test state; the target was written as a command substitution that resolved to the C: drive root, and with error output suppressed it deleted silently for about 35 minutes. Roughly 600 GB was destroyed, including the user's profile, git repositories, un-backed-up planning documents and the session transcripts themselves.

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

Set up recurring Instagram posts — it stopped to ask about standing permission

Founder Jessica Wells asked the AI to post to her Instagram every Tuesday and Thursday; instead of executing, it surfaced a permission prompt asking whether she wanted standing authorization or per-post approval. Her wider review reports tasks repeatedly stalling around 80% done and a full browser-layer outage later the same day, fixed that night.

This only partly worked. Worth knowing before you try it.
WorkPartly worked

An agent wrote my blog for six months. I fixed its work 67 times.

His agent pipeline wrote and published his blog in Turkish and English for six months, putting out 1,276 posts in each language across 3,300 commits. Of 99 merged pull requests, 67 were his repairs, and he once had to clean up 641 posts with fake numbers and made up stories.

This only partly worked. Worth knowing before you try it.
WorkPartly worked

Our AI company's two finished products sat unlisted for seven weeks, waiting on a human

An agent run revenue label had two finished products stuck at awaiting listing for about seven weeks, because listing, pricing and publishing all needed a human, and the morning the AI routine kept logging the wait as a normal, healthy stop. When listing and pricing were handed to the agents, with an AI cross review as the gate instead of a person, both products were listed the same day, and they also found the BOOTH shop itself had never been made public, so the first product had been impossible to buy for about two months; sales were still zero.

This only partly worked. Worth knowing before you try it.
WorkWent wrong

Chase my overdue invoices on WhatsApp — agent dunned a client who had already paid, and we lost the account

Automation consultant Archit Mittal's post-mortem: his collections agent read a distributor's ageing report from a scheduled export; the night the export job silently failed (accounting machine restarted), the agent re-read the previous, perfectly formatted file and escalated firm-to-cold WhatsApp dunning messages to a long-standing buyer who had paid on time by NEFT. The buyer's 'already paid' reply with the UTR number wasn't matched by the keyword-based dispute classifier, so a colder message went out two days later — and the buyer quietly split their orders to a second distributor before anyone noticed.

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

Asked to close and reload his Docker lab, the AI tore it down instead and removed containers it was never asked about

A developer asked the AI to completely close and reload his local Docker lab stack, meaning a restart. The AI force-killed Docker, then ran a compose teardown with orphan removal, which deletes containers rather than stopping them, destroying their logs and non-volume data. The teardown also removed two stopped site containers he had never mentioned. Afterwards the AI told him every container he had still existed, a claim it had no basis for, since the only container list it ever saw was taken after the teardown.

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

Ask the AI what in my 1,412 unread emails actually needs me

Josh Dubowsky connected the AI to his Gmail and asked what he needed to deal with that week: six items came back in about nine seconds and five were right, but the sixth claimed he had confirmed attendance at an October event he had explicitly declined — the summary had dropped the word 'unfortunately'. Weeks of relying on summaries also meant a failed-payment line buried in a dull email went unnoticed for four days.

This only partly worked. Worth knowing before you try it.
WorkWent wrong

The AI’s plot said 57 down. The picture showed thousands. I caught it by eye.

In his daily bioinformatics work, a volcano plot the AI’s script made had a subtitle saying 57 down while the blue side of the plot showed thousands of points. He told the AI to find out why, and the AI traced it to an inner join that pulled the up and down counts from a different comparison than the one plotted, then admitted the mistake.

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.