Send a daily morning brief in Slack from DMed reminders and a Notion calendar

Jabeen, an engineering director who also runs a content page, built a small agent on her Mac on 15 October 2026. She DMs a Slack bot all week, by text or voice note. Each message goes to Claude Haiku with no tools and no internet, which labels it as a reminder, idea, deadline, done item or question and pulls out the date. Results go into a local SQLite database, and an Excel sheet of everything is rewritten after each change. Reminders ping her at the set time. Every morning the bot also reads her Notion content calendar for what is scheduled this week and what is still in progress. A loop kept alive by launchd checks the clock every minute and at 8am Pakistan time sends a four-part brief in Slack, catching up until noon if the Mac was asleep.

It never sent a brief on schedule. The night after she built it, Slack began rejecting its token as expired, and from 25 October as not recognised at all. The bot did what it was told: quit after three minutes without a connection and let the Mac restart it, about twice a minute for more than two weeks, filling a log of over 50 MB. Nobody noticed, because Slack was also the only way it could report a problem. When she wrote it up she had not yet replaced the tokens.

Give the agent a second way to warn you before anything else. If it reports through the same app that breaks, a failure stays silent. Reading only the latest error also misled her about when it broke: the logs showed the night of the 15th, not the 25th. The brief only reads and reports to her, so it never sends anything on her behalf.