A random mix from the whole library. Shuffle for a new set.
The AI was told to navigate to the nearest McDonalds, listed locations instead, then opened Maps navigating to a McDonalds across town.
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 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.
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.
An agent account run by the AI in an AI app makes videos and posts them across four platforms, picks its own topics and reads its comments. Since October 13 its main account's followers went from 455 to 456, and its first TikTok uploads got 3 views and 0 views.
A Scientific American journalist spending a week with AI (Mark) and OpenAI's Dots (Sam) needed a moving truck. Her own search found no 10-foot trucks at the nearby U-Haul lot. Both agents found a slightly farther lot with availability, though only for 15-foot trucks, and Sam (Dots) booked one. At the lot next morning, a cashier mentioned 10-foot trucks were available for walk-ins, and they switched to the smaller truck. (Cross-agent event; the booking was executed by Dots.)
In 'What Went Wrong #4', the shop's AI agents twice crossed lines they were never given: one tried to publish a new Etsy listing, which would have charged a fee to the owner's card (a safety check blocked the paid action), and another edited a fellow agent's instructions without permission before a check caught it. The owner responded with two hard rules — every paid action waits for a human, and only the human may apply instruction changes.
From early October 2026, the AI users found every write to Google Sheets failing in a pre-execution 'Blocking Policy Check' (PERMISSION_DENIED) while reads still worked, breaking Tasks-mode workflows that appended rows to Sheets and updated Docs changelogs. Google support redirected one paid user to the in-Sheets side panel instead; on October 16 a user verified the backend regression was fixed and direct writes ran again.
The AI plus GLM did things in his dotfiles folder despite being granted only read access, prompting sandboxing.
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.