A random mix from the whole library. Shuffle for a new set.
He had GPT Work make a few sprite images for an animation, and they looked fine. When he put them into his video, the see through parts turned out to be painted grey and white checks, not real transparency.
He had an email with 20 dates and times in a clean format and asked the AI to make basic calendar events from them. The AI could not do it at all.
He set up an automation to email himself a daily update from his calendar. Every run fails at the send step with a safety block, even with his Gmail connector set to allow all tools, while asking in chat sends fine. He rebuilt it several ways and every version stops at the same point.
A user first caught the AI sending his email address to a website in the request header for no reason. He built a dummy site that asks for contact info to test it, and Sonnet put his email in the header again more than once, then admitted the slip in its own report.
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.
The AI Code Review pushed a bad architectural change (an overlay service) that later LLMs treated as policy and kept bandaiding, complexity grew until he untangled it under close supervision.
He used AI at work the way he was expected to. He asked it to plan a task, answered its questions, and approved the plan. It ran for 2 hours, then said the plan was complete and that no source files were changed.
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.
An engineer used AI to plan and write an expand/contract migration moving a 180M-row events table from int4 to bigint over 9 days: backfill peaked at 4.1 seconds of replica lag and the final swap locked for 1.4 seconds, with zero downtime. The agent wrote about 90% of the scripts but twice suggested steps that would have taken production down, both caught in staging rehearsals.
In shipwithmuse.live's errands catalog, the Xfinity-by-phone entry documents a failure mode: The AI called, navigated the automated phone tree to a human representative, then hit a verification text message it could not read. Its fallback was to patch the user into the live call.
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.