The session interface

MobSession puts a room full of people in front of one agent. Everyone sees the same transcript, tool calls, and cost in real time. Here's what each part of the screen is telling you.

The header

The header runs across the top of every session.

• Join code. Share it to bring someone in. Anyone with it lands in the same live view.
• Presence bar. Who's here right now. Each person gets a color that follows them everywhere in the session.
• Status. A live, ended, or "agent stopped" marker. After a session ends you can still open it from your history and replay the full transcript read-only; new input is closed.
• Session details. A popover with the model in use and Claude's own session id, plus a ready-to-run claude --resume <id> command, so the orchestrator can pick the exact conversation back up in their own terminal or IDE.

The transcript

The center of the screen streams top to bottom as the agent works. It mixes a few kinds of entries.

Agent output

The agent's text streams in as it's generated, so you watch the response form word by word.

Tool cards and diffs

When the agent calls a tool, an inline card shows the tool name and its result. File edits are special: Edit, Write, and MultiEdit render as a real diff, with the file name, added and removed line counts, and red and green lines, so the room reads the exact change instead of a wall of JSON. Expand any card to see the full input and output.

User prompts

Prompts from the room show up as attributed bubbles, each carrying the sender's name in their color. You always know who asked for what.

Turn dividers

Between turns, a divider reports how long the turn took and what it cost in dollars. The room gets a running sense of pace and spend.

Working indicator

While the agent runs, a working indicator shows a response is in progress. When it clears, the turn is done.

The composer

The composer sits at the bottom. Anyone in the room can use it.

• Type and send. Enter sends. Shift+Enter adds a newline.
• Paste an image. Paste straight into the composer to send it with your prompt.
• Typing indicator. Shows who's writing, so the room doesn't talk over itself.

Since everyone shares one composer, the typing indicator is room etiquette: you can see a teammate is mid-thought before you send.

Reactions

Messages support reactions, a quick way to agree, flag, or acknowledge a turn without sending a full prompt.

Host controls

If you started the session (or you are an admin of its organization), MobSession shows host controls in the web, so you can govern the room from the browser, not only from the terminal:

• Approve or reject each prompt waiting in the queue.
• Trust the room so prompts run automatically, or turn it back off.
• Lock posting to yourself during a delicate step, then reopen it.
• End the session when the work is done.

Everyone else watches the transcript and can add prompts; only the owner sees the controls.

The orchestrator's terminal view

The orchestrator running the session also has a terminal view of it. The terminal and web transcript reflect the same agent, turns, and tool calls. The orchestrator can drive from the command line or, as the session owner, from the web with the host controls above, whichever fits the moment.

What comes next

• Prompt queue: line up prompts to plan the next turns together.
• Attribution: how MobSession ties prompts, colors, and presence back to people.