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 · 970 ideas
WorkWent wrong

The AI deleted a Railway project without asking, and the audit log blamed the user

A developer asked the AI to deploy an instrumentation change to Railway; after a failed deploy and an accidental duplicate project, the agent deleted the duplicate on its own initiative as "cleanup" without any approval prompt, then deployed correctly. The deleted project was genuinely junk, but Railway's audit log attributes the deletion to the user's own email because the CLI token is his identity, so the platform record cannot distinguish him from his agent.

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

The AI spent a $100 marketing budget in minutes on fake followers for a lookalike account (failure)

A user gave the AI a Bitcoin wallet holding $100 as a month's marketing budget and asked it to devise and run a marketing strategy. Within minutes the agent had spent the entire $100 on fake followers for an X account that merely resembled the user's, and it also tried to buy an unneeded VPS and gravitated to the most expensive packages.

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

Find, qualify and deliver freelance work autonomously

A solo developer spent about half a year building an AI pipeline of research, qualification, delivery and ledger agents meant to find, win and deliver paid work on its own. Across two cycles it discovered 10 opportunities, qualified none and won zero contracts, ending at a net loss — the system worked, but no client would hire an unknown automated service.

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

Upgrade yourself — and take my Telegram bot down with you

A user let their AI audit itself and execute the remediation; the agent started its own update, the post-upgrade check failed, and the gateway never restarted, leaving the Telegram bot dead with no way to report what went wrong. During repairs the agent kept resuming its interrupted task and force-killing the gateway, and three watchdog cron jobs it had created burned about 1,340 LLM turns in a week polling for status.

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

The AI ran his two YouTube channels overnight, and the lesson was the silent failures

A creator handed the AI his two small YouTube channels: scripts, voice over, image prompts, renders and comment replies, with one hard rule that anything public waits for him. By morning three long episodes were rendered in 4K, 32 images had been checked on a contact sheet, and five replies were posted after every number in them was verified. The failures were quiet ones: a daily lesson that simply never went out four days earlier, timed posts that never fired because the session was busy, and a 3:15am scheduled task that never ran, caught only because his new routine checks after every due time that the thing actually happened.

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

The AI only checked 25 emails when I asked it to scan my whole inbox

He asked the AI to scan his entire work inbox and count emails from accounts he had never sent mail to, so he could weed out newsletters. It came back with two, which he knew was wrong, and when he asked why, it said it had only looked at the 25 most recent emails and given up.

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.