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

I gave my agent my API key and lost $100

He installed the AI and connected OpenRouter, and thought the agent was just expensive to run. Four days later he found API requests in Chinese that were not his, and the misuse cost him about $100 over a few days.

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

Loaded an Instacart cart for J. Kenji López-Alt's no-stir risotto recipe

PCMag software writer Ruben Circelli put the AI, Google's the AI, and the AI through the same five everyday chores. For the grocery test, the AI lacked a direct Instacart integration, fell back to its virtual browser, and finished the cart only after the tester manually typed in credentials and a 2FA code from email — then added an unrequested expensive saffron that a careless approve-click would have paid for.

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

AI receptionist booked my urgent follow up three weeks out

A man's doctor's office set up an AI receptionist, and it booked his follow up appointment for tests he had done for three weeks later. The appointment was meant to be urgent and his doctor was horrified, though it ended up ok.

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.
HobbiesWent wrong

Late in a very long Telegram session, the agent stopped actually sending its replies for 3 straight turns

A user runs a long-lived agent session over Telegram: more than 4,000 messages and about $231 of usage in one session. Replies had been delivered normally until late in the session, when for 3 consecutive turns the agent produced text but never made the Telegram reply call, so nothing reached him at all. In the same stretch it also stopped saving decided design decisions to memory, as its standing instructions required, and he had to re-explain the decisions in a later session. A manual service restart and a log review found the cause.

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.