Documentation

How Dispatch works

Nine pages, in the order they're worth reading. Start with Getting started if you've just installed it, or go straight to The Deck if you're here for the agent side.

01Start

Getting startedInstall Dispatch, point it at your projects, and open the first few terminals.

02Core

BroadcastOne command bar, every targeted terminal — and each one is still a real interactive shell.The DeckWhat finished while you were elsewhere, what is blocked on you, and how to answer it without going to find it.PlanningInstall the MCP server, then let a lead session open the day's terminals itself — each in the right repo, each seeded with its own prompt.WorkspacesSeparate contexts with their own terminals, roots and targeting — and processes that keep running when you switch away.DocumentsOpen a markdown file as a live tile beside the work — rendered, editable, and readable back by the session that wrote it.

03Integrations

Studio and RojoLink a tile to a running Studio window, and see at a glance whether Rojo is actually synced.

04Reference

Keyboard and quick openEvery shortcut inside the window, plus the one machine-wide key that brings Dispatch forward from anywhere.LicensingHow keys, seats, trials and the offline grace window work — and an honest account of what the gate does not stop.

Dispatch v0.1.16 · Windows. These pages track the app's own README, which is the source of truth if the two ever disagree.