MobSessiondocs

Terminal and web, in sync

How a MobSession keeps the orchestrator's terminal and the mob's browser as one live, bidirectional session.

A MobSession is one session shared by many people. The orchestrator drives it from their terminal, the mob watches and chips in from the browser, and both stay in sync in real time. There's no "host screen" and "follower screen." Both are live views of the same running session, and input can come from either side.

One session, two surfaces

The orchestrator runs the session in their terminal exactly like a normal Claude Code session: the agent's output streams in, the orchestrator types prompts directly, and ESC interrupts at any time. The local experience doesn't change.

The mob sees that same session in the browser. It's not a recording or replay. What the agent says, what the orchestrator types, and what the mob types all show up on both surfaces as they happen.

What flows both ways

Input and output move freely between terminal and browser:

  • Agent output streams to everyone. As the agent thinks and responds, that output lands in the terminal and the browser at the same moment.
  • A prompt typed in the browser drives the agent. A prompt submitted from the browser appears in the orchestrator's terminal and goes to the agent, just as if the orchestrator had typed it.
  • A prompt typed in the terminal shows up for the mob. When the orchestrator types, the mob sees it. Everyone follows the same thread.
  • The orchestrator can always interrupt. ESC in the terminal stops the agent mid-run, the same as in any Claude Code session.

The result is one conversation with the agent that many people can read and contribute to at once.

Why the orchestrator is never out of the loop

The terminal is the source of truth. Every prompt, whether it started in the browser or the terminal, lands in the orchestrator's terminal before it reaches the agent. That gives the orchestrator:

  • Full visibility. Every incoming prompt and every line of agent output in one place. Nothing happens off to the side.
  • Direct control. Typing into the same session, the orchestrator can redirect the agent, add context, or jump in with their own prompt anytime.
  • Immediate interruption. ESC is one keystroke away. If the agent heads the wrong way, the orchestrator stops it without leaving the terminal.

The mob gets a live seat; the orchestrator keeps their hands on the controls.

A quick walkthrough

  1. The orchestrator starts a session in their terminal and shares the link with the mob.
  2. The mob opens the browser view and sees the live session.
  3. Someone in the mob submits a prompt. It appears in the orchestrator's terminal and drives the agent.
  4. The agent responds. Its output streams to the terminal and the browser together.
  5. The orchestrator types a follow-up. The mob sees it, and the agent acts on it.
  6. If the agent goes off course, the orchestrator presses ESC to interrupt.

Keep reading