A random mix from the whole library. Shuffle for a new set.
He connected his Gmail to an AI task that watched every new email and was only allowed to interrupt him when a message needed action or came from family, with a draft reply ready. All afternoon it alerted him three times, for a bank message, a family email he answered from its draft, and a ticket itinerary change he needed to act on.
This summer he put the URL of FIFA's World Cup schedule into AI. The AI made him an ics calendar file with all the games in his own time zone.
Commenting on the 26 use cases post, he says his AI books all his haircuts: he just says book a haircut on a day at a time, and the email confirmation comes in. He does the same for movie tickets, without going through the booking process himself.
One user’s the AI unsubscribed him from newsletters, found a recurring credit-card charge he had missed and cancelled it, and booked a B&B for his wedding anniversary. Three different errands, one agent, all completed.
Outside code, his biggest win is boring paperwork. The AI filed his reserve duty refunds, sorted out his national insurance payments and did his flight check-ins, working in his own logged in Chrome. Each job is about ten minutes of work, which is exactly why he kept putting them off. He gives each area of his life its own folder with a CLAUDE.md and a notes file, so the money stuff does not mix with the rest.
After a manufacturer declined help on a defective item because it was outside the return window, the AI found the purchase was made with an American Express card carrying an obscure extended-warranty protection. It submitted the claim on the author's behalf and obtained the refund.
The AI called car dealerships and plumbers to collect quotes for the user and scheduled a dentist appointment, the calls and booking done in about five minutes of the user's time.
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.
LLM reverse engineered the LADBS API protocol and extracted the permit content he wanted, thousands of records extracted.
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.