Run an overnight chief of staff for email and calendar
The system that triages my email, dispatches 6 parallel agents, and blocks my calendar before I wake up. Task: The system that triages my email, dispatches 6 parallel agents, and blocks my calendar before I wake up I used to start every morning the same way. 45 minutes of email triage. Scanning yesterday’s inbox, copying action items into my task manager, checking for duplicates, assigning priorities. Then calendar review. Then figuring out when to leave for meetings based on traffic. Then time-blocking my day. By the time I actually started working, I was already tired. Last month I built a system that does all of this before I wake up. By 6:15 AM, my task system is current. My calendar has drive time events calculated from real traffic data. And when I sit down, I press one button and six AI agents start working in parallel while I focus on what actually matters. The system runs on Claude Code + $100/month. A virtual assistant doing the same work would cost $400-1,000/month minimum. What you’re getting in this guide: → The overnight automations (email triage at 5:30 AM, calendar prep at 5:45 AM) → The Morning Sweep command (one button dispatches 6 parallel agents) → The Time Block workflow (auto-generates your daily schedule with location batching) → Complete architecture breakdown (4 layers: MCP servers, scheduled tasks, subagents, commands) → Every agent file copy-paste ready (email-drafter.md, client-notes.md, meeting-scheduler.md, and 3 more) → Every command file copy-paste ready (am-sweep.md, time-block.md, email-triage.md, calendar-prep.md) → The classification framework that keeps humans in control (Dispatch / Prep / Yours / Skip) → Step-by-step setup process (plan for a weekend) This is the complete system. Build it once, run it forever. The Architecture The system runs on Claude Code with scheduled tasks and subagents. Here’s how the pieces fit together. Layer 1: MCP Servers (The Connections) MCP (Model Context Protocol) servers give Claude Code access to external services. You need four. Google Calendar MCP Or use the full-featured version: Gmail MCP Todoist MCP (or your task manager of choice) Google Maps API (for drive time calculations) This requires a Google Cloud project with the Directions API enabled. Store your API key in your environment. Layer 2: Scheduled Tasks (The Triggers) Claude Code supports two types of scheduling Keep reading with a 7-day free trial Subscribe to The AI Corner to keep reading this post and get 7 days of free access to the full post archives.; tools: Claude Code. Human role: The original post does not say how a person stayed involved.; limitations: Requires a Google Cloud project with Directions API enabled and valid API keys stored in the environment. The source is a paid blog post, so full technical details may be behind a paywall. Integration uncertainty exists regarding the stability of MCP servers and scheduled task reliability. Human approval is mandatory before sending messages or modifying calendars to prevent errors..
Tools
Published on Agent Work Atlas:
Overview
The system that triages my email, dispatches 6 parallel agents, and blocks my calendar before I wake up
Workflow
The system that triages my email, dispatches 6 parallel agents, and blocks my calendar before I wake up I used to start every morning the same way. 45 minutes of email triage. Scanning yesterday’s inbox, copying action items into my task manager, checking for duplicates, assigning priorities. Then calendar review. Then figuring out when to leave for meetings based on traffic. Then time-blocking my day. By the time I actually started working, I was already tired. Last month I built a system that does all of this before I wake up. By 6:15 AM, my task system is current. My calendar has drive time events calculated from real traffic data. And when I sit down, I press one button and six AI agents start working in parallel while I focus on what actually matters. The system runs on Claude Code + $100/month. A virtual assistant doing the same work would cost $400-1,000/month minimum. What you’re getting in this guide: → The overnight automations (email triage at 5:30 AM, calendar prep at 5:45 AM) → The Morning Sweep command (one button dispatches 6 parallel agents) → The Time Block workflow (auto-generates your daily schedule with location batching) → Complete architecture breakdown (4 layers: MCP servers, scheduled tasks, subagents, commands) → Every agent file copy-paste ready (email-drafter.md, client-notes.md, meeting-scheduler.md, and 3 more) → Every command file copy-paste ready (am-sweep.md, time-block.md, email-triage.md, calendar-prep.md) → The classification framework that keeps humans in control (Dispatch / Prep / Yours / Skip) → Step-by-step setup process (plan for a weekend) This is the complete system. Build it once, run it forever. The Architecture The system runs on Claude Code with scheduled tasks and subagents. Here’s how the pieces fit together. Layer 1: MCP Servers (The Connections) MCP (Model Context Protocol) servers give Claude Code access to external services. You need four. Google Calendar MCP Or use the full-featured version: Gmail MCP Todoist MCP (or your task manager of choice) Google Maps API (for drive time calculations) This requires a Google Cloud project with the Directions API enabled. Store your API key in your environment. Layer 2: Scheduled Tasks (The Triggers) Claude Code supports two types of scheduling Keep reading with a 7-day free trial Subscribe to The AI Corner to keep reading this post and get 7 days of free access to the full post archives.
Reported result
The author claims the system completes tasks by 6:15 AM and reduces morning fatigue, but no measured metrics or verified outcomes are provided in the source. The text asserts a cost of $100/month versus $400-1,000 for a virtual assistant, but these figures are unverified. Acceptance check: Measure time saved on morning triage over two weeks and verify that no unauthorized emails or bookings were sent.
Human role
The original post does not say how a person stayed involved.
Limitations
Requires a Google Cloud project with Directions API enabled and valid API keys stored in the environment. The source is a paid blog post, so full technical details may be behind a paywall. Integration uncertainty exists regarding the stability of MCP servers and scheduled task reliability. Human approval is mandatory before sending messages or modifying calendars to prevent errors.
Try it
I want to set up an overnight chief of staff system using Claude Code. My business context is [replaceable: e.g., solo consultant managing client emails]. I have access to Gmail, Google Calendar, and Todoist. Please guide me through connecting the necessary MCP servers. First, perform a dry run: fetch yesterday's emails, categorize them into Dispatch, Prep, Yours, or Skip, and draft responses for the 'Dispatch' category only. Do not send anything. Show me the drafts and the proposed calendar blocks for review. If the output looks correct, I will approve the next step. If inputs are missing, ask me for specific API keys or account permissions before proceeding.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.