Agent Native OS
Workshop.
Install the architecture
that runs our company.
Today it starts running yours.
Your first build is a Morning Brief, live by tonight. Afterward, things you only dreamed of building become possible.
Today's schedule
| Time (ET) | Section | Node |
|---|---|---|
| 10:00-10:30 | Welcome + Overview + 7-Layer Stack | The map: what you're building + why |
| 10:30-11:05 | Sub-Agents + Fleets | First sub-agent swarm |
| 11:05-11:15 | Short Break | 10 minutes |
| 11:15-11:50 | Connecting Your Data | Sources wired to the brief |
| 11:50-12:25 | Security + Observability | Keys vaulted + runs traced |
| 12:25-1:00 | Knowledge + Memory | Cairns 101: teach + demo the layers |
| 1:00-1:10 | Short Break | 10 minutes |
| 1:10-1:45 | Build the One Cairn | Your second brain, on disk |
| 1:45-2:05 | Lunch | 20 min (working lunch + Q&A) |
| 2:05-3:00 | Wire + Deploy: Morning Brief | The deployed brief |
| 3:00-3:30 | Close + Open Q&A | Showcase + what's next |
Quick poll: where are you today?
Drop a number in the chat so we pace the day for the room. No wrong answer.
New to Claude Code. Here to see what's possible.
Used it a few times. Still finding my footing.
Live in the terminal. Ready to go deeper (8D).
Just write it in the chat, so we know who's already set up and who's brand new. Welcome either way.
It's not theory. It's what's powered all this:
Not Professors. Agent Native Orchestrators.
Five people who build this stuff every day, in the room with you the whole time.
Last cohort walked out with these.
Real morning briefs. Real deliveries. Real machines. By tonight you start yours.
You did not buy the morning brief.
You bought everything behind it.
The morning brief is one expression of what this architecture can do. The repo has hundreds more, and your Claude knows how to install all of them.
Sub-agents, background agents, team agents. All yours.
Blueprints, guides, and a Cairns knowledge vault.
Start it today. Expand it all week and into Summer Camp.
One Operating System. A whole fleet behind it.
Everything today lives in one place.
Wade built your portal: a visual map and teacher for the agent-native-os repo. Every prompt, every skill, the full run of show. You have exclusive access. Open it now and keep it open all day.
The 7-Layer
Stack.
Everything you bought, from the bare repo to the Growth OS. You install the first layers today.
This is the whole system. You bought all of it.
Seven layers, one path: Repo → Harnesses → Orchestration → Agent Native OS → Blueprint → Growth OS → Outcome. Today you install the first layers as your morning brief. Summer Camp takes it all the way to a business that pays.
You're already
set up.
Setup happened before class. Returners, one quick update and everyone starts level.
Your machine is ready.
- Claude Max active
- Claude desktop + Code CLI working
- GitHub CLI authenticated (gh auth status)
- agent-native-os repo cloned
- /personalize run, CLAUDE.md is yours
- Infisical secrets manager installed + signed in
- Secrets Guard hook active (blocks secret leaks)
- (bonus) first connector wired
Open the GitHub folder from setup and select agent-native-os.
Run /update-course to pull the latest. It preserves your personal work and only adds new course material.
No /update-course yet? Tell your Claude to pull the latest from the agent-native-os upstream.
Pre-flight complete.
Cleared for launch.
You're loaded in. Five moves, one brief.
Let's build!
We build the morning brief
block by block.
Every section follows the same rhythm. Teach the idea, Demo it live, then you Build the block yourself.
The idea, and why it matters. No terminal yet.
We run the skill live. You watch a block get built.
You run the same skill. 4D gets the MVP, 8D goes deeper.
Five moves. One Morning Brief.
Here is the whole day. Each move lights up as you finish it. The last one is the goal: your brief, deployed and live.
No matter where you're at, we've got you covered.
- ·First time in Claude Code, or early experience.
- ·Here to see what's possible and leave with working blocks.
- ·You build the MVP of every block today.
- ·You live in the terminal. Claude Code is a daily tool.
- ·You want to go deeper, not just get it running.
- ·You customize each block and preview the summer-camp moves.
Your fleet does
the work.
First move: build your fleet.
- ·Parallel workers, one context each.
- ·Each gets a scoped job + an output contract.
- ·They all report back to the lead.
- ·Long-running, keep working after you leave.
- ·Good for builds, scrapes, and watchers.
- ·You check the result, not the clock.
- ·A fleet with named roles.
- ·They coordinate toward one goal.
- ·A lead splits the work and merges it back.
Sub-agents · Background agents · Agent fleets
Your turn: run your swarm.
Prompt on your Workshop Day page · breakout rooms open
Run a research swarm on your own idea.
Paste the Research Swarm prompt from your run-of-show. It spawns three sub-agents in parallel: web, your repo, your transcripts. Then it synthesizes one consensus brief.
Customize the roles and model tiers (Haiku workers, a stronger synthesizer). Then wire the swarm onto a real recurring job so it runs without you.
The exact prompt lives on the LMS Workshop Day page. No new command to memorize.
Short Break
10 Minutes
You just ran your first fleet.
Next: connect your sources so the brief has real things to read.
Your AI can see
your world.
Next move: connect your sources.
Tools come in two shapes.
A persistent connection: Gmail, Slack, Drive. The fleet reads and writes live.
- ·Tokens / context: every connected MCP loads its tools into your context, even when idle.
- ·Functionality: covers a subset of the platform (Slack connector ~11 actions).
- ·Customization: you get what the maker built.
- ·Accounts: native connectors connect one account at a time.
A one-shot tool the agent calls: fetch, transform, post. Efficient and composable.
- ·Tokens / context: loads into your context only when it runs.
- ·Functionality: can reach the platform's full API (Slack: 2,000+ actions).
- ·Customization: can be custom-built for exactly what you need.
- ·Accounts: can connect all your accounts at once.
Connecting your sh*t
Your turn: connect your sources.
Prompt on your Workshop Day page · breakout rooms open
Wire your first source.
- 1.Pick one source you actually use (Gmail or Calendar).
- 2.Wire it in.
- 3.Ask it one real question.
- 1.Wire three sources at once.
- 2.Give each its own sub-agent.
- 3.Have them all feed one brief.
How to trust
your fleet.
Next move: vault your keys.
How To Trust
The Fleet.
Security + Observability. Here is how we keep it safe to let agents work.
It asks before it acts. You promote a project to auto only once you trust it.
Secrets stored in Infisical for safekeeping. Your deployed app reads its own copy from Vercel.
Version control plus one backup, so any mistake is cheap to undo.
See every agent action, token, and cost. Nothing happens in the dark.
Security and Observability
Your turn: lock it down.
Prompt on your Workshop Day page · breakout rooms open
Lock down your fleet.
- 1.Claude creates each key as a safe PASTE_HERE placeholder. It never sees a real secret.
- 2.You type the two real Supabase keys into the Infisical web UI yourself.
We wire Langfuse live: Stop + PostToolUse hooks that trace every agent action, token, and cost. Watch it in the room, take the pattern home.
- ·Nothing your fleet does happens in the dark.
Your fleet
remembers.
Cairns 101: the foundational concept of the whole system.
Next move: build your second brain.
Every session, your agent starts from zero.
It is not a missing-data problem. It is an untiered-data problem. You either tell it too little or you drown it in everything.
No memory. It forgets yesterday, re-asks what you already answered, repeats old mistakes.
Dump every transcript into context. It drowns in noise, misses the signal, and you pay for every token, every call.
Tiered recall. Load a tiny map always, fetch detail only when the question needs it.
A cairn marks the path.
Tyler stacks stones on hikes with his family. A cairn is that stack: a marker that tells the next traveler which way the path goes.
Not the whole mountain. Just the marker you need to keep moving. One source, one cairn.
Three tiers. Load light, drill deep.
L1 routes. L2 summarizes densely. L3 proves.
~16 categories, ~6k tokens. The map. 60-70% of questions stop here.
e.g. a card for you, one for current projects, one for hobbies.
Dense summaries. The catalog the map points into.
e.g. the same topics, with the detail behind each one.
The raw source, never edited. The exact quote, with provenance.
e.g. the full transcript or original doc.
Every agent asks the Librarian.
The Librarian fans out across every cairn at once. Most questions are answered right here.
Need more? Pull the L2 card. Need the exact line? Fetch L3. It stops as soon as it has enough.
Every answer comes back with its source: which cairn, which tier, which line.
Same answer. A fraction of the cost. None of the noise.
Memory Layers + Cairn System
Your turn: build your Cairn.
/build-agent-conversations-cairn · breakout rooms open
/build-agent-conversations-cairn
Reads your recent Claude conversations. You approve the L1 waypoints. L1 + L2 + L3 land in your vault.
- 7DObsidian: a visual graph your agents read and write.
- 8DPostgres + pgvector: real semantic search at scale.
- 9DGraphRAG: entity + relation graph, answers that trace their path.
- 10-12DNeo4j: a production knowledge graph, multi-hop reasoning.
Explore the Stack.
LUNCH
Back in 20 minutes.
The Morning
Brief.
You built it all day. Now watch it snap together.
Four blocks built. Time to ship.
Every block you built today snaps into the brief.
Ship the Morning Brief, live.
Your turn: run it.
/build-morning-brief gmail,calendar (+ ~/briefing-config.md PRD)
/build-morning-brief gmail,calendar
Claude assembles the app from everything you built today. Deploy it on Vercel: import your private repo, set the project root to apps/morning-brief, and paste your keys into Environment Variables.
- ·Schedule it: the brief rebuilds itself every morning.
- ·Add delivery: a Telegram or email ping when it is ready.
- ·Add sources: more agents feeding a richer brief.
What comes
next?
You shipped one brief. Here is the ceiling it climbs toward.
Your brief becomes a command center.
Not a feed you skim. A surface that shows what changed, what needs a decision, and what your fleet already handled. Tyler's Pepper board is the live example.
Email, calendar, Slack, iMessage, GitHub: every channel summarized and ranked before you open a single app.
Your Cairns feed it directly. It already knows what you decided last week and who you owe a reply.
What ran overnight, what worked, what needs a human call. One click to approve, delegate, or dig in.
The morning brief is one expression.
The Agent Native OS is the full framework.
Point it at any business. The same five modules show up every time.
SUMMER
CAMP!
Take the whole stack all the way: ship production agents, build a real business on it.
You leave with a working Agent Native OS
for one real business.
Runs on as little as Claude Code. Scales to a full self-hosted fleet we share openly. The framework meets you at whatever level your stack is at.
Your visual map + teacher for the repo.
Everything today, and everything you did not get to, lives here. Your private guide to the agent-native-os repo: prompts, skills, the full run of show. Copy, paste, keep building.
