I updated a client's email triage so it forwards mail to her customers
He updated an old email triage workflow for a client this weekend. Jev now runs alongside GPT-4o mini, which still controls which emails get forwarded to her customers.
A random mix from the whole library. Shuffle for a new set.
He updated an old email triage workflow for a client this weekend. Jev now runs alongside GPT-4o mini, which still controls which emails get forwarded to her customers.
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.
Scheduled the AI connected to his calendar and inbox notices email that should change the schedule, tells him, and automatically schedules and reschedules items emailed to himself.
Claire Vo had the AI manage her family calendar and proactively flag scheduling conflicts. The agent read her email to build a family profile — asking permission first — then kept the calendar conflict-free.
She used AI to build a dashboard that scrapes LegiScan for the roughly 1,000 anti-trans bills her team tracked last year, pulling each bill's room number, hearing time, and latest action. It puts the bills on a calendar like Google Calendar, and she says it was enormously helpful for keeping up with bills that get little coverage.
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.
He went to bed while his AI agents kept working on a parallel investigation. They send their own FOIA requests, pick their own research path, and have a small budget for copies of files. He set the web permissions for the night before letting them loose.
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.
Jack created a recurring daily website-check goal by chat in about a minute, then deleted it by chat. The Goals tab itself was slow to load (once 25 seconds, once stuck on placeholders).
He runs AI on his homelab. He can ask the AI to throw an event on his calendar and it appears, and the setup can also send events to his primary calendar by email.
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.