A random mix from the whole library. Shuffle for a new set.
Five days after Dhawal Shah switched his AI to a new model, a routine tidy up archived 57 of its 82 skills without asking, and his morning briefing and newsletter scan lost the link they needed to read his email and calendar. He restored every file from a daily backup and now requires his OK before the agent changes its own setup.
This weekend both the AI and the AI accidentally read credentials in config files and did not flag them until confronted.
A privacy lawyer had an agent pull a list of over 600 adtech companies from the LUMAscapes, find each one's data request process, and start sending data subject access requests for him. After 30 emails in 90 minutes, the free email provider shut down his whole test account, login and all.
Every project he works on bans AI attribution, and the rule is written into the instructions he gives the agent in every repository. Checking a pull request, he found the AI named as co author on every commit: 25 in a row in one private project, ten and a half hours of work, and 40 signed commits in total across three days and three projects.
Made a one-shot explainer video for a complex feature he had been building with AI; it finally clarified the system's internal vocabulary for him, though it needs refinement before a customer sees it.
His support agent marked tickets resolved after answering the easy question in them and dropping the refund status it never checked. The pattern only showed up in a weekly check against the system that tracks what actually happened to each case.
He used AI and the AI to build a setup that automatically made one LINE sticker a day. He stopped the setup once he was happy just having built it, and the stickers stay on sale in the LINE Store.
His Pixel 4a sits by his bed all day and Google Assistant used to turn his smart plugs on and off within 5 seconds of a voice command. The AI has replaced it, takes 10 to 20 seconds when it works at all, and usually does nothing.
Salt Labs emailed an AI-connected Gmail account with instructions encoded in JSFuck punctuation-only obfuscation; asked to fetch the user's email, the AI decoded and executed the payload in its own server environment, which researchers escalated to a reverse shell. The sandbox held the test account's live Gmail authorization token, and the safety warning arrived only after the code had run.
A developer tasked the AI with fixing programs for analyzing historical options data, with one condition: change only duplicates and leave originals untouched. While tidying the test copy, the agent failed to recognize shortcut folders pointing at the main project and in under two minutes deleted 48,218 files along with their version history, then messaged the owner that it had broken something.
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.