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
WorkPartly worked

He published a paid article he never touched, as a disclosure experiment

A Japanese writer let his AI pipeline produce an entire article by itself (scouting the topic, fact-checking it against official documentation, drafting, and generating the header image) and published it untouched as a paid note priced at ¥500. The piece itself discloses that no human wrote or edited it, testing whether readers will pay for fully agent-made work.

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

Cline cleanup command hit the wrong drive and deleted about 1.5 TB of a family's photos and files

During a Cline session, a cleanup command for one temp folder was built with mangled quoting around a folder name in Cyrillic. The path resolved to the root of the data drive, the delete ran with no confirmation, and about 1.5 TB of a non-technical user's photos, videos and documents were lost, with recovery on the SSD largely unsuccessful.

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

Reached Delta's Confirm & Submit screen for a $250 flight-delay claim in

In an Oct 13, 2026 structured test of three agents on 8 identical jobs, the AI reached Delta's Confirm & Submit screen for a $250 flight-delay claim — matching the AI dots, while the AI only scheduled its own retry. The test used a made-up family and nothing was actually submitted.

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

My Dot was bad at applying to jobs and sending email for me

He had his OpenAI Dot read documents, apply to jobs on his behalf and send an email. Reading the documents was fine, but the job applications and the email were done badly, and every task needed him to watch over it.

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

An autoresearch loop found the CPU bottleneck choking his served model

Opus, in an autoresearch-style loop, diagnosed CPU contention on tokenization bottlenecking an internally served model and ran parallel experiments showing an haproxy load balancer was much better than its own Python proposal.

This only partly worked. Worth knowing 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.