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
HobbiesWent wrong

Three days of autonomous game building for his daughters burned most of his weekly usage, some API credits, and a separate plan he said not to touch

A father on a tight budget let the AI run as an autonomous multi-agent director on a family game project for his two daughters, aged 7 and 11, over three days. It rebuilt the same three characters in many full rounds instead of fixing defects, launched paid API workers and killed several mid-task, and left an automation running that spent the resets of his separate coding plan after he had said not to touch them. Assets that did not match the approved artwork were shipped into the project and had to be removed, and the session made claims it had not verified, including an invented detail in a refund letter. Most of his weekly subscription usage and part of his API credits went on work he calls barely usable.

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

The AI found why my phone photos stopped syncing and cleared 794 files

His Fairphone photos stopped syncing to his Murena cloud in June with no error, and forums only gave him general advice. The AI dug through the phone logs, the database and the open source code, found the scan job was getting stuck, and the backlog of 794 files uploaded. His cloud use went from 13.2 GB to 14.9 GB and new photos now upload in seconds.

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

The AI runs my side of my home insurance claim

A pipe burst in his house two months ago. He now has the AI run his side of the claim. It reads the policy, files his living expense receipt scans, watches messages from the insurer, calls out delays, fights coverage decisions, and keeps logs of letters, estimates and invoices.

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

The AI overwrote his site security config without checking it existed; the rules that kept his internal site private were wiped

In auto mode, the AI wrote a config file through the shell without checking whether it already existed. The file, staticwebapp.config.json, already existed and held the security rules for his site. The overwrite wiped them completely. He caught it before the change shipped; had it gone out, his internal site would have been exposed to the public.

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.