openclaw-mission-control

What it is

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.

How it works

Mission Control provides core operational areas including work orchestration (organizations, board groups, boards, tasks, tags), agent operations (agent lifecycle management), governance and approvals (approval flows), gateway management (connect and operate gateway integrations), and activity visibility (timeline of actions). It supports an API-first model to service both web workflows and automation clients from the same platform.

Getting started

Option A: One-command production-style bootstrap

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 | bash

This clones the repository into ./openclaw-mission-control if no local checkout is found in your current directory.

If you already cloned the repo:

./install.sh

The installer is interactive and will:

• Ask for deployment mode (docker or local).
• 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

Option B: Manual setup

Prerequisites

• Supported platforms: Linux and macOS. On macOS, Docker mode requires Docker Desktop; local mode requires Homebrew and Node.js 22+.
• Docker Engine
• Docker Compose v2 (docker compose)

1. Configure environment

cp .env.example .env

Before startup:

• Set LOCAL_AUTH_TOKEN to a non-placeholder value (minimum 50 characters) when AUTH_MODE=local.
• Ensure BASE_URL matches the public backend origin if you are not using http://localhost:8000.
• NEXT_PUBLIC_API_URL=auto (default) resolves to http(s)://<current-host>:8000.
  • Set an explicit URL when your API is behind a reverse proxy or non-default port.

2. Start Mission Control

docker compose -f compose.yml --env-file .env up -d --build

If you are iterating on the UI in Docker and want automatic frontend rebuilds on source changes, run:

docker compose -f compose.yml --env-file .env up --build --watch

Notes:

• Compose Watch requires Docker Compose 2.22.0+.
• You can also run watch separately after startup:

docker compose -f compose.yml --env-file .env up -d --build
docker compose -f compose.yml --env-file .env watch

After pulling new changes, rebuild and recreate all services:

docker compose -f compose.yml --env-file .env up -d --build --force-recreate

For a fully clean rebuild (no cached build layers):

docker compose -f compose.yml --env-file .env build --no-cache --pull
docker compose -f compose.yml --env-file .env up -d --force-recreate

3. Open the application

• Mission Control UI: http://localhost:3000
• Backend health: http://localhost:8000/healthz

4. Stop the stack

docker compose -f compose.yml --env-file .env down

Authentication

Mission 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

Documentation

Complete guides for deployment, production, troubleshooting, and testing are in /docs.

Project status

Mission Control is under active development.

• Features and APIs may change between releases.
• Validate and harden your configuration before production use.

Contributing

Issues and pull requests are welcome.

• Contributing guide
• Open issues

License

This project is licensed under the MIT License. See LICENSE.

Star History