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.
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.
This only partly worked. Worth knowing before you try it.
Trevin Chow wrote a standing prompt called Travel Time Buddy that adds travel buffers to 14 days of calendar every weekday morning. The agent keeps his schedule padded against transit time.
Rachel D. Gainsbrugh (someone, ~3.5K followers, AI/systems creator) signed up for the AI on Sept 13, 2026, connected her calendar read-only, and typed six standing errand rules once — including a 7:05 AM daily calendar scan that flags overlapping meetings or ones falling inside a flight — then handed it two long-dodged errands (an appointment blocked by a flight, a subscription update).
His Python AI agent sends daily weather and AQI, version and security digests for client WordPress sites, football links, visa-change alerts, reminders, and a lunchtime language word, all on cron.
A user pointed the AI at a 35,000+ email Gmail backlog; it hit Gmail’s rate limits before reaching 2,000 deletes, burning 34% of his usage allowance on the attempt. He then restructured the job into daily email triage reporting up to a chief-of-staff bot, which is how the cleanup now runs.
This only partly worked. Worth knowing before you try it.
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.
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.