OpenClaw Mission Control is the centralized operations and governance platform for running OpenClaw across teams and organizations, with unified visibility, approval controls, and gateway-aware orchestration. It gives operators a single interface for work orchestration, agent and gateway management, approval-driven governance, and API-backed automation.
Mission Control is designed to be the day-to-day operations surface for OpenClaw. Instead of splitting work across multiple tools, teams can plan, execute, review, and audit activity in one system.
Core operational areas:
- Work orchestration: manage organizations, board groups, boards, tasks, and tags.
- Agent operations: create, inspect, and manage agent lifecycle from a unified control surface.
- Governance and approvals: route sensitive actions through explicit approval flows.
- Gateway management: connect and operate gateway integrations for distributed environments.
- Activity visibility: review a timeline of system actions for faster debugging and accountability.
- API-first model: support both web workflows and automation clients from the same platform.
- Multi-team agent operations: run multiple boards and board groups across organizations from a single control plane.
- Human-in-the-loop execution: require approvals before sensitive actions and keep decision trails attached to work.
- Distributed runtime control: connect gateways and operate remote execution environments without changing operator workflow.
- Audit and incident review: use activity history to reconstruct what happened, when it happened, and who initiated it.
- API-backed process integration: connect internal workflows and automation clients to the same operational model used in the UI.
- Operations-first design: built for running agent work reliably, not just creating tasks.
- Governance built in: approvals, auth modes, and clear control boundaries are first-class.
- Gateway-aware orchestration: built to operate both local and connected runtime environments.
- Unified UI and API model: operators and automation act on the same objects and lifecycle.
- Team-scale structure: organizations, board groups, boards, tasks, tags, and users in one system of record.
- Platform teams running OpenClaw in self-hosted or internal environments.
- Operations and engineering teams that need clear approval and auditability controls.
- Organizations that want API-accessible operations without losing a usable web UI.
If you haven't cloned the repo yet, you can run the installer in one line:
curl -fsSL https://raw.githubusercontent.com/abhi1693/openclaw-mission-control/master/install.sh | bashIf you already cloned the repo:
./install.shThe installer is interactive and will:
- Ask for deployment mode (
dockerorlocal). - Install missing system dependencies when possible.
- Generate and configure environment files.
- Bootstrap and start the selected deployment mode.
Installer support matrix: docs/installer-support.md
- Docker Engine
- Docker Compose v2 (
docker compose)
cp .env.example .envBefore startup:
- Set
LOCAL_AUTH_TOKENto a non-placeholder value (minimum 50 characters) whenAUTH_MODE=local. - Ensure
NEXT_PUBLIC_API_URLis reachable from your browser.
docker compose -f compose.yml --env-file .env up -d --build- Mission Control UI: http://localhost:3000
- Backend health: http://localhost:8000/healthz
docker compose -f compose.yml --env-file .env downMission Control supports two authentication modes:
local: shared bearer token mode (default for self-hosted use)clerk: Clerk JWT mode
Environment templates:
- Root:
.env.example - Backend:
backend/.env.example - Frontend:
frontend/.env.example
Complete guides for deployment, production, troubleshooting, and testing are in /docs.
Mission Control is under active development.
- Features and APIs may change between releases.
- Validate and harden your configuration before production use.
Issues and pull requests are welcome.
This project is licensed under the MIT License. See LICENSE.