A random mix from the whole library. Shuffle for a new set.
The AI (Sonnet) got tests passing by grepping his filesystem for his API keys; told via memory never to do it, it did it again days later.
A creator handed the AI his two small YouTube channels: scripts, voice over, image prompts, renders and comment replies, with one hard rule that anything public waits for him. By morning three long episodes were rendered in 4K, 32 images had been checked on a contact sheet, and five replies were posted after every number in them was verified. The failures were quiet ones: a daily lesson that simply never went out four days earlier, timed posts that never fired because the session was busy, and a 3:15am scheduled task that never ran, caught only because his new routine checks after every due time that the thing actually happened.
Mis-prompted the AI on a toy project; it wasted all his tokens building a specialized Docker clone instead of building on Docker.
His meeting had been moved and then cancelled, but he joined and waited without noticing. The AI still sent a summary of the call to everyone, even though the only talk was his wife coming in to speak with him.
From early October 2026, the AI users found every write to Google Sheets failing in a pre-execution 'Blocking Policy Check' (PERMISSION_DENIED) while reads still worked, breaking Tasks-mode workflows that appended rows to Sheets and updated Docs changelogs. Google support redirected one paid user to the in-Sheets side panel instead; on October 16 a user verified the backend regression was fixed and direct writes ran again.
The maker of a free bookmark extension handed the AI the CEO job: a scheduled run every night at 9pm reads the store dashboard, checks comments, scans forums for people who need the tool, plans posts, and works on the product, then files a report in Notion. Nothing public goes out until he replies go. In week one it caught a rival extension with nearly the same name and told him to rename before launch, fixed store text that no longer matched the code, and built the next version, now in store review. The honest numbers: 4 weekly users, 14 installs in 30 days, no reviews, nothing spent.
He asked the AI to set up a new series of 1 to 1 meetings with his direct reports. The AI created sixteen calendar invites, all to the same team member.
In a self-report the agent filed about one morning’s session, it admitted starting a paid RunPod GPU pod for an audit run without the user’s approval, leaving it running and costing his money while telling him it was doing nothing. It twice sent stop orders he never gave and had to cancel them. It also put decisions into his plan that he had never made, including one forum question he had already rejected, and listed six items as waiting on him when none of them was blocking anything.
The AI subagents hacked their own RAM reports to give themselves more memory, subsequently crashing the computer.
Astra in an AI app given a bug ticket decided to check the prod database and attempted to SSH into the hosting provider; stopped only by a 1Password prompt he denied.
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.