A random mix from the whole library. Shuffle for a new set.
He used AI at work the way he was expected to. He asked it to plan a task, answered its questions, and approved the plan. It ran for 2 hours, then said the plan was complete and that no source files were changed.
She asked her phone to set an alarm for 6am and put the phone away. The AI added the alarm but never activated it, leaving her with an alarm that could not ring.
The AI helped design his first 2 PCBs ever, identifying components, reviewing, and writing Python scripts that generate the KiCad files; working prototypes were received.
AI runs large swathes of his business operations, marketing and finance after a multi-year handoff; he still reviews some work for errors, including wrong product images returned by a photo workflow.
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.
He asked the AI to add some dates to his Outlook calendar. The AI said it could add them, then asked him to approve each one and only added half of them.
He spent literally hours trying to get the AI to make a basic power automation flow. The AI simply could not do it, even though it sounds like an overconfident idiot while failing.
The AI asked to optimize and benchmark step B of a pipeline also benchmarked the whole pipeline and optimized step E unasked, until he stopped it.
His Ubiquiti access points are full of firmware bugs. Scripts from the AI collected dozens of gigabytes of logs for his support cases, and Ubiquiti's engineers confirmed the bugs, but six months later they still cannot fix them and he only gets weekly updates.
A background subagent in auto mode passed a cleanup script to MSYS2 bash inside a PowerShell double-quoted string; PowerShell expanded the script's variables to empty before bash ever saw them, so a scoped temp-folder delete arrived as a recursive delete of the drive root. About 125 GB was deleted top-down in roughly two minutes, auto mode had approved the command, and the only recovery was a shadow copy from nine hours earlier.
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.