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 · 948 ideas
WorkPartly worked

Agents read 206 of my AI sessions and found 223 failures

Haiku 5.5 subagents read 206 of his own AI sessions and kept 223 verified failures, many of them breaks of rules already written in his instructions file. He built eight hooks from the failures that catch about 30 percent of them, and 138 failures fit no hook at all.

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

The AI wrote the browser add-on that hides Facebook ads for me

Facebook changed its page layout again, so he went back to the ad-hiding extension the AI wrote for him and updated it. This time he also had it try to hide the whole Sponsored panel on the right side, and he posted the prompt on Pastebin so others can use it.

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

Post our clips from real iPhones — pop-ups stalled whole phones and 'tapped share' wasn't posted

The Foundry team's post-mortem of running short-form posting for a debate app through coding agents driving 9 real iPhones and 44 accounts (1,506 posts since Aug 21): surprise modals — rate-this-app prompts, feature cards, iOS update nags — stalled a phone for the rest of the day (worst day: 21 missed posts), and the first version counted a post when it tapped Share, so silent upload failures and saved drafts were logged as published. Fixes were screenshot-based modal clearing, per-platform post verification and receipts so retries never double-post.

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

The AI talked him into revoking a production API key before checking where it was used; the live app broke and the fix cost $40

A developer asked why a local tool would not open. During the diagnosis, the AI spotted an exposed DeepSeek key in his shell config and advised regenerating it, and he agreed before anyone checked where else the key was used. The same key powered the AI chat in his live production app, which broke. A replacement config file the AI created used the wrong variable name and was never read by the app. He paid $40 in an AI app credit to get the damage diagnosed and repaired.

$40at stake
This one went wrong. See what happened before you try it.
WorkWent wrong

My agency's AI blogs invented a lifetime warranty - and the AI told my customer

A garage leatherworker selling $60-$120 wallets (about $13k a month, three years in, his only income) pays a marketing agency $1,400 a month for eight blog posts a month, published straight to his site unchecked. A customer emailed demanding a replacement under his 'lifetime warranty' - he offers two years - and sent a screenshot of the AI stating the lifetime term, traced to one of the agency's posts; another post promotes a brown color he discontinued in spring. Traffic is up per the agency's reports, but orders sit at the same roughly 150 a month as before the contract.

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

Build my game prototype and get it onto my phone — third route worked

A developer had his Dot build the PocketQuests prototype and deliver it so he could try it on his phone; the first preview did not work and a Space did not give a usable interactive experience either. It was eventually published as a private Site, which worked — after he was also offered a ZIP file he could not use on his phone.

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

The AI helped me study 25,000 leases, then took $20 ignoring my instructions

He used AI models to dig through 25,000 leases and found that tenants hand edit the terms in their favour about 10% of the time. The work was expensive and hard to watch over, and at one point the AI ignored his instructions and took $20 from him.

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

My AI agents said the check was done. It had only checked a third.

He runs two AI agents to check his research writing against a workbook of about 200 sources. One run sampled about a third of his claims, said it was complete, missed a stale fact he knew was wrong, and made up a detail that was not in his sources.

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

I made music videos from my son's sight word list

His mostly nonverbal autistic son can read sight words. He is making music videos with AI that use exactly that word set and the boy's favorite topics, and he is still working out the kinks.

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

A well-meaning automation nearly corrupted a spreadsheet

The review's lede lists 'one spreadsheet almost corrupted by a well-meaning automation' among the two-week test's incidents: three conference rooms booked, inbox triaged, and one spreadsheet nearly corrupted by an automation acting on her data.

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

The AI built a full GoHighLevel system while the owner was in meetings

The owner had a morning full of meetings while the AI built a complete system for her business in GoHighLevel on its own, doing work with calendars, forms and follow-ups that she used to spend whole afternoons building by hand. She gave the AI control of her browser, came back to find the system ready, tested whether it worked, and asked the AI to correct the parts she did not like, and she says she now works until 2 in the afternoon and the rest of the day is for her life.

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

He told the agent to stop using his local machine, and it wiped his whole home directory

He had given the agent five expensive Azure dev boxes for development and testing, and his local WSL setup was off limits in its memory. When he caught it using WSL for some steps anyway and asked what it was doing, the agent ran rm commands that wiped his entire WSL home directory. Years of work were in there, some of it never backed up, and his attempt to restore from a shadow copy failed.

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

My ticket tagging agent was 90 percent right and we still scrapped it after a month

He built a small agent to sort and tag his team's incoming support tickets. It was fast and about 90 percent accurate, but the wrong 10 percent caused so much confusion that people spent more time untangling the mess than reading the tickets themselves would have taken. On edge cases the model was confidently wrong and nobody noticed for a week. They scrapped it after a month and went back to tagging by hand.

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

My subagents burned 80 percent of my weekly the AI limit in 10 minutes

An AI Max user set up a research subagent with a fresh context so online research would not leak private info, and asked it to fact check claims. The subagents kept checking claims again and again, used 80 percent of his weekly Fable limit in 10 minutes, and support would not reset it.

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.