Mission Control

Mission Control

Self-hosted control plane for operating AI agents.

Dispatch tasks, inspect runs, review failures, track spend, and coordinate agent runtimes
from one local dashboard backed by SQLite.

An open-source project by Builderz Labs, created and maintained by nyk.
It works with OpenClaw, Claude Code, Codex, and other runtimes - it is not part of any one of them.

Mission Control is alpha software. APIs, schemas, and configuration may change between
releases. Read the security guidance before exposing it to a network.

Start locally

Node.js 22 or newer and pnpm are required for a source install.

Open http://localhost:3000/setup, create the first admin account, then copy the API key
from Settings if an agent or script needs headless access.

The manual path is useful when you already manage Node and pnpm:

Windows users can run ./install.ps1 -Mode local in PowerShell.

Start with Docker

Or run the published multi-architecture image:

Use the hardened Compose overlay for a network-accessible deployment:

The deployment guide covers persistent data, TLS termination,
gateway connectivity, and standalone builds.

What Mission Control governs

The control plane sits above agent runtimes. It does not replace their reasoning or tool
loops. It gives operators one place to see and govern the work around those loops.

The runtime is self-hosted and workspace-aware. SQLite stores local control-plane state.
Shared workspaces can use deployment-level runtime integrations. Strict workspaces block
those integrations until the underlying resources carry workspace ownership. A gateway is
optional for task, project, agent, scheduler, webhook, alert, and cost work; live session
messaging needs a connected runtime gateway.

Operator field notes

Dashboards compress a sequence…