Build the Bridge.
One agent you think with, one that runs the work, and helpers who never interrupt you. The captain shouldn't be reading every message.
- BeforeEvery message in my room
- What I asked forAn assistant for the traffic
- NowI talk to one. One runs the rest.
The captain is inundated.
By November I had a lot of agents working at once, and every one of them reported into the same conversation I used to think with my advisor. One Thursday afternoon I said:
[…] I think you need an assistant. Imagine me, the captain, trying to talk to my number 1, my first officer, and the officer of the deck bursts into the room every 2 minutes with a message, then the officer of the deck, then the CO, they the chiefs start showing up. The captain is inundated. […]
My advisor started an assistant that same minute to take all the helpers' messages and bring it only what mattered. That evening:
Okay, I appreciate you creating a yeoman. Please make sure all future sessions also create a yeoman. This is so much more pleasant than watching the scroll while I'm trying to read of all the text. This is actually quite pleasant.
A yeoman is a ship's clerk. That's what I called the assistant.
An advisor and an officer.
Two days later, on a Saturday evening, I made it the structure. My advisor was still doing work of its own while we talked, so I asked it to stop and hand all of it to that assistant:
“So I need you to stop working and pass notes to your yeoman because I need to be able to talk to you when I'm ready to talk. and I can't be interrupted with all kinds of text flashing on the screen. That's why we have a yeoman. […] I really need an advisor and the most productive we've been is when I'm able to have a banter with you backandforth.”
The assistant got a new title, the officer of the day. Then I gave it a rule about when it may break in. “Your number one” here is that officer; in my captain picture, my advisor was mine:
“Okay, I've asked your number one to only interrupt if he has to, and to wait for you to ask him questions. So if we can document that process, I won't have to repeat it in the future, and we can begin.”
Three seats.
One agent is still the common case. In a survey published in May 2026 of about 1,100 developers and working professionals, 69% said their current agent workflows use a single agent. So start with one. Add seats when the traffic starts landing in the room where you think.
An advisor you think with.
You talk to it. It stays quiet unless it needs you, and it doesn't run the work while you're talking.
An officer who runs the work.
It starts the helpers, takes their reports, and brings you only what needs you, in one batch when you ask.
Helpers who report to the officer.
Never to you. If a helper needs a decision, it goes up the chain.
Course 1's Lesson 15, Stop Being the Messenger already says “One agent runs the others. You run the one.” This lesson splits that one in two: the agent you think with, and the agent that runs the work.
It also changes how loud things should be, but not everything. Lesson 14, I Run on Carbon wants the urgent things right in your face, and that still holds. The officer interrupts only when something can't wait, and saves the rest for one batch. Reminders of anything you have to show up for are never batched: they come through on time, as that lesson says.
Talk to one agent. Let one run the rest.
Helpers report to the officer, never to you. The officer brings you what needs you, in one batch, and interrupts only when it can't wait.
If you run one agent and it's quiet, you don't need the rest yet.
Clear your room.
One paste when the traffic gets loud, and a one-day count first.
- Count the interruptions.
For one day, tally every message that pulled you out of what you were doing. How many could have waited for one batch?
- Set up the seats.
Only if the count says you need them. Paste this into the chat you think in.
You're my advisor. I talk to you. Set up one lead to run the helpers. Helpers report to the lead, never to me. The lead brings me only what needs me, in one batch when I ask, and interrupts only if something can't wait. Tell me what you'd count as can't wait, so I can agree or change it.
Talk to one agent. Let one run the rest. Keep the chatter out of your room.
Where this comes from in course 1. Course 1's Lesson 14 (loud for what's urgent), Lesson 15 (one lead runs the others) and Lesson 17 (fresh beats limping). New here: the agent you think with is not the agent that runs the work.
Pace the Burn
One big job can eat a big piece of your allowance in minutes. Pick a pace and say it, size big jobs first, and never spend the room for the handoff.
← Previous: Lesson 10, Is Anyone Following It?
Every exchange on this page really happened and is quoted exactly, slips included; […] marks where I trimmed. Times are Eastern. Names of clients, people, companies and products are left out. My agents are AI models; the names are left out on purpose.