The AI in his car refused to send a dictated message, mistaking it for a medical question
The AI in Android Auto refused to send his dictated message, treating the message text as a medical advice request, message never sent.
A random mix from the whole library. Shuffle for a new set.
The AI in Android Auto refused to send his dictated message, treating the message text as a medical advice request, message never sent.
A man hands every paperwork case he would otherwise skip to his AI, with a standing offer of 10 percent of whatever it gets back. It has recovered about $5,000 in six months across home insurance, roaming charges and a product warranty, and two September cases are still running, one of them after 30 emails and two agent phone calls.
He used the AI API to draft his articles automatically for a week. Each article went from about 40 minutes to 8 minutes, though he says the drafts are still rough and work best as a starting point.
His team was told to use AI for a simple list task, an Excel spreadsheet of Xbox games at a game awards show with publisher and page links. Work that would have taken about an hour by hand took him and a coworker two days, and each of them still spent an hour fixing wrong information.
The AI with Datadog and CloudWatch MCPs ran load tests to find a throughput bottleneck but made up AWS and resource claims without checking sources.
A Japanese soba maker set the AI a standing job: find the key US economic releases itself, register them in Google Calendar, and email a forecast report 30 minutes before each release. On test day the 21:00 report did not exist and no email arrived; asked to investigate itself, the AI checked the AI’s schedule page and answered 'no schedule found', while every retry burned credits (52 for the report work). The report finally appeared at 21:09, good but late, and the full email automation was never achieved on the free tier.
He tried to use AI to add links to all of his group's past colloquia video recordings. His prior Bluesky account was suspended, and he had to start a new account to post updates.
Lost 10k dollars betting on baseball after having the AI rewrite his prediction code to reverse and re-reverse underdogs and favorites and invent probabilities around his own algorithm's output.
The AI was working on a web app the student's friends use live. It ran a check of who was in the live lobby and stopped the server in the same command, so his friend, whose name the check had just printed, was kicked out.
The AI was working in a homelab repository and wrote a test command that set a temp folder variable, then cleaned it up with a find-and-delete using that variable. An earlier step in the chain failed, so the variable was never set. Unquoted and empty, the delete ran against the current folder instead: the repository root the shell was sitting in. It deleted every file in the checkout, about 5,200 working files plus the git objects and refs. Only files the sandbox mounted read-only survived.
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.