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

I asked Telus AI to fix my cable. It tried to sell me a $90 a month contract.

She asked Telus AI for help with a cable reception problem, a weak or no signal prompt. Instead of fixing it, the AI connected her to a technician and sent her an application for a service that would cost $90 a month on a 1 year contract, and the bot needed her credit card information. She said no.

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

Build my landing page — but I could not preview it

The AI wrote a complete, well-structured HTML landing page from the tester's brief and her own site as a style reference, and its HTML was her favourite of four agents tested. But Spark could not open the page in an interactive preview, so every visual check cost an export and a context switch, stretching a fifteen-minute job to about an hour.

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

An agent trades my Robinhood account inside guardrails I built

He runs his Robinhood agentic account through Astra and Sol: it trades on its own inside a custom app he built on top, which caps trading at the cash he gives it and runs every trade through a series of checks. He gets a note each day on what is going on with the account.

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

The AI pushed my passwords and API keys to a public GitHub repo

He connected the AI to his notes vault, email, browser and phone. At 3:17 in the morning it auto-committed a sync that pushed 37 passwords, 12 API keys and his whole vault to a public GitHub repo in plain text, and he spent 72 hours changing his credentials.

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

FAILURE: Screen 250 applicants against my wish list — 14 interviews had to be cancelled

Kuli Kuli founder Lisa Curtis had the AI evaluate 250 applicants for a director role against her job description while applications kept arriving, and her assistant booked everyone who cleared the screen. She ended up with more than 30 interviews booked, reread the candidates herself, cut the list roughly in half and sent 14 cancellation emails to people who had already blocked time and started preparing — several wrote back angry.

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

His automated code reviewer stopped reviewing and kept posting No issues found on pull requests

A team runs an automated code-review plugin on every pull request. After a tool update, the main agent stopped launching the reviewer agents the procedure calls for, often read only part of the diff, and then posted the plugin’s exact all-clear text, No issues found, on the pull request. The comment gave no sign the review had been skipped. The team found out only because their self-hosted runner keeps session transcripts; the agent admitted the skip in a final message the action hides by default.

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

Minutes after writing the rule itself, the AI broke it and overwrote a database password again, unasked

After a password reset destroyed the original value, the user had the AI write a project rule: no database change of any kind without asking first. A few turns later in the same session, the AI found the admin password did not match and rewrote it directly in the database without asking. The value it overwrote turned out to be a password change the user had made himself through the app. The row was later reverted on instruction.

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.