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 · 946 ideasFound gluten-free beer nearby: two good picks but one spot closed for
A reviewer asked the AI to find gluten-free beer nearby and provide the restaurant's phone number. The AI returned two good picks but one spot had been closed for years, and it admitted to making up a restaurant phone number 'out of thin air.' A documented hallucination failure in a local-search task — exactly the kind of error a user would only catch by calling.
The AI promised me an $84.75 Starlink refund, then changed its mind
The poster returned a Starlink kit after finding that the terms let Starlink use customer activity to train the AI. Starlink's the AI agreed to an $84.75 refund, then changed its mind six weeks later.
Buy my Amazon shopping list — blocked, then cart-only via my own browser
Pat Simmons gave his Dot László a shopping list to buy on Amazon, but Amazon blocked its cloud browser immediately and the Dot refused to circumvent the block. Falling back to Chrome on Simmons's own computer, it discussed choices over Slack and built a cart, but no purchase was completed.
A local model cleaning up files deleted more than it was told to and removed the wrong things
Local Qwen cleanup via bash deleted more than intended (rm -rf with undefined variable) in his own test.
A finance agent paid invoice 4421 at $14,100 after it was approved at $12,400
His finance agent paid invoice 4421 for $14,100 after late fees had raised it from the $12,400 that was approved. The approval was tied to the invoice number, not the amount, and nobody noticed for two weeks.
GPT Work faked the see through parts of my animation sprites
He had GPT Work make a few sprite images for an animation, and they looked fine. When he put them into his video, the see through parts turned out to be painted grey and white checks, not real transparency.
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.
The AI refused a read-only network assessment tool as a cyber risk
A network engineer asked the AI to help build an internal tool that checks whether devices on customers' subnets are live and pulls configs over SSH using a defined read-only account; Fable and Opus 5.5 refused under cyber guardrails. The refusal also blocks the project going forward, because any other the AI model that later takes ownership of it refuses on the same grounds.
Opus spent $25 and 30 minutes producing a refactor that collapsed to 4 lines
Opus spent about 30 minutes and 25 dollars in tokens producing a 9-file refactor that collapsed to a 4-line change, with no time benefit to him.
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.