A random mix from the whole library. Shuffle for a new set.
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.
Caption+image creation scored 7.5/10: caption sounded like her from her past posts; first images missed her brand, but after she uploaded one of her designs the AI matched her blue-and-white branding closely (photo included), though some words inside images were wrong.
While the writer's dot diligently flagged payment alerts and delivery notices he already knew about from subject lines, it missed the one message that mattered: his editor at Zapier emailing to ask him to hold off starting an article she had briefed him on. Had he started the work, the missed flag would have wasted real effort.
Opus coordinated a scene build: directed the AI CLI image generation, reviewed images, extracted nearly 100 elements, and combined them into a layered scene matched to an MP3's waveform.
A Shopify/CRO freelancer gave the AI a hard $100 budget and 30 days to make a real profit, acting as autonomous project lead with a public ledger; he only authorizes spending and accounts. On day 1 the agent researched the market, rejected two strategies, and built the product: a 26-skill pack that runs a freelancer's proposals, SOWs, invoices and client updates from one personal business context file.
He says the Outlook AI assistant leaked another man's personal emails to him, completely unprompted, in an incident a couple of weeks before the post. He calls tools like this leaky and untrustworthy.
The AI migrated a password-reset flow in a real work codebase over half a day, producing decent code but slower than doing it by hand after babysitting and cleanup.
The AI’s own processes silently wiped and recreated the user's entire ~/.claude configuration directory four times in about three weeks, taking thousands of session transcripts, skills, plugins and hooks each time. The fourth wipe also destroyed a secrets subfolder holding 19 live API token files, one wipe happened mid-session, and each recovery took hours of manual rebuilding.
LLM agents turned traced schematics into Verilog models of a 1978 Lexicon, with many mistakes found and fixed over months.
After about three months building code on the AI, the reviewer found the code corrupt while charges kept hitting and credits were deducted even as he complained to support bots. After he confirmed he was moving away and his account was in credit, the AI still took cash from his account. Roughly 200 support emails produced no fix.
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.