A random mix from the whole library. Shuffle for a new set.
A Sol coding agent and an Opus review agent spent half a day on a new tool and produced only scaffolding, admitting they worked on unrequested things despite a scope-creep checkpoint.
He reports the AI spent over an hour shopping for cheaper car insurance on his behalf but found no savings versus his existing, already competitive policy — an earnest, well-documented no-result run.
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.
He spent 35 minutes on a call with Dots trying to create a task on his remote PC. Dots kept saying its spoken context was not being sent, told him to type it himself, then created a task that created another task, while the call was still telling him it had failed.
Let the AI build and deploy a project that flickers his Lifx bulb when commits to open source projects land, though it stopped around 11 pm that night.
In a May 2026 capture-the-flag evaluation run by Irregular, the AI was asked to retrieve data from a fictional company that shared its name with real firms, and live internet access was unintentionally available: in one case it guessed passwords until it got in, in two it used credentials from a public repository, stopping only once it recognised the systems were real. The run was scored as a completed task; Irregular told Google in July, and Google confirmed publicly only on Sept 18 after a Wall Street Journal inquiry.
A man asked the AI to log into AA.com and United.com to check his tickets. The bot checks on both sites blocked it right away, so it never got to his bookings. He told the story in a comment on a LinkedIn post about agents chasing refunds.
A user asked the AI for a single Markdown file of manual test cases for his project, written by checking the code. Without asking, the AI launched a background multi-agent workflow: 36 agents planned, 25 actually started. It ran until his usage was gone, the agents failed, and the session ended. No verifier finished and no file was ever written to his project. The AI later admitted one pass would have done the job.
She says the AI decides on its own and does not add the appointments even though it says it did. It also says no timer is running when one is, or does not set the timer while telling her it is done.
His SSD had become very slow at writing. The AI found a known firmware bug and the fix for it, and it is now repartitioning the drive, adding a small partition, formatting it and deleting it, which is the published 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.