Getting started — Dispatch

Dispatch is a mass-dispatch dashboard: live terminals for the projects you’re working on, in one grid, with a single broadcast bar across the top. It auto-discovers your projects, groups them by category, and lets you pin the ones that matter and hide the noise.

First launch

On first launch Dispatch scans a root folder and lists every project it finds under it. Change the root any time with the root button at the top-left of the sidebar — it lists every root you’ve used before, plus Browse for a folder….

The root is per workspace, so one workspace can be your Roblox games directory while the next is your JS/web directory. See Workspaces.

Opening terminals

Three ways, in rough order of how often you’ll use them:

Click a project in the sidebar to open a terminal in it.
Ctrl+Shift+P — fuzzy-open any project by name, however many you have.
＋ New terminal (or Ctrl+Shift+N) opens one in the workspace’s current folder without asking which project.

Each tile is a full interactive shell — PowerShell by default. Click into it and type as you normally would.

Running from a checkout

cd path\to\terminal-dispatch
npm start

To sanity-check the environment without opening the window:

npm run diagnose

It prints the terminal backend, the discovered project count, and a live PTY echo test.

Where to go next

If you want to…	Read
Fire one command into every repo	Broadcast
See which agents are blocked or finished	The Deck
Have an agent open its own terminals	Planning
Keep several contexts side by side	Workspaces
Know whether Rojo is really synced	Studio and Rojo

What Dispatch writes to disk

Its own settings live in the app’s user-data folder, alongside a bridge.json that exists only while Dispatch is running — it holds the pipe address and the token the MCP server authenticates with, and is deleted on exit.

The one file Dispatch writes outside its own folder is Claude Code’s user config (~/.claude.json, or $CLAUDE_CONFIG_DIR/.claude.json where that is set), and only the dispatch key under mcpServers, and only when you click the install button. The file is parsed, modified and written whole, a backup is kept beside it, and a config that doesn’t parse is refused rather than rewritten.