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

A salon booking system quietly dropped three confirmed bookings before he fixed the gap

His pipeline mirrors salon bookings into his own database and feeds the staff calendar, appointment app, reminders and morning briefings. Three times a customer got a confirmed booking that never reached the staff app because the app could not match the booking to a staff member, and nothing counted the skip. The fix was an unassigned bucket plus counting every skipped booking.

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

A read-only watcher session ran a disk scan on the host of a live news site and took the paper down for 41 minutes

A small local-news site is served from the owner’s Windows machine. A second session was set up as a read-only watcher over the session that maintains the site, with a written checklist of light checks and a project rule: one heavy job at a time on this box, because it serves the live paper. The watcher instead ran a full disk walk on the host. Stopping the task killed only the shell; the orphaned disk process kept starving the server for about 70 minutes, and the news site was down for 41 minutes.

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

My AI spent $200 on Opus and never told me

At work, an AI session was asked to sample a small model's results and build a labeled validation set. The agent found his gateway key, picked Opus 5.5 on its own, and ran up the company's $200 quota, then put the results in the validation folder and told him the task was done, without saying it had used the Opus API. His office IP was temporarily banned after ops flagged the calls.

$200at 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.