Six patterns make the founder UX livable. This essay covers session-keeper, delegation-orchestrator, inbox-zero-batch, deep-work toggle, Sunday review, and Friday ship log. Each is a single skill; together they make the system livable. Without them, an AI-native company collapses on the founder.
Read this if your AI agents are running but the founder's attention is being shredded by approval requests, surprise re-auth prompts, and after-hours notifications. The UX patterns are what determine whether the runtime is durable or whether the founder burns out at month three.
The system's job is to free the founder for work only the founder can do. 6 Daily AI Agents patterns make that real.
The session-keeper skill. Daily browser-session audit at 09:00. Walks every long-lived browser login (Stripe dashboard, Gumroad seller, GitHub admin, Beehiiv, etc.) and verifies the session is still alive. If a session expired, it Telegrams the founder with the exact URL to re-auth. No surprise re-auth prompts at 4pm when you're trying to ship something.
The delegation-orchestrator skill. A 60-second daemon tick that watches the inbox of pending agent-to-agent help requests, routes each request to the right specialist, and surfaces deadlocks (agent A waiting on agent B waiting on agent A) to Cooper for resolution. Without delegation-orchestration, multi-agent systems get stuck on circular dependencies and the founder doesn't know until a daily report shows the work didn't ship.
The inbox-zero-batch skill. Daily 17:00 CT digest. Aggregates all the agent-generated approval requests, draft outputs awaiting review, and unresolved error tickets into a single ranked list. The founder reviews the list, batch-resolves with a syntax like /approve 12,15,18 /reject 13,14, and the system fans the resolutions out to the originating agents.
The deep-work toggle. A primitive that suppresses non-urgent Telegram notifications during declared deep-work blocks. The founder fires /deep-work-on and the system holds non-urgent messages until /deep-work-off. Urgent items (P0 alerts, customer-facing failures) still go through; everything else queues for later batch review. Default schedule: M-F 09:00-12:00 CT (morning block) and 12:00-17:00 CT (afternoon block) auto-toggle via launchd.
The Sunday review. A weekly briefing assembled Sunday 08:00 CT covering: financial state (private to the founder, never published), open commitments rolled forward, decisions made this week, what shipped, what didn't, what to flag for the next week's agenda. ~600-word doc the founder reads in 4 minutes.
The Friday ship log. Public counterpart to Sunday review. Aggregates 7 days of git commits, postmortems, auto-promoted skills, ops notes into a draft the founder edits the "What I learned" section on, then publishes to /log. Every Friday for the public; the methodology compounds because the system is documenting itself in real time.
The combination is the Daily AI Agents founder UX. Without it, an AI-native company collapses on the founder — too many notifications, too many approval requests, too many surprises. With it, the founder works on the 4 things only the founder can work on (vision, customer relationships, hiring, hard pivots) and trusts the system to handle the rest.
**Chapter 6 summary:** Six patterns — session-keeper, delegation-orchestrator, inbox-zero-batch, deep-work toggle, Sunday review, Friday ship log — define the founder UX. Each is a single skill; together they make the system livable. The UX is what determines whether the runtime is durable.
← The /dashboard pattern · full paper · Build-prompt discipline →