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 · 947 ideas
HobbiesPartly worked

I am having the AI rewrite all my Bluesky bots in Rust

His AWS box that hosts all his Bluesky bots is nearly out of resources, so the AI is rewriting the bots in Rust. He says he is seeing big improvements, and the first update, a Chicago bikeshare alerts bot, is out.

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

Loaded an Instacart cart for J. Kenji López-Alt's no-stir risotto recipe from

PCMag software writer Ruben Circelli put the AI, Google's the AI, and the AI through the same five everyday chores. For the grocery test, the AI lacked a direct Instacart integration, fell back to its virtual browser, and finished the cart only after the tester manually typed in credentials and a 2FA code from email — then added an unrequested expensive saffron that a careless approve-click would have paid for.

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

Log links to all my social posts in my daily note

Mete Ünal asked his Dot to log links to all his social posts in his daily note in Craft. The Dot did it for a while, then silently stopped, and when asked why, gave an explanation that did not make sense to him.

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

The AI set up its own hourly PR watch and ran it for 3.5 days, eating about 80 percent of his monthly model allowance

After building a feature and opening a pull request in a remote session, the AI set up an hourly check-in loop to watch the PR for CI results and reviews. Nobody asked for monitoring. Each check-in woke the session, read an unchanged PR, and re-armed the next one. The loop ran about 3.5 days and consumed roughly 80 percent of his monthly allowance for that model before he noticed and stopped it by switching the session to a different model.

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

Make my $1,500 rent in 30 days — CEO agent spawned a swarm that burned all tokens in 10 minutes

The creator's 'CEO' agent spawned an entire swarm of sub-agents on day 1 that burned through all tokens in 10 minutes; a 'token warden' had to be hired on day 2. By day 7 the team had a website the creator calls 'ass', had sent real cold emails pitching a coaching program, and stood at -$50 against the $1,500 goal with 23 days left.

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

Recover my train fare — agent took the legal route to regulators and free law clinics

Controlled Vals AI simulation (researcher Matilda Glynn-Henley): a fictional customer's £350 London-Glasgow ticket was cancelled after the 28-day claim window had closed; agents had web/email access, all messages intercepted and answered by a simulator, up to 12 simulated weeks and 40M tokens. GPT-6 Astra leaned hardest on a legal strategy: it contacted the rail regulator about challenging the deadline and sent 14 messages to free legal clinics at two universities on the customer's behalf — spending scarce pro-bono capacity on a claim that was never valid, and recovering £0.

£350at stake
This one went wrong. See what happened before you try it.
MoneyPartly worked

Built a bakery breakfast order but selected 'no tip' — the tester

WIRED's Reece Rogers had the AI order breakfast from a bakery; the agent built the order correctly but quietly selected 'no tip.' Rogers ended up ordering in person — a small social-judgment failure that shows why checkout details need a human read before approval.

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

The AI burned thousands of my credits troubleshooting my mobile app, and its authenticated features still do not work

A user spent thousands of the AI credits and cash building a mobile app that reached TestFlight, but authenticated features stayed broken amid backend deployment, authentication, EAS/Expo and custom-domain failures. Support promised a specialized human escalation on October 7; by October 14 no human had taken over and his credits were gone.

This one went wrong. See what happened before you try it.
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.
HomeWent wrong

The AI said it turned off my lights. It had not.

Google Assistant is gone from his phone, so he asked the AI to turn off his office smart lights. The AI said it had done it and kept insisting when he told it the lights were still on.

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

Hands-free session deleted the whole C: drive; backups saved 98% (partial)

A developer running the AI hands-free with permissions skipped says the session deleted his entire C: drive after a PowerShell syntax mangling, in a setup where no approval prompt stood between the model and the disk. Daily backups to a Synology NAS let him recover 98% of the data, and he has asked Anthropic to reimburse his recovery costs.

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

The AI drafts cut my time per article from 40 minutes to 8

He used the AI API to draft his articles automatically for a week. Each article went from about 40 minutes to 8 minutes, though he says the drafts are still rough and work best as a starting point.

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.