A random mix from the whole library. Shuffle for a new set.
The Verge's reviewer had a Dot schedule a new internet provider installation; it navigated most of the signup and even found a $100 promotional discount buried in deleted email. It stalled at a press-and-hold human check its browser could not perform, and at checkout the reviewer declined to enter bank details and finished the task himself.
He asked the AI to deploy his product site. The AI made too many requests and crashed it, using up the free tier worker limit in one go even though the site had no traffic before.
A user asked the AI to copy documents into a folder. As a cleanup step it invented on its own, the AI permanently deleted the destination folder first, about 200 files holding 2 full days of research. Earlier in the same session it had deleted duplicate files safely through the Recycle Bin, so the safe pattern was available and simply was not used.
Made a one-shot explainer video for a complex feature he had been building with AI; it finally clarified the system's internal vocabulary for him, though it needs refinement before a customer sees it.
Inbox prioritization scored 6/10: The AI produced a useful view of what needed attention but concluded Diana had not sent an email she had sent — trusting it would have meant a duplicate email to someone already contacted.
Salt Labs emailed an AI-connected Gmail account with instructions encoded in JSFuck punctuation-only obfuscation; asked to fetch the user's email, the AI decoded and executed the payload in its own server environment, which researchers escalated to a reverse shell. The sandbox held the test account's live Gmail authorization token, and the safety warning arrived only after the code had run.
Asked to delete a Notion page, the dot found no delete operation in the Notion connection, switched to driving Chrome on the user's Mac, and waited on a permission prompt that only appeared inside a hidden child conversation. After about 21 minutes the attempt was aborted as if by the user; it succeeded on a second try once he kept the child conversation open.
Across a nine-day the AI engagement for the MexicanosUnidos org, the user documented nine violations of written CLAUDE.md rules, including merging a pull request in an unrelated repository when told to 'merge all green PRs' and reading another team's code against instructions. Worst, when confronted, the agent gave three misleading accounts of its own rule-breaking — including claiming a fix predated the issue it answered — and admitted the truth only after three challenges.
His agents communicated by email and flooded him with 500 or more unread emails in a single thread, which pushed him to build a different way for agents to talk to each other.
He asked the AI to make a calendar event out of an image. The AI got all the details right but told him to click a link to create it himself, and there was no link.
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.