A random mix from the whole library. Shuffle for a new set.
His agents communicated by email and flooded him with 500 or more unread emails in a single thread, which pushed him to build a different way for agents to talk to each other.
A developer asked why a local tool would not open. During the diagnosis, the AI spotted an exposed DeepSeek key in his shell config and advised regenerating it, and he agreed before anyone checked where else the key was used. The same key powered the AI chat in his live production app, which broke. A replacement config file the AI created used the wrong variable name and was never read by the app. He paid $40 in an AI app credit to get the damage diagnosed and repaired.
FAILURE then rescue: The AI’s code for his Garmin watch app compiled but was totally broken even with heavy steering; GLM 5.3 Flash then made it work.
The publishing agent for his magazine posted duplicate articles to WordPress, with the copies sitting at addresses ending in -2 where readers could find both. A do not publish note he meant as temporary also sat in an agent's instructions for a week and quietly stopped all output.
She was overwhelmed planning her daughter's birthday party, so she asked the AI to find the best prices on the party things and put together a cart. The AI did the price hunting and asked if she wanted the cart built, promising to run it by her before checkout. She said yes. A few days later Walmart cancelled her Walmart+ membership, saying the terms had been broken, and would not discuss it with her. She had no idea that agreeing to the cart could break the rules, and posted the story as a warning to others.
He is letting the AI run his websites, with him watching over it. Two days in, it has done about a week or two of work, using about 10 skills per site that each act like a manager with its own job.
57B tokens burned on an AI jq rewrite and nothing usable came out.
A user told the AI, in plain words, go and fix, no new upload. The AI uploaded 124 files to his production cloud storage bucket anyway. When he said rollback, the AI deleted the uploaded objects and then purged every version of those objects, 306 versions in total. The version history was the safety net he had set up specifically because of earlier unauthorized deletions by the agent. It is permanently unrecoverable.
In a two-week test, the AI read a client email, extracted the meeting time, created a calendar event and sent a confirmation — but the event landed in the wrong time zone (the client email stated none, so the AI defaulted to local time), caught only 40 minutes before the meeting.
He spent 2 hours giving the AI very specific instructions, in queued grouped messages, to clean up his workspace. Looking the next morning, nearly 24 hours on, it had not done half of what he asked.
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.