Arrive ready.

Six accounts and three local installs. Get all of them green before workshop day.

Accounts

• Claude (Anthropic). The Max plan ($100/mo) is what we recommend. Pro works for the workshop but you will hit message caps mid-day on the build.
• GitHub. Free tier is fine. Submit your username through the onboarding form so the team can send your repo invite.
• Infisical or 1Password. Infisical is the preferred team-grade secrets path. 1Password is still useful, and a gitignored .env fallback is acceptable for local practice.
• Google account. The morning brief reads from Gmail, Calendar, and Drive. Pick the account you actually use day-to-day.
• Vercel. Free tier. Sign up with GitHub for one-click deploy.
• Supabase. Free tier. The morning brief uses it for any persistence.

Local installs

• Claude Code. The terminal CLI. Different from Claude Desktop; you want both. Install instructions in the workshop installer.
• Node.js. Version 20 or newer. node --version to check.
• Git. Pre-installed on macOS; on Windows use Git Bash or WSL2.

The student repo is the canonical source. Clone it before workshop day so you arrive with a working setup.

cd ~/Documents
gh repo clone aibuild-lab/agent-native-os
cd agent-native-os
bash verify.sh

Windows users: use Git Bash or WSL2, not PowerShell. The common setup fracture point is Windows + native PowerShell + Claude Code path mismatches. Pick one Unix-like shell and stick with it.

If verify.sh fails, copy the output into Claude (Desktop or Code) and ask "fix this for me." Don't guess.

Slack is where the cohort lives during and after the workshop. Three steps to confirm you're in:

1. Accept the invite in your email (subject: "You've been invited to AI Build Lab on Slack").
2. Join #agent-native-os and pin it.
3. After submitting onboarding, check your email for the GitHub repo invite and accept it.

If you do not see an invite email, check spam, then DM Tyler with the email you signed up with.

Workshop assumes you've seen these terms before. You don't have to memorize them; just skim once so you don't get lost.

Workshop Lexicon → — 109 terms, two definitions each (plain-speak + under-the-hood). Open in a tab during workshop day.

The terms most worth pre-skimming: agent, MCP, slash command, CLAUDE.md, connector, OAuth, Cairn, 4D / 8D.

Day-of structure (rough):

• Morning. Setup gate, framing, opening demos.
• Mid-day. 4D track: morning brief build. 8D track: extensions in a separate Wade room.
• Afternoon. Capstone push, deploy to Vercel, troubleshooting clinic.
• Wrap. Honest framing: partial completion is the norm. Most students don't finish a live deploy in-class. The portal is for everything you didn't get to.

4D vs 8D: 4D is the basic working setup (morning brief deployed). 8D is the advanced extension layer (cron, Slack relay, multi-source). You don't have to pick before workshop day — most start 4D and come back for 8D extensions later.

Workshop day kicks off with /personalize, a slash command that asks you 21 questions about your role, goals, and preferences. It runs 30-60 minutes in-class. You can shorten that to 5 minutes by answering the high-leverage questions in writing first.

Optional: write a paragraph in advance answering each of:

1. What's your role and what do you actually do day-to-day?
2. What's the one repetitive task you wish a Claude agent could just do?
3. What tools do you use most (apps, services, CLIs)?
4. What does "winning" look like for you by end of workshop?
5. What scares you about agents right now?

Save your answers in a get-to-know-you.md file. /personalize can read it and skip the longer in-class flow.