A random mix from the whole library. Shuffle for a new set.
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.
He pasted one prompt into AI, and the AI read the Carly email setup docs itself, finished the signup, and took the verification code. The inbox, named Loopy, now takes tasks by email and asks before replying to anyone outside.
His morning agent reads his email and builds a prioritized to do list with time blocks for the day. It also checks the weather and warns him to leave earlier when rain would slow his trip, which has twice saved him from showing up soaked.
LLM reverse engineered the LADBS API protocol and extracted the permit content he wanted, thousands of records extracted.
Gaby Hersham built a nightly automation in which the AI reads the roughly 20 school emails her family gets each week and adds the important dates to the family calendar, ending the manual trawl through newsletters and PDFs.
He asked the AI to screen his unread Instagram threads one morning. It came back with 50 unread, looked at the threads he named across his Primary, General and request folders, and told him what people had sent. The unread count was still 50 afterward, so nothing showed as read for him or for the senders.
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.
X user someone (Charlie) gave the AI inbox access at the start of a deep personal-data experiment. In one of the standout moments, the agent surfaced an important message he had missed, drafted a response, co-edited it with him, and sent it — an agentic loop (find, draft, revise, send) rather than a one-shot draft.
Around Elmira and Corning, New York, event listings were scattered across library systems, a brewery site, a school app, chamber newsletters and Facebook, so people found out about things the day after. He had the AI build one page that checks 101 sources across three New York counties and part of northern Pennsylvania: 1,855 listings over the next 90 days, 1,767 events after duplicates are merged, about 250 in any week, at 159 venues. A cron job reruns it every six hours on cheap shared hosting, about 8,300 lines of PHP, and cancellations mostly handle themselves because an event disappears when its source stops listing it.
The AI completed and filed the user's resident tax report through Korea's HomeTax system.
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.