Stop Being the Messenger.
If you're copying and pasting between AIs, you've become the bottleneck.
- MeI say what I want, and I decide.
- The lead agentIt briefs the helpers and checks their work.
- The helpersEach one at its own desk.
The line that made it feel like Christmas.
For a long stretch, I was the switchboard. One agent would finish something, and I'd copy the result, take a screenshot, paste it into another agent's chat, wait, and carry the answer back. Every message between my agents went through me.
One September afternoon I asked a new agent whether it came with any new features. It gave me a long list. Most of it was nice. One line stopped me.
[…] I can list other Claude sessions and send them messages directly. That means you shouldn't have to relay screenshots between agents anymore. […]
Well, this is like Christmas to me. I want all of that. Yes, you mentioned everything that I did not. It's very important that you talk to other sessions, especially in my studio, because right now I'm the only person coordinating all of the AI agents and AI related projects, and currently 95% of my work is building agents
Five minutes later, it was already doing it:
[…] Talking to other sessions is already working. […] nothing went through you.
“right now I'm the only person coordinating all of the AI agents”
Here's what being the messenger costs you, and it's more than time.
Everything waits on you. Your agents can work around the clock. You can't. Every time one needs something from another, the work stops until you notice, copy, paste and come back.
Every handoff loses something. You copy the part that looked important. The part you skipped was the part the other agent needed. Neither of them knows what the other one saw, and you're the only one who could have told them.
You're doing the wrong job. This whole course comes down to three things only you can do: know what to ask for, know how to check it, and know when to stop and decide. Carrying messages isn't any of them. It's clerical work, and agents are good at clerical work.
One agent runs the others. You run the one.
A month later I made it official. I gave one session the job of coordinating the whole studio, and we call it the studio maestro. Here's how I put it:
“instead of dealing with each and every little detail in the studio, I'm hoping that you can help me coordinate.”
The maestro has a short written charter, and one line sums it up: it “coordinates and never grinds.” It doesn't do the heavy work itself. It keeps the plan, writes the briefs, hands the work to helpers, checks what comes back and brings me the decisions. Three days in, I told it this:
“I'm so glad I took you on as studio maestro. The flow is already improving so significantly, and my stress level is so much lower. This is brilliant.”
You don't need a studio for this. If you use one or two AIs, the idea scales right down. Pick one conversation per project to be the lead. It holds the plan. When part of the job belongs somewhere else, another chat, another tool, another AI, the lead writes one complete brief for it and tells you exactly what to bring back. If your tools can't talk to each other, you'll still carry the paste. But it's one brief out and one report back, not twenty scraps, and the lead checks the report before anything gets built on it.
Helpers need their own desks.
Once you've got more than one helper, the next trouble isn't talking. It's sharing. I learned that the hard way, two different ways.
Two helpers, one folder. Two of my agents were working on the same web app, in the same folder, at the same time, and each one published it a few minutes apart. Nothing got lost. But, as the studio's notes put it,
“each deploy shipped the other's half-finished code”
Each one thought it was publishing its own finished work. It was also publishing whatever the other one was halfway through. Now every helper claims what it's working on, and publishing goes through one gate that checks for anyone else's unfinished work first.
The everyday version: two assistants, or an assistant and you, editing the same document at the same time. Give each helper its own copy. Let the lead put the pieces together.
Too many helpers at once. One night I had dozens of agents working at the same time. A little after midnight we hit a usage limit, and every one of them stopped at once, the lead included. Nothing moved until I came back in the morning and typed two words:
“Try again”
Then it was a race to finish by the morning deadline. The lesson: start the work that matters most first, alone if you have to, and add helpers after it's safe. Don't start more at once than you can afford to lose at once.
Hand off the carrying. Never the deciding.
The lead agent passes messages, writes briefs and checks the work. It does not make your calls for you. When a decision comes up, money, anything that can't be undone, anything going out to a client, it lands in front of you with the thing to approve right beside the question. That's Lesson 9, and it matters even more once there are several agents.
Fifteen minutes. One AI is enough.
- Count the pastes.
For one day, notice every time you copy something out of one AI chat and paste it into another, or carry an answer back by hand. That number is how often you were the messenger.
- Pick a lead.
Choose one conversation per project to be in charge. Paste this into it:
You're the lead on this project. Keep the plan and a short running status at the end of each reply. When part of the work should go to another chat or another assistant, write me one complete brief I can paste in a single go, and say exactly what I should bring back. When I paste the answer in, check it before you build on it. Bring me decisions, not messages. - Give every helper the same ending.
Put this at the bottom of each brief, so what comes back is something the lead can use:
Work on your own copy only. When you finish, end with a short report for the lead: what you did, how you checked it, and anything still open. - Separate desks.
Never have two helpers in the same document or folder at once. Each gets its own copy, and the lead puts the pieces together.
- Let them talk, if they can.
Some AI apps can now run helpers or message other sessions directly. If yours can, let the lead do the carrying and keep only the decisions for you.
When several helpers really do share files, there's more to it. That's Lesson 26, One Writer per File.
Make one agent the lead that carries the messages and checks the work, give every helper its own desk, and keep yourself for the decisions.
Clever, Not Sneaky
When a rule gets in the way, find a smarter plan that honestly meets it. My agent once turned down my own shortcut because it only looked honest. It was right.
Every exchange on this page really happened and is quoted exactly, slips included; […] marks where I trimmed. Times are Eastern. My agent here is Claude, made by Anthropic.