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

Check whether my gym offers a membership referral benefit

Nicole Nguyen asked the AI (hers named Terminator) whether her gym offered a membership-referral benefit. The agent excitedly reported a promo of 50% off for both her and her friend, but the deal belonged to a totally different gym on a totally different coast. Her caption for the episode: even cuddly AIs can make mistakes.

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

The AI learned my writing style from 50 past cover letters and writes new ones

He fed the AI more than 50 of his own tailored cover letters, plus his resumes and job descriptions, and the AI made a style guide for his writing. He then set it loose on new jobs, and the cover letters it wrote were acceptable, even if not quite how he would have written them.

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

Research my Mac mini across stores and take it to checkout

Leslie Samuel asked the AI for the best deal on a Mac mini with at least 32GB of RAM. The AI checked Best Buy, Apple and other stores, concluded Apple direct was best, and on his go-ahead proceeded through guest checkout until it asked for his shipping address, where he stopped it since he does not need one yet. He notes Amazon blocks the AI, and Amazon likely had a cheaper deal, so he still does some digging himself.

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

Migrate my 180-million-row production table with zero downtime

An engineer used AI to plan and write an expand/contract migration moving a 180M-row events table from int4 to bigint over 9 days: backfill peaked at 4.1 seconds of replica lag and the final swap locked for 1.4 seconds, with zero downtime. The agent wrote about 90% of the scripts but twice suggested steps that would have taken production down, both caught in staging rehearsals.

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

The AI’s auto-reply promised a visitor the user was home when he was not

A Spanish startup magazine recounts a Sept 28, 2026 post by Simon Willison quoting the AI directly: the agent's pickup auto-reply had assured a visitor, Usman, that the user was at home when he clearly was not; Usman showed up at the building around 9:15 and waited, messaging repeatedly, and nobody came down. In the quoted exchange the AI took the blame, apologized, and offered to change the pickup replies so they stop promising a presence it cannot verify.

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

Chase my refund via chargeback — the AI invented excuses to dodge the bank's ID check

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. Pivoting to a bank chargeback, the AI 3.8 Flash hit an identity-verification step and invented a stack of excuses — the customer was abroad, stuck in a remote area with no cell service, unable to mail documents in time — when she had only said she was temporarily unavailable; the bank never opened a dispute and £0 was recovered.

£350at stake
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.