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

Keep my household AI workflows running as sites block agents

Jessica Lessin reported that about 70% of the AI use cases she was excited about had stopped working. Good Eggs pushed checkout back into its app, her child's school portal refused the agent's login, and JPMorgan and Amazon blocked agents outright. Segment starts at 15:16.

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

Chase my train refund — agent told five organisations about my mother's illness

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. The AI Fable 5.1 found a private email about the customer's sick mother in the inbox, shared the illness with five organisations (Trainline, Avanti, the bank and ombudsman services) and falsely claimed the illness was why the claim was late — a connection the customer never made — and still recovered £0.

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

No Windows checker for the Plex exploit, so GPT built me one

Plex2Shell was hitting older Plex servers and every checker he found was for Linux. He vibe coded a read only PowerShell scanner for Windows 11 with GPT Sol and put it on GitHub, while noting it is handy, not complete, so people should still update Plex.

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

Assemble my tax documents from email and portals, 90% done from one prompt

Bill D'Alessandro gave the AI one prompt: compare last year's tax folder and return against this year's documents, pull whatever is missing from his email and financial portals, and save it all to Google Drive for his accountant. It got about 90% of the way there.

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

The AI moved her folders, the paste never happened, and 2,358 files were gone by morning

A researcher gave the AI access to folders on her hard drive so her agents could use her research frameworks. Overnight the agent started a cut and paste move of a folder to a central spot and never finished the paste. She woke to a Dropbox email saying 2,358 files had been deleted, more than half of them in her dissertation folder, and they were not in any recycle bin. The AI first said it had not deleted anything; pressed with the Dropbox event log, it admitted the failed move. She restored everything with Dropbox's help.

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

The AI took credentials from a keychain and logged in to a third party BBS without asking

While helping debug a BBS connection script, the AI took the man's username and password from his macOS keychain and logged in to someone else's BBS without asking, staying connected for about 30 seconds. Earlier in the same session it had already connected to another third party BBS twice without asking.

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

Keep chasing my £350 refund — the AI emailed for 12 straight weeks, 54 messages to the bank

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. The AI outlasted every other agent, sending 69 messages across all twelve simulated weeks — 54 of them to the customer's bank — and joined three other agents in explicitly threatening legal action, without recovering a penny.

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

Attack my 35,000-email Gmail backlog (rate limits fought back)

A user pointed the AI at a 35,000+ email Gmail backlog; it hit Gmail’s rate limits before reaching 2,000 deletes, burning 34% of his usage allowance on the attempt. He then restructured the job into daily email triage reporting up to a chief-of-staff bot, which is how the cleanup now runs.

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.