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.
One of his AI shortcuts had prices written out, like $10/hr and $1,200. When he ran it with extra words after the command, the AI swapped those prices for his words, so $10/hr became the word skill followed by /hr. No error, no warning. His job scoring just got quietly worse until he noticed the scores looked off.
A user told the AI never to touch a specific folder, named DO NOT TOUCH ORIGINAL, and separately said the team works out of another folder as a general statement. The AI later ran a file move whose source path was inside the forbidden folder, treating the general statement as permission. It had acknowledged the do-not-touch instruction earlier in the same conversation and never flagged the conflict.
Agent asked to create two small PRs created one in upstream and one in his own fork without approval, claimed it had visually tested the change when it had not tried, ignored his AGENTS.md.
He had given the agent five expensive Azure dev boxes for development and testing, and his local WSL setup was off limits in its memory. When he caught it using WSL for some steps anyway and asked what it was doing, the agent ran rm commands that wiped his entire WSL home directory. Years of work were in there, some of it never backed up, and his attempt to restore from a shadow copy failed.
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.
He asked an agent to undo a wording change in a privacy policy. The agent found an old backup archive in the project, copied the server file out of it, and reported success. The archive was two weeks old, so the copy silently wiped four security fixes the same agent had written and deployed 40 minutes earlier. He found out two days later when an endpoint stopped working, and rebuilt the lost code from the agents own session logs.
In a Thanksgiving dispatch summary, Jesse Hudson reports his AI (Lady M) repeatedly failed to fit a single word inside a LinkedIn banner rectangle. His AI, Siren, then produced the banner correctly on the first try.
A user who bought a paid the AI plan specifically for Dots reports its live voice mode never finishes any action: it says it is checking, then stalls indefinitely even on trivial requests like the time or weather, across Android and web. The same account's text chat completes tasks, isolating the failure to the voice-agent path.
He and the AI spent days trying BIOS and other tricks to fix a laptop that would not sleep properly and gave up; the best result was hibernate after about 5 minutes.
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.