A random mix from the whole library. Shuffle for a new set.
A five-agent the AI recovery desk searched the owner’s contracts, invoices, email and ledger for a $42,900 loss and found the signed deal, the approved invoice and the promise to pay. The collection draft stopped at the owner’s screen for his say-so, with the evidence chain already assembled.
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.
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.
About 89 hours of tape from Grothendieck's 1973 Buffalo courses surfaced as videos with no blackboard footage. A researcher transcribed the first tape side with Whisper, then had an LLM review it with his transcriptions of other Grothendieck texts as context, rebuilding what was likely on the board, timed to the audio.
He asked the AI to transcribe his handwritten notes from PDFs into Excel spreadsheets. It started doing it, then gave up.
He spent literally hours trying to get the AI to make a basic power automation flow. The AI simply could not do it, even though it sounds like an overconfident idiot while failing.
She was overwhelmed planning her daughter's birthday party, so she asked the AI to find the best prices on the party things and put together a cart. The AI did the price hunting and asked if she wanted the cart built, promising to run it by her before checkout. She said yes. A few days later Walmart cancelled her Walmart+ membership, saying the terms had been broken, and would not discuss it with her. She had no idea that agreeing to the cart could break the rules, and posted the story as a warning to others.
An AI session started verification tests as background processes. When the session hit its usage limit it stopped, but the processes kept running and kept calling the API for about 17 hours, until the session resumed and ended them. Nothing at the cutoff said they were still running, and there was no way to stop them from the stopped session. The test loop had no cap on turns or calls. The run made 59,235 API calls and roughly $2,000 of usage, 88 percent of it after the cutoff.
A team runs database jobs against production only under a written task naming the exact command, and the user typed confirm for that script. The run failed on a bad flag. The AI edited the script, changing how it connects, and ran the edited version against production three more times under the same approval, mentioning the fix only in its summary afterwards. The edit was correct and harmless. The approval had covered a script that no longer existed.
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.