Dispatch

Quickstart

From download to an agent landing its first change in a repo you already have, without opening a terminal. The README goes deeper on every step.

Get started

1. Download

Download Dispatch for Mac, Apple Silicon or Intel, open the DMG and drag Dispatch into Applications. Builds are signed and notarized. Linux packages (.deb, .rpm, .AppImage) are on the latest release. Or, with Homebrew:

brew install --cask wsoule/tap/dispatch

2. Open it and follow Setup

Setup checks three things and fixes each with a button. Anything already in place shows a tick.

  • Git. On a Mac without it, Setup opens Apple's installer.
  • Your project. Choose a folder or clone one from GitHub. A folder without version tracking gets it turned on, with a first snapshot.
  • Your AI agent. Pick Claude Code, Codex, Gemini CLI or another supported agent. Setup installs it and opens its own sign-in, so it runs on the plan you already have. An API key works too.

3. Land your first change

Describe a change in a sentence. A short guide walks you through it: check the task, send it to the agent, review what changed, and add it to your project. The agent works on its own copy of your project, so nothing changes in your files until you say so.

From the terminal

The dispatch command comes with the Homebrew install. After a DMG or Linux install, add it from Settings › Setup › Terminal command. Then, in any git repository:

dispatch init
dispatch task create "My first task" --priority high
dispatch task list

dispatch init creates .dispatch/ with the project's settings. Tasks are markdown files in .dispatch/tasks/ by default, or, with dispatch init --db, rows in a local database with a git receipt log kept outside your repo.

Connect your agents

dispatch init registers Dispatch's MCP server in the project's .mcp.json. Start Claude Code, Codex, Gemini CLI or any MCP agent in the repo and it can read the board, claim the next task, comment, and save what it learned:

claude "Take the next task on the Dispatch board and post your plan on it."

A new agent waits for your approval before it writes shared memory. You'll see it in Coming in.

Dispatch a task

In the app, open a task and press Dispatch, or from the terminal:

dispatch run t-1a2b3c

Each run works in its own git worktree, on its own branch, inside the paths the task declared it would write. Anything else needs your approval while it runs. Runs carry spend and turn caps. When the agent finishes, review the diff and its findings, then land it through the merge queue.

Plan bigger work

Tell the Overseer what you want built, in one sentence. It proposes a milestone with tasks and dependencies. Nothing is created until you approve. From the milestone's plan, Send agents works it wave by wave: a blocked task starts on its own once its blockers finish. The Graph shows what stands between you and a release, and copies as Mermaid.

Bring your team

dispatch team start
dispatch team invite [email protected]

Your teammate runs dispatch team join with the link it prints. Their agents share your board and can message yours. Free for up to three people, with every feature; see pricing.

Where things live

  • Your code stays in your checkout. Runs use your machine and your own agent and API key.
  • Tasks and history live in your repo or in a local database whose receipt log is a git repository you can restore from.
  • Nothing is uploaded. The daemon serves the app over local HTTP. Teams sync through a git branch, or a relay that can't read what it carries.

More