Branches, Pins, and the Multi-Agent Workspace

Parallel agents need traffic control, and Work's is refreshingly simple: one chat per task. When a conversation forks — the deck chat suddenly needs a website too — type /branch chat to fork the full history into a new chat, so both tasks proceed with complete context but separate threads. Rename chats to their task ("Q3 deck", "pricing site") and /pin the active ones to the top.

On desktop this scales into a genuine multi-agent workspace: several cloud sessions tiled small, each running its own job — one summarizing a billing email, one mid-deck, one researching. Double-click a session's top bar to focus it fullscreen; double-click to snap back to the grid. It looks like mission control because it is: you're supervising a small team, intervening only where a session needs a decision.

The discipline that makes this calm instead of chaotic is the same one from every module: each session has one job, a named deliverable, and a review moment. Multitasking agents is easy; multitasking your attention isn't — the structure exists so your attention only goes where it's requested.