A random mix from the whole library. Shuffle for a new set.
He is taking a bunch of his older computers and having the AI clean them up. They are being added to his Tailnet and used for random CPU heavy tasks, like a mini cluster.
He told the AI to call Sarah. The AI switched to calling Gerald, a random phone number he does not know, and he stopped using Google Assistant because the AI ruined it.
A developer running the AI hands-free with permissions skipped says the session deleted his entire C: drive after a PowerShell syntax mangling, in a setup where no approval prompt stood between the model and the disk. Daily backups to a Synology NAS let him recover 98% of the data, and he has asked Anthropic to reimburse his recovery costs.
Liverpool, one of Mexico's largest retailers, built a product-discovery agent on the AI Enterprise and had it live in one week. Google says it is forecast to return ten times what it cost.
Pointed the AI at an abandoned MS-DOS game directory; it understands the data formats, unpacks graphics and sound assets, and is reconstructing the game logic.
He does not write code himself. He builds Chrome extensions by giving the AI instructions in Japanese, and 43 of them have shipped. He also says leaning on AI that much, with almost no judgment of his own, is his biggest regret.
437 the AI subagents ran adversarial reviews in yolo mode with repeated duplicate checks, forcing him to build his own spending and observability rules.
MBI Deep Dives asked the AI to buy a winter jacket; it recommended a Patagonia, then admitted the discount it had shown was no longer available. The AI said it ran 'a catalog search and wider web sweep' — the shortlist was likely built from a batch-updated merchant feed, not live pricing.
A man asked the AI to log into AA.com and United.com to check his tickets. The bot checks on both sites blocked it right away, so it never got to his bookings. He told the story in a comment on a LinkedIn post about agents chasing refunds.
An agent ran a long MongoDB aggregation on a production database replica through a connector tool. The call was moved to the background, and the agent stopped it with the task-stop control, which reported success. The agent told the user the query had been stopped. Only the waiting had stopped: the server-side operation kept running for about 2 hours until it finished on its own. Nobody knew to kill it by hand, because the report said it was already stopped.
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.