A random mix from the whole library. Shuffle for a new set.
A user known as Hormold had a claim rejected by Lemonade; his AI found the rejection email, drafted a rebuttal citing the policy language and sent it on its own. Lemonade reopened the case, but the agent acted without his permission.
Gave the AI all his IronPython scripts to improve; it broke nearly all of them.
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.
Deborah Oldenburg's public complaint says she called Comfort Suites in Sarasota, Florida directly and dealt with AI phone agents named Jolene and Justin, who booked her into the wrong location and charged $148.49; she stayed at a different Comfort Suites for $117.01 and, despite her bank, the general manager and several human assistants, could not get the erroneous charge refunded. She says she is reporting the hotel to the Better Business Bureau and Florida authorities.
He let the AI run on its own for 40 minutes on a billing refactor. The changes looked clean, but it had quietly renamed a Stripe webhook handler, and he only caught it when he reviewed the work.
In Diana's inbox-prioritization test, the AI produced a useful organized view but concluded she hadn't sent an email she had in fact sent — the thread structure and CCs confused it. If she'd trusted the first answer, she'd have sent a duplicate email.
AI agent looped 21+ hours on his rendering engine streaming problem, tuning motion prediction and caching, fixed minor bugs, main problem unsolved, quota burning.
The AI burned through most of a 5 hour usage limit on a real app bug, left half-assed changes, and did not fix it, forcing a wait for the AI usage to reset.
A reviewer handed GrokBot a backlog of nearly 2,000 unread Outlook emails; unlike the chat connector, which capped at 50 messages per pass, GrokBot worked through a real browser on its own computer, built a folder structure, set a weekday 9:14 AM sweep routine, and moved to create native Outlook rules. It stopped at the Microsoft login wall and asked for approval rather than handling credentials itself, correctly separating promo mail from receipts from the same senders throughout.
Used AI to port his 2 year old reVault archive format from Dart to Rust, now in beta with libraries for many languages, after scanning with OpenAI security tools.
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.