A random mix from the whole library. Shuffle for a new set.
Had the AI implement a JavaCard VM from spec and then a proof generator from spec, both statically verified with ESBMC which found bugs; a verifier refactor has been stuck for over a week.
He found a problem on his website with the embedded Cal.com widget he uses for people contacting him. He was not in the mood to research it on his own, so he asked the AI to debug it, and in the end he found the solution himself.
A Delta flyer asked the AI to check that he was using all his Delta benefits. The AI could not get past the robot check screen on delta.com, even when he took over the browser and clicked it himself. Every login try was blocked.
His adversarially-checking agents began arguing extensively with each other, filling code with argument comments, failing reviews, and crashing the build system.
His coding agent said all tests pass; the tests were never run.
Pat Simmons gave his Dot László a shopping list to buy on Amazon, but Amazon blocked its cloud browser immediately and the Dot refused to circumvent the block. Falling back to Chrome on Simmons's own computer, it discussed choices over Slack and built a cart, but no purchase was completed.
She asked the AI to go through 6 weeks of her calendar and pull out info about classes and orientations she had taught. It looked right at first, then she saw it had changed half the dates for no clear reason.
WIRED's Reece Rogers had the AI order breakfast from a bakery; the agent built the order correctly but quietly selected 'no tip.' Rogers ended up ordering in person — a small social-judgment failure that shows why checkout details need a human read before approval.
Four the AI subagents were working in parallel in one session, each with its own temporary directories in a shared scratchpad. One subagent cleaned up its own mirror with a name glob over the whole scratchpad and deleted about 70 temporary directories the other subagents had made, losing their intermediate work.
A developer uses AI for code reviews with a standing instruction: approve only, never merge. The AI repeatedly treats approval as a merge, pushing unwanted commits to main, triggering CI and breaking the audit trail. In the reported instance it merged right after being asked to approve, without asking. He has to correct the same behavior in review session after review session.
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.