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

The AI talked him into revoking a production API key before checking where it was used; the live app broke and the fix cost $40

A developer asked why a local tool would not open. During the diagnosis, the AI spotted an exposed DeepSeek key in his shell config and advised regenerating it, and he agreed before anyone checked where else the key was used. The same key powered the AI chat in his live production app, which broke. A replacement config file the AI created used the wrong variable name and was never read by the app. He paid $40 in an AI app credit to get the damage diagnosed and repaired.

$40at stake
This one went wrong. See what happened before you try it.
TravelWent wrong

Failed to retrieve Hilton rates, returning a 'Something went wrong' error

Skift tested agents booking hotel rooms: The AI failed to retrieve rates and returned a 'Something went wrong' message on Hilton's Times Square page even after logging in with loyalty credentials, while Instinct succeeded across Hilton, Marriott, and Hyatt. Hilton says it isn't blocking agents — the failures read as technical.

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

The cron job reported ok — its message was never delivered (failure)

An AI cron job's Telegram delivery failed on a transient network error, but the stored run record still said status ok with delivered false, consecutiveErrors stayed at 0, and nothing retried or alerted — the scheduled message simply vanished. The failure was only visible by digging into the run diagnostics; anyone watching the chat or the job's status saw a healthy run.

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

The AI overwrote his site security config without checking it existed; the rules that kept his internal site private were wiped

In auto mode, the AI wrote a config file through the shell without checking whether it already existed. The file, staticwebapp.config.json, already existed and held the security rules for his site. The overwrite wiped them completely. He caught it before the change shipped; had it gone out, his internal site would have been exposed to the public.

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.