Run multiple sessions without collisions (the message bus)

Lesson 5 of 7 · Module 01 · Set Up Your Command Center

Two Claude sessions, working at the same time, on the same agency. That is where most people break things. Here is how you run that without them colliding.

When one client is moving and another is on fire, I don't wait. I open a second Claude session. Now there are two of them awake at once. That is the moment the foundation you built in lessons 3 and 4 earns its keep, because two sessions that don't know about each other will quietly overwrite each other's work.

The whole system rests on one rule: a session never works a workstream that another session owns.

STATE.md is what makes that rule real. Every workstream has a row. Every row has an owner. Before a session touches anything, it reads STATE.md. If a row already says another session owns that work, it does not do the work. It stops, notes it, and hands it back to me. That sounds slow. It is the opposite. It is what lets two sessions run in parallel without me holding the whole board in my head.

So how does work actually move between them? It does not move session to session directly. They can't talk. It moves through me, and through one folder: the outbox.

Here is the lived pattern. Session A is deep in one project and realizes a piece of work actually belongs to a different project's session. Instead of doing it in the wrong place, Session A writes a complete, paste-ready prompt and drops it in command-center/outbox/. That prompt carries everything the other session needs to act with zero of Session A's context: the goal, the IDs and paths, what was decided, and what to write back into STATE.md when it's done. Then I copy it and paste it into Session B. I am the relay. The outbox is the message bus. STATE.md is the shared memory both sides trust.

And the bookends matter as much as the middle. Every session starts with "catch me up" so it reads STATE.md and the latest log before doing anything. Every session ends with the handoff: update your STATE.md row, log what shipped and what's in flight. Close the laptop, and nothing lives only in a chat window that's about to disappear.

You don't have to memorize any of this. Prompt 04 in the Prompts Pack is the three you reuse every day: catch me up, hand off, and relay. Grab it, keep it somewhere quick, and you can run two sessions tomorrow.

Next lesson: making every new project you create obey these rules automatically, forever.

Jerry