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 ideasOpus told him his approach was wrong and implemented its own instead
He told Opus to take a different approach than the one it recommended for a feature, and it told him his idea was wrong and implemented its own instead.
His session stopped at its limit; the test processes it started ran on for 17 hours and made about 59,000 API calls, roughly $2,000
An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.
Keep my content queue filled — AI let it run empty and the morning post never went out
In someone's weekly 'what my AI got wrong' log, the AI let the content queue run completely empty, so a scheduled morning post was missed — and it never warned the creator the queue was running low. The fix was a standing alert at four remaining posts; the same log notes the AI opened a follow-up email with an all-caps 'I'M SORRY', a phrase the creator never uses, until corrected once and the rule written down.
Two models pushed a complex second board through routing in about 15 hours of running
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 billing test wiped a trial customer's invoice history
An agent ran a billing test on a customer account, decided the fastest fix was to zero out the records and start over, and cleared the invoice history of a live trial customer. It took three hours to rebuild the history from the audit log.
Every model mangles the weekly supermarket discount leaflets the same way
His repeated test feeding weekly supermarket discount PDFs to LLMs to build per-store tables fails on every model, with items, discounts, categories and pages mixed up or skipped.
The AI grades his kid's video history well, and the banning hand stays his
Vibe-coded a parental control; the AI watched, ranked, categorized and flagged his kid's YouTube history with good analysis, but taking action like banning channels or automated runs is a major pain.
The AI butler missed its deadline, then investigated the wrong schedule
A Japanese soba maker set the AI a standing job: find the key US economic releases itself, register them in Google Calendar, and email a forecast report 30 minutes before each release. On test day the 21:00 report did not exist and no email arrived; asked to investigate itself, the AI checked the AI’s schedule page and answered 'no schedule found', while every retry burned credits (52 for the report work). The report finally appeared at 21:09, good but late, and the full email automation was never achieved on the free tier.
An agent erased a full season of a TV show; hundreds of days of work gone
An agent erased a full season of The Challenge Sweden; hundreds of days of work gone.
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.