Documentation

How Dispatch works

Twelve 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.

12 pages66 sectionsDispatch v0.2.30 · Windows

01Start1

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

02Core6

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.

Branches and worktreesPut two tiles on one repository without them fighting over one checkout: each on its own branch, in its own folder, with the ones that have gone wrong saying so.

03Integrations2

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

Plugins and the MarketplaceOne place for the widgets Dispatch runs and the files it writes into other programs, each listing what it is allowed to touch, in words, before you install it.

04Reference3

Keyboard and quick openEvery shortcut inside the window, plus the one machine-wide key that brings Dispatch forward from anywhere.

CustomizingColours, terminal palette, your own buttons, the keymap and the shape of the window, as a folder of data that cannot run anything.

LicensingHow keys, seats, trials and the grace window work, and an honest account of what the gate does not stop.

These pages are written from the app's own source and its README, which are the source of truth if any of them ever disagree.