A random mix from the whole library. Shuffle for a new set.
A father set up the AI with access to his credential vault so it can log into his child’s school information system and the other school sites, pull together the homework and due dates, add them to the child’s calendar, and add a reminder the day before with a link. He modelled the workflow out formally and set it running daily.
A freelance engineer let the AI run his side business blog and X account on its own for 90 days. The blog made ¥31 a month while his costs were ¥9,110 a month, and he writes that the hard parts were what did not work, including runs that had stopped without him noticing.
The AI given desktop and email access failed to clean up his desktop, said it could not press buttons or drag files to the recycle bin and suggested he do it himself.
On his boss’s suggestion he tried AI to compare two documents. It failed badly, and about 15 minutes later he was back at square one.
A pipe burst in his house two months ago. He now has the AI run his side of the claim. It reads the policy, files his living expense receipt scans, watches messages from the insurer, calls out delays, fights coverage decisions, and keeps logs of letters, estimates and invoices.
He clicked an AI suggestion to clean up an Excel document to see what it would offer. Excel crashed at once, and his unsaved documents could not be recovered.
He is building a training plan for a half marathon in November and a year long training calendar that builds up to the Moose Mountain 50km in August 2027. He also set up a scheduled task in an AI app that sends him a coaching email every Sunday evening.
437 the AI subagents ran adversarial reviews in yolo mode with repeated duplicate checks, forcing him to build his own spending and observability rules.
A developer let the AI write specs and code while the AI reviewed, all run through GitHub Actions and controlled from Telegram. Between September 21 and October 5 it merged 67 agent pull requests, but keeping the automation alive took 54 changes and 129 maintenance pull requests, and it burned through 3,000 monthly Actions minutes in about three and a half days without him noticing for two days. He went back to running the agents locally with himself making the final calls.
A vendor LLM-based SRE product his company used took out multiple production systems and caused a cluster failover; it was pulled within 2 weeks.
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.