The Morning Brief.

Open Claude Code in your local workshop folder. Onboarding wired up your remotes: upstream points at the AI Build Lab course repo (read-only), origin points at your own private GitHub repo. Course updates flow IN from upstream. Your work flows OUT to origin.

The brief needs your Gmail and Calendar connected. You wired these in Stage 02, but a five-second check now beats a confusing failure later.

Gmail and Calendar should both show green. If either is red or missing, the brief will start with empty source data and the rest of the build wastes your time.

This is the backend that stores your briefs, source registry, and delivery log. Vercel will read from this in Step 07, so it has to exist first.

• Sign up at supabase.com if you haven't (free for new accounts). Signing up gives you an organization automatically.
• Recommended (Supabase connector): if you've connected the Supabase connector, Claude creates the morning-brief project and runs the schema (0001_morning_brief.sql) for you, then confirms the tables exist. No SQL Editor, no database password to set by hand.
• By hand (no connector, or to learn it): create the project yourself at supabase.com, then open the SQL Editor, paste the contents of apps/morning-brief/supabase/migrations/0001_morning_brief.sql, and Run. You should see "Success. No rows returned."

Either way, the agent helps. With the Supabase connector, Claude creates the project and runs the schema directly, so you skip the SQL Editor. Without the connector, you do those two steps yourself in the Supabase website and Claude tells you exactly what to paste. Your only must-do is a free Supabase account and signing in when asked.

Your API URL is public (not a secret), so Claude sets its two URL placeholders for you directly. Your two keys are secret, so Claude creates them as PASTE_HERE and you fill them in yourself, across three placeholders (the anon key under two names, service_role under one). You first paste Claude your Infisical project ID (an identifier from the URL, not a secret). You will never paste your real Supabase keys into this chat with Claude.

If Claude offers to enter a real key for you, say no. The API URL is public, so it's fine for Claude to set that one, but every real key you type yourself in Infisical. Do not create a project .env or .env.local with real values.

After Claude finishes, fill in just the two keys yourself in the Infisical web UI (your API URL is already set). Open Supabase, Settings, then API Keys, on the Legacy API keys tab (not the default Publishable/Secret tab):

• The API URL is already set for you in both SUPABASE_URL and NEXT_PUBLIC_SUPABASE_URL, so you can skip it.
• Copy the anon public key into both SUPABASE_ANON_KEY and NEXT_PUBLIC_SUPABASE_ANON_KEY.
• Copy the service_role secret key into SUPABASE_SERVICE_ROLE_KEY. Treat this one with extra care, it bypasses row-level security.

Pick Telegram, email, or both. The brief will fire to whichever channels you wire up. Most students do Telegram. Some do email-only. Some do both. If you've already shipped a Stage 03 build like iMessage Status Check or Email Reply Queue, the channel pattern is the same one at smaller scope.

If you want Telegram:

• Open Telegram. Search @BotFather. Tap Start.
• Send /newbot. Pick a display name. Pick a username ending in bot (for example, your_morning_brief_bot).
• BotFather replies with a token. Save that token to Infisical as TELEGRAM_BOT_TOKEN.
• Send your bot any message first. Bots cannot start conversations, you have to message it first or it cannot reach you. Type hi, anything.
• In a browser, open https://api.telegram.org/bot<YOUR_BOT_TOKEN>/getUpdates. Find result[0].message.chat.id. That number is your chat ID. Save it as TELEGRAM_CHAT_ID.

If you want email:

• The brief sends via the Gmail MCP you already wired in Stage 02. No new setup needed.
• Tell Claude the email address to send to. Yours, usually.

This is where the sub-agents wake up. /build-morning-brief reads the blueprint, asks you a handful of setup questions, then spawns sub-agents to scaffold the project, generate the brief compiler, and wire your sources.

The skill walks you through:

• Picking your sources (Gmail, Calendar, manual notes, Obsidian vault, optional official Exa setup for 8D)
• Choosing your delivery channel (matches what you set up in Step 05)
• Choosing where the markdown fallback lands (your Obsidian Inbox folder is the recommended pick)
• Confirming a cost ceiling so the agent does not loop on expensive calls

The agent does this for you. The skill produces a compiled brief from today's sources and writes it to a dated markdown file. It also stages the Vercel project structure under apps/morning-brief/. You will not see the deployed dashboard yet, that comes in Step 07.

This is where the dashboard goes live. Important: it must be auth-gated, so only you can see your brief.

• If you have not already, confirm origin points to your own private repo named <your-username>/agent-native-os-private. Push your work to origin: git add . && git commit -m "wire morning brief" && git push. Your real secrets are in Infisical, not committed files.
• In Vercel → Add New Project, choose the free Hobby plan and import your own private repo (<your-username>/agent-native-os-private), not the AI Build Lab / aibuild-lab org repo.
• Set the Project Root to apps/morning-brief. Vercel asks during import. If you skip this, the build fails.
• Framework preset auto-detects as Next.js.
• Expand Environment Variables. Add every required value from Infisical into Vercel for Production, Preview, and Development: SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY, NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, plus TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID if you wired Telegram.
• Click Deploy. Wait about two minutes.
• Once it deploys, enable Vercel password protection on the project (or wire Supabase magic-link auth in front of the read view). The brief contains your private data, do not leave the URL publicly readable.

Run the brief skill one more time end to end:

You should see five things in order:

• The skill completes without errors.
• A new dated markdown file appears in your Obsidian vault at ~/Documents/Obsidian/Inbox/morning-brief-YYYY-MM-DD.md.
• Your Vercel URL renders today's brief (you log in first if the auth gate is on).
• The Telegram ping lands on your phone (or the email lands in your inbox) with the brief headline and your top priority.
• Refresh the Vercel dashboard. The delivery log shows the new entry.

Open Supabase. Table editor, then the briefs table. There should be a row dated today with the compiled brief. Look at delivery_logs, you should see a row for the ping that just fired. This is your audit trail.

The reason this matters: tomorrow, when the cron fires while you are asleep, this is where you'll check that it actually ran.

The final step. The brief is built. The dashboard is live. Now you wire the cron that fires it before you wake up.

The agent does this for you. Claude generates the cron entry, configures the headless Claude Code session, sets the time, and writes a one-line kill switch you can run from your phone if the brief starts going sideways.