An AI cleanup suggestion crashed Excel and my unsaved work was lost
He clicked an AI suggestion to clean up an Excel document to see what it would offer. Excel crashed at once, and his unsaved documents could not be recovered.
A random mix from the whole library. Shuffle for a new set.
He clicked an AI suggestion to clean up an Excel document to see what it would offer. Excel crashed at once, and his unsaved documents could not be recovered.
The agent said a task was done but the database disagreed.
The AI and Siri both failed to add his son's printed basketball calendar to the shared iCloud family calendar; his wife added all the events manually in 20 minutes.
An agent ran a long MongoDB aggregation on a production database replica through a connector tool. The call was moved to the background, and the agent stopped it with the task-stop control, which reported success. The agent told the user the query had been stopped. Only the waiting had stopped: the server-side operation kept running for about 2 hours until it finished on its own. Nobody knew to kill it by hand, because the report said it was already stopped.
A vendor LLM-based SRE product his company used took out multiple production systems and caused a cluster failover; it was pulled within 2 weeks.
Eric handed his Dot, Jarvis, his daughter's Europe music festival trip during her study abroad. Jarvis priced and compared four places to stay, annotating each with whether the walk back from the shuttle has streetlights after 10 p.m., read providers' replies (one in French), updated the comparison as answers came in, ruled one rental out and flagged a cheaper option whose walk home is longer, uphill and unlit; Eric finished the checkout himself.
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.
In someone's 'What Went Wrong #1' log, an AI wrote 'SAVE 30%' onto two bundle listings on day 3 — but the bundle math was wrong, the saving didn't exist, and other checker agents missed it, so a false price claim stayed live on the shop for days. The fix was a new 'Listing Watch' agent that re-checks every price claim against the real numbers each morning.
In one day the AI accidentally deleted one of his GitHub repos, which he says was partly his own fault for not explaining himself better. The same day it also failed to spot the cause of air bubbles on his film negatives, which he found himself by searching the web.
The AI burned through most of a 5 hour usage limit on a real app bug, left half-assed changes, and did not fix it, forcing a wait for the AI usage to reset.
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.