tmux: collaboration survives disconnects
Agents run as ordinary local processes inside tmux sessions. Work keeps moving when a browser closes or a connection drops, because the browser is a view into the terminal—not the thing keeping it alive.
Git worktrees: collaborate without interfering
Worktrees give each agent an isolated directory and branch. A developer can keep working while an agent investigates a bug or prepares a change, without either borrowing the other’s working directory.
PostgreSQL: shared context outlasts a terminal
Messages, reviews, pins, media, whiteboards, Brain state, jobs, and activity are persisted independently from terminal output. They preserve the record of a collaboration after an agent exits, a page refreshes, or someone returns later.
MCP: reusable capabilities in a shared environment
MCP exposes reusable, project-aware capabilities to agents as narrow tools. Agent-scoped tools carry the relevant repository context and permissions, allowing useful practices to be shared rather than hidden inside a single prompt or chat.
Local execution: keep the environment people already use
Dispatch uses the repositories, credentials, coding-agent CLIs, and compute already available on a macOS or Linux machine. It adds a durable workspace around the environment; it does not try to replace it.