215 notifications a day became a triage bot of his own building
He gets 215 GitHub notifications a day, so he built a bot to triage them.
A random mix from the whole library. Shuffle for a new set.
He gets 215 GitHub notifications a day, so he built a bot to triage them.
Lixka, an accelerated nursing student at Mercy University, uploaded all six syllabi to her AI 'Mila'. Mila identified that Monday, September 28th was a 'triple-header' — two quizzes and a Pharm lab she hadn't noticed — then built a sustainable weekly rhythm around fixed classes, clinicals, and workouts, and asked permission before creating three tracked goals: quiz prep, reflection paper, and workouts/downtime.
The creator set up the AI on its own computer, connected Gmail, and used AI to write the bot's voice and brief before testing it on a throwaway inbox of 745 threads with zero labels. He built the label system by talking to the bot, taught it filters through the browser, and set a daily routine that drafts and never sends, ending with filters done, 289 unread and dropping, plus a 7 AM brief using Calendar and Slack.
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.
He had the AI collect his will and trust documents and check them against state statutes. The review found missing signatures, an illegal clause, and outdated law references, and he fired his attorney the same day.
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.
Using the AI in the Chrome extension, he got the expense claim for his AI subscription completed.
He helped his brother with the website of Ichtus Vlaanderen, an NGO he used to work for. Using the AI through the WordPress.com MCP connector, he fixed design problems like a messy photo section and buttons that were too big.
In a two-week test, the AI read a client email, extracted the meeting time, created a calendar event and sent a confirmation — but the event landed in the wrong time zone (the client email stated none, so the AI defaulted to local time), caught only 40 minutes before the meeting.
He is juggling several legal cases of his own, and his lawyers do not have time to answer him every day. The AI transcribes audio, organizes his evidence and writes the case summaries he hands to them. He calls it the best tool he has ever had, and says stopping would mean going back to doing all of that alone.
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.