dispatch
Sessions waiting on you:0finished:0· all quiet
Sign inStart the trial

Docs Core

Broadcast

One command bar, every targeted terminal, and each one is still a real interactive shell.

Type in the bar at the top and press Enter (or Send). The command goes to every targeted terminal: the ones whose checkbox is ticked.

Targeting

  • All / None target everything or nothing.
  • When several groups are open, group chips appear. Click one to target that group alone.
  • Tick and untick individual tiles with the checkbox in each tile header.

The counter reads 3/4 targeted, so the bar always answers the question “what is Enter about to hit”.

Interrupting and clearing

  • Ctrl-C sends an interrupt to all targeted terminals.
  • Clear clears their screens.

Both respect targeting rather than reaching every open terminal.

It is still a normal shell

You can click any single terminal and type into it normally. Broadcast is an extra way to reach the shells, not the only way. Nothing about a tile is read-only or replayed.

Discovery, pinning and noise

Dispatch groups discovered projects by category and shows each one’s type, branch and a clean/dirty dot. Two controls keep a large workspace usable:

  • Pin the projects you’re actively on. They collect under ★ Pinned at the top.
  • Hide the ones you never open. The [Hidden] toggle brings them back when you need them.

Pins, hidden projects and recents are stored by full path, so they are shared across every workspace rather than being set up again per root.

Git status

Every tile and sidebar row shows its branch and a clean/dirty dot, plus ↑/↓ ahead-behind. It refreshes on a timer and after a rescan, which is usually enough to notice you are about to broadcast git pull into a repo with uncommitted work.

Completion pings

When a terminal rings the bell (how long-running tools signal “I’m done, your turn”), Dispatch flags it, whatever is running in that tile. The tile border and header glow amber with a pulsing dot, the sidebar row gets a marker, and inactive workspace tabs show a count of how many terminals are waiting.

If the window isn’t focused, or the terminal is in a different workspace, you also get a Windows toast; click it to jump straight to that terminal. Clicking or typing into a terminal clears its flag, and nothing pings for the terminal you’re already looking at.

The 🔔 button in the top bar mutes the toasts. The in-app highlight stays either way.

The bell means a session needs you. It does not mean the work is done, and a session that stops without ringing tells you nothing at all. Sessions that report for themselves close that gap, which today means Claude Code. See the Deck.