Dispatch
Menu
IdeasArchitectureDocs Principles
GitHub ↗

Architecture

A visible control plane around durable work.

Dispatch coordinates local agent processes and the artifacts around them. It does not attempt to replace the tools that make a repository useful.
Browser UI SSE · WebSocket · HTTP
Dispatch server
Agent lifecycle Messages, media, pins Jobs, reviews, MCP
tmux sessions Agent CLIs + project worktrees
PostgreSQL Shared, durable state
The browser is a view into durable local work. Processes and shared state continue independently of a tab.

Agent lifecycle

Agents run as ordinary local processes inside durable tmux sessions. Their browser presence is a view into the work, not the process that keeps it alive. Each agent can have a worktree and branch, so parallel changes remain isolated until they are intentionally combined.

Shared state

Messages, reviews, pins, media, jobs, and activity are persisted independently from terminal output. They are the parts of a collaboration that should still be useful after an agent exits or a page refreshes.

Extensibility

MCP exposes project-aware capabilities to agents as narrow tools. The aim is not to require a universal workflow language, but to make useful operations discoverable and composable.