### Manual Setup and Development Start

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

For manual setup, clone the repository, install Node.js version 22, install dependencies with pnpm, and start the development server.

```bash
git clone https://github.com/builderz-labs/mission-control.git
cd mission-control
nvm use 22 && pnpm install
pnpm dev
```

--------------------------------

### Development Quick Start

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Sets up the project for local development by copying the environment file, installing dependencies, and starting the development server.

```bash
cp .env.example .env.local
pnpm install
pnpm dev
```

--------------------------------

### Install, Build, and Start Mission Control (Direct Node)

Source: https://github.com/builderz-labs/mission-control/wiki/Deployment-Runbook

Use this command sequence to install dependencies, build the project, and start Mission Control when running directly as a Node process.

```bash
pnpm install --frozen-lockfile
pnpm build
pnpm start
```

--------------------------------

### Production Build and Start

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Builds the production application and starts the production server using frozen lockfiles for consistent dependency installation.

```bash
pnpm install --frozen-lockfile
pnpm build
pnpm start
```

--------------------------------

### Clone and Start Mission Control

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/LANDING-PAGE-HANDOFF.md

Steps to clone the repository, install dependencies, and start the development server.

```bash
git clone https://github.com/builderz-labs/mission-control.git
cd mission-control
pnpm install
cp .env.example .env    # edit with your values
pnpm dev                # http://localhost:3000
```

--------------------------------

### Install Mission Control Locally

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

Installs Mission Control locally using a setup script. Access the UI at /setup after installation.

```bash
bash install.sh --local
```

--------------------------------

### Install Mission Control via One-Liner

Source: https://github.com/builderz-labs/mission-control/blob/main/skills/mission-control-installer/README.md

Install Mission Control by piping the installer script directly to bash. This is a convenient way to get started quickly.

```bash
curl -fsSL https://raw.githubusercontent.com/builderz-labs/mission-control/main/install.sh | bash
```

--------------------------------

### Install and Build Project

Source: https://github.com/builderz-labs/mission-control/blob/main/CLAUDE.md

Install project dependencies and build the project using pnpm.

```bash
pnpm install
pnpm build
```

--------------------------------

### Clone and Install Dependencies

Source: https://github.com/builderz-labs/mission-control/blob/main/CONTRIBUTING.md

Clone the repository, install dependencies using pnpm, and set up the environment variables.

```bash
git clone https://github.com/builderz-labs/mission-control.git
cd mission-control

pnpm install

cp .env.example .env
# Edit .env with your values

pnpm dev
```

--------------------------------

### Local Installation with pnpm

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

Clone the repository and run the install script with the --local flag for a local installation.

```bash
git clone https://github.com/builderz-labs/mission-control.git
cd mission-control
bash install.sh --local
```

--------------------------------

### Clone and Install Mission Control Locally

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

Clone the repository and run the local installation script. This script handles Node.js, pnpm, dependencies, and generates secure credentials. Access the setup page via the provided URL after installation.

```bash
git clone https://github.com/builderz-labs/mission-control.git
cd mission-control
bash install.sh --local     # or: bash install.sh --docker
```

```bash
open http://localhost:3000/setup    # create your admin account
```

--------------------------------

### Manual Setup for Mission Control

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

Manually set up Mission Control by cloning the repository, installing Node.js version 22+, pnpm, and then running the development server. Access the setup page via the provided URL.

```bash
git clone https://github.com/builderz-labs/mission-control.git
cd mission-control
nvm use 22 && pnpm install
pnpm dev                    # http://localhost:3000/setup
```

--------------------------------

### Docker Installation

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

Use the install script with the --docker flag for a Docker-based installation.

```bash
git clone https://github.com/builderz-labs/mission-control.git
cd mission-control
bash install.sh --docker
```

--------------------------------

### Clone and Run Mission Control Locally

Source: https://github.com/builderz-labs/mission-control/wiki/Getting-Started

Use these commands to clone the repository, install dependencies, set up the environment, and start the development server.

```bash
git clone https://github.com/builderz-labs/mission-control.git
cd mission-control
pnpm install
cp .env.example .env
pnpm dev
```

--------------------------------

### Standalone Production Deployment

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Installs dependencies, builds the application, and starts the standalone server for bare-metal deployments.

```bash
pnpm install --frozen-lockfile
pnpm build
pnpm start:standalone
```

--------------------------------

### Install and Activate SELinux on Ubuntu

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Installs SELinux packages, activates it, and reboots the system. Includes a status check.

```bash
sudo apt update
```

```bash
sudo apt install selinux-basics selinux-policy-default
```

```bash
sudo selinux-activate
```

```bash
sudo reboot
```

```bash
sudo apt install policycoreutils; sestatus
```

--------------------------------

### Start Mission Control Application

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/SCREENSHOT-GUIDE.md

Use these commands to start the Mission Control application locally. Choose the command that suits your development environment.

```bash
pnpm dev
```

```bash
docker compose up
```

--------------------------------

### Mode Override Examples

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Demonstrates how to use mode overrides with Make commands to target specific environments or components.

```bash
make restart dev
make restart mc dev
make status openclaw
make upgrade prod
```

--------------------------------

### Docker Compose Zero-Configuration Setup

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

Run 'docker compose up' for a zero-configuration Docker setup that automatically generates credentials and persists data across restarts.

```bash
docker compose up
```

--------------------------------

### Install Ubuntu/Debian Build Tools

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Installs Python, make, and g++ required for native compilation of packages like better-sqlite3 on Ubuntu/Debian systems.

```bash
sudo apt-get update
sudo apt-get install -y python3 make g++
```

--------------------------------

### Docker Zero-Configuration Setup

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

Run Mission Control using Docker Compose for a zero-configuration setup. Credentials are auto-generated and persisted across restarts.

```bash
docker compose up           # auto-generates credentials, persists across restarts
```

--------------------------------

### Install and Configure Automatic Security Updates

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Sets up unattended-upgrades to automatically install security patches.

```bash
sudo apt-get install -y unattended-upgrades && sudo dpkg-reconfigure -plow unattended-upgrades && sudo unattended-upgrade -d
```

--------------------------------

### Install macOS Build Tools

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Installs Xcode command line tools necessary for native compilation on macOS.

```bash
xcode-select --install
```

--------------------------------

### Run Mission Control Installer Script

Source: https://github.com/builderz-labs/mission-control/blob/main/skills/mission-control-installer/README.md

Execute the installer script with various options to customize the deployment mode, port, or skip specific checks.

```bash
# Auto-detect deployment mode (prefers Docker)
bash install.sh
```

```bash
# Force Docker deployment
bash install.sh --docker
```

```bash
# Force local deployment (Node.js + pnpm)
bash install.sh --local
```

```bash
# Custom port
bash install.sh --port 8080
```

```bash
# Skip OpenClaw fleet check
bash install.sh --skip-openclaw
```

--------------------------------

### Start Production Server with Custom Port

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Starts the production server, overriding the default port with a custom one using the PORT environment variable.

```bash
PORT=3000 pnpm start
```

--------------------------------

### Development Server Command

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

Starts the development server for Mission Control.

```bash
pnpm dev
```

--------------------------------

### Install Fail2ban for Brute-Force Protection

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Installs fail2ban to protect against brute-force attacks. Configuration is done in `/etc/fail2ban/jail.local`.

```bash
sudo apt-get install -y fail2ban && sudo systemctl enable --now fail2ban
```

--------------------------------

### List Agents GET Request Query Parameters

Source: https://github.com/builderz-labs/mission-control/blob/main/SKILL.md

When listing agents via GET /api/agents, you can use query parameters to filter and paginate results. Example parameters include status, role, limit, and offset.

```json
{ "agents": [{ "id": 1, "name": "scout", "role": "researcher", "status": "online", "config": {}, "taskStats": { "total": 10, "assigned": 2, "in_progress": 1, "completed": 7 } }], "total": 1, "page": 1, "limit": 50 }
```

--------------------------------

### Start Mission Control

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/quickstart.md

Run Mission Control locally using pnpm. Access the UI at http://localhost:3000 and set up your admin account if it's the first run.

```bash
pnpm dev
```

--------------------------------

### Recommended .env for Standard Install

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Use these environment variables for a standard Mission Control installation. Using an absolute path for MISSION_CONTROL_DATA_DIR ensures data persistence across rebuilds.

```env
OPENCLAW_STATE_DIR=/root/.openclaw
MISSION_CONTROL_DATA_DIR=/absolute/path/to/.data
```

--------------------------------

### CLI Agent Control Commands

Source: https://github.com/builderz-labs/mission-control/blob/main/CLAUDE.md

Example commands for interacting with Mission Control agents, tasks, and events via the CLI.

```bash
pnpm mc agents list --json
pnpm mc tasks queue --agent Aegis --max-capacity 2 --json
pnpm mc events watch --types agent,task
```

--------------------------------

### Configure Firewall with UFW

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Installs and enables the Uncomplicated Firewall (ufw), allowing SSH traffic.

```bash
sudo apt-get install -y ufw && sudo ufw allow OpenSSH && sudo ufw enable && sudo ufw status
```

--------------------------------

### Start Mission Control on a Custom Port (Direct Node)

Source: https://github.com/builderz-labs/mission-control/wiki/Deployment-Runbook

Override the default port (3005) by setting the PORT environment variable before starting Mission Control.

```bash
PORT=3000 pnpm start
```

--------------------------------

### Create Agent-Scoped API Key

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/SECURITY-HARDENING.md

Example command to create a new API key for an agent with limited scopes, adhering to the principle of least privilege. This is a placeholder for the actual command, as the specific command was not provided in the text.

```bash
# Example: Create agent-scoped key (actual command not provided in source)
# openclaw create-api-key --agent-id <agent-id> --scopes "read:tasks,execute:tools"
```

--------------------------------

### Get Mission Control System Overview

Source: https://github.com/builderz-labs/mission-control/blob/main/skills/mission-control-manage/README.md

Retrieve a full system status report, including memory, disk, sessions, and processes.

```bash
# Full system status (memory, disk, sessions, processes)
curl -H "x-api-key: $API_KEY" http://localhost:3000/api/status?action=overview
```

--------------------------------

### Run Mission Control CLI Commands

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/cli-agent-control.md

Examples of common Mission Control CLI commands for listing agents, queuing tasks, and controlling sessions. Ensure API URL and key are set via environment variables or profile flags.

```bash
node scripts/mc-cli.cjs agents list --json
```

```bash
node scripts/mc-cli.cjs tasks queue --agent Aegis --max-capacity 2 --json
```

```bash
node scripts/mc-cli.cjs sessions control --id <session-id> --action terminate
```

--------------------------------

### Docker Compose Commands

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Use these commands to start Mission Control with Docker Compose. Choose the appropriate command based on whether gateway connectivity is required.

```bash
docker compose up          # with gateway connectivity
docker compose --profile standalone up   # without gateway (standalone mode)
```

--------------------------------

### Install Build Dependencies on Ubuntu/Debian

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

If 'Module not found: better-sqlite3' occurs, native compilation may have failed. Install necessary build tools like python3, make, and g++ on Ubuntu/Debian systems.

```bash
sudo apt-get install -y python3 make g++
rm -rf node_modules
pnpm install
```

--------------------------------

### Docker Compose Basic Commands

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Provides essential Docker Compose commands for managing Mission Control services, including starting, restarting, and stopping containers, and checking status.

```bash
# 1) choose mode in .env
#    MC_MODE=prod   # or dev
#    OPENCLAW_ENABLED=1   # set 0 to run MC without OpenClaw stack

# 2) run universal verbs
make up
make restart
make down
make status
```

--------------------------------

### Reviewer Agent SOUL Example

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/agent-setup.md

Example SOUL.md defining a quality reviewer agent. Outlines its role and specific review criteria for completed tasks.

```markdown
# Aegis — Quality Reviewer

You are Aegis, the quality gate for all agent work in Mission Control.

## Role
Review completed tasks for correctness, completeness, and quality.

## Review Criteria
- Does the output address all parts of the task?
- Are there factual errors or hallucinations?
- Is the work actionable and well-structured?
```

--------------------------------

### Run Mission Control in Gateway Optional Mode

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

Starts Mission Control with the gateway optional mode enabled, allowing standalone operation without a gateway connection.

```bash
NEXT_PUBLIC_GATEWAY_OPTIONAL=true pnpm start
```

--------------------------------

### Basic Workflow Steps

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/LANDING-PAGE-HANDOFF.md

Illustrates the typical steps involved in using Mission Control, from cloning to monitoring.

```text
1. Clone & Start       git clone ... && pnpm install && pnpm dev
2. Agents Register     Via gateway, CLI, or self-registration endpoint
3. Tasks Flow          Kanban board with automatic dispatch and quality gates
4. Monitor & Scale     Real-time dashboards, cost tracking, recurring automation
```

--------------------------------

### Make Command Grammar

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Illustrates the command structure for Make, allowing for verb, scope, and mode overrides for targeted operations.

```text
make <verb> [all|mc|openclaw] [dev|prod]
```

--------------------------------

### Create Mission Control Database Backup

Source: https://github.com/builderz-labs/mission-control/blob/main/skills/mission-control-manage/README.md

Initiate a backup of the Mission Control database.

```bash
curl -X POST -H "x-api-key: $API_KEY" http://localhost:3000/api/backup
```

--------------------------------

### Trigger Update API

Source: https://github.com/builderz-labs/mission-control/blob/main/skills/mission-control-manage/README.md

Applies an available update to Mission Control. This endpoint is intended for bare-metal installations; Docker installations will receive instructions on how to update.

```APIDOC
## POST /api/releases/update

### Description
Applies an available update to Mission Control. This endpoint is intended for bare-metal installations; Docker installations will receive instructions on how to update.

### Method
POST

### Endpoint
/api/releases/update

### Response
#### Success Response (200)
- (No specific response fields mentioned, typically indicates success or provides update instructions for Docker.)
```

--------------------------------

### Create Agent with Template

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/agent-setup.md

This command demonstrates creating a new agent and applying a predefined template during creation. The 'developer' template provides a default configuration for coding tasks.

```bash
curl -X POST http://localhost:3000/api/agents \
  -H "Authorization: Bearer $MC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "scout", "role": "coder", "template": "developer"}'
```

--------------------------------

### Trigger Mission Control Update

Source: https://github.com/builderz-labs/mission-control/blob/main/skills/mission-control-manage/README.md

Apply an available update to Mission Control. This endpoint is for bare-metal installations; Docker installations will return instructions instead.

```bash
# Apply available update (bare-metal only; Docker returns instructions)
curl -X POST -H "x-api-key: $API_KEY" http://localhost:3000/api/releases/update
```

--------------------------------

### Developer Agent SOUL Example

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/agent-setup.md

Example SOUL.md defining a senior developer agent. Specifies expertise in full-stack TypeScript, approach to coding, and constraints.

```markdown
# Scout — Developer

You are Scout, a senior developer agent specializing in full-stack TypeScript development.

## Expertise
- Next.js, React, Node.js
- Database design (PostgreSQL, SQLite)
- API architecture and testing

## Approach
- Read existing code before proposing changes
- Write tests alongside implementation
- Keep changes minimal and focused

## Constraints
- Never commit secrets or credentials
- Ask for clarification on ambiguous requirements
- Flag security concerns immediately
```

--------------------------------

### Production Build Command

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

Builds the production-ready version of Mission Control.

```bash
pnpm build
```

--------------------------------

### Researcher Agent SOUL Example

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/agent-setup.md

Example SOUL.md defining a research agent. Details expertise in web research, data synthesis, and specifies output format requirements.

```markdown
# Iris — Researcher

You are Iris, a research agent focused on gathering and synthesizing information.

## Expertise
- Web research and source verification
- Competitive analysis
- Data synthesis and report writing

## Approach
- Always cite sources with URLs
- Present findings in structured format
- Distinguish facts from inferences

## Output Format
- Use bullet points for key findings
- Include a "Sources" section at the end
- Highlight actionable insights
```

--------------------------------

### Create and Mount LUKS Encrypted Volume

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/deployment.md

Formats a device with LUKS, opens it, creates a filesystem, and mounts it for secure data storage.

```bash
sudo cryptsetup luksFormat /dev/sdX && sudo cryptsetup open /dev/sdX mc-data && sudo mkfs.ext4 /dev/mapper/mc-data
```

--------------------------------

### Station Doctor Script

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

Executes a script to check the installation health of the station.

```bash
bash scripts/station-doctor.sh
```

--------------------------------

### Run Unit Tests

Source: https://github.com/builderz-labs/mission-control/blob/main/CONTRIBUTING.md

Execute unit tests using Vitest.

```bash
pnpm test
```

--------------------------------

### GET /api/connect - List Connections

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/cli-integration.md

Lists all active connections to Mission Control.

```APIDOC
## GET /api/connect

### Description
Lists all active connections to Mission Control.

### Method
GET

### Endpoint
/api/connect

### Parameters
None

### Response
#### Success Response (200)
- Returns a list of connection objects. (Specific fields not detailed in source text)

#### Response Example
(Example not provided in source text)
```

--------------------------------

### Create Implementation Task for Handoff

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/orchestration.md

Following the research task, create a new task for the 'scout' agent to implement the findings. This task includes a description referencing the previous research task.

```bash
# Step 2: Implementation task for scout (after iris finishes)
curl -X POST "$MC_URL/api/tasks" \
  -H "Authorization: Bearer $MC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ 
    "title": "Implement Redis caching for /api/products",
    "description": "Based on research in TASK-1: Use cache-aside pattern with 5min TTL...",
    "priority": "high",
    "assigned_to": "scout"
  }'
```

--------------------------------

### Fetch Assignments Response

Source: https://github.com/builderz-labs/mission-control/blob/main/SKILL.md

This is an example of the JSON response when fetching assignments. It includes a list of tasks, each with an ID, description, and priority.

```json
{
  "assignments": [
    { "taskId": "42", "description": "Fix login bug\nUsers cannot log in with SSO", "priority": 1 }
  ],
  "framework": "generic"
}
```

--------------------------------

### Run Tests

Source: https://github.com/builderz-labs/mission-control/blob/main/CLAUDE.md

Commands for running various tests and checks for the project.

```bash
pnpm test             # unit tests (vitest)
pnpm test:e2e         # end-to-end (playwright)
pnpm typecheck        # tsc --noEmit
pnpm lint             # eslint
pnpm test:all         # lint + typecheck + test + build + e2e
```

--------------------------------

### SVG Icon Component

Source: https://github.com/builderz-labs/mission-control/blob/main/wiki/STYLE_GUIDE.md

Example of an SVG icon component using Tailwind CSS classes for sizing and styling. Ensure stroke properties are set for scalability.

```tsx
<svg viewBox="0 0 16 16" fill="none" stroke="currentColor"
  strokeWidth="1.5" strokeLinecap="round" strokeLinejoin="round"
  className="w-5 h-5">
  <circle cx="8" cy="8" r="6" />
</svg>
```

--------------------------------

### Sync Agents from Local Discovery

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/agent-setup.md

Synchronize agents by scanning standard directories for agent definitions. Agent directories are detected by marker files.

```bash
curl -X POST http://localhost:3000/api/agents/sync \
  -H "Authorization: Bearer $MC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"source": "local"}'
```

--------------------------------

### Configure Agent Dispatch Model

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/orchestration.md

Override the default model routing for an agent by setting `config.dispatchModel`. This example sets the agent to use a specific Opus model.

```bash
curl -X PUT "$MC_URL/api/agents" \
  -H "Authorization: Bearer $MC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"id": 1, "config": {"dispatchModel": "9router/cc/claude-opus-4-6"}}'
```

--------------------------------

### System Overview API

Source: https://github.com/builderz-labs/mission-control/blob/main/skills/mission-control-manage/README.md

Fetches a comprehensive overview of the system status, including memory, disk usage, active sessions, and running processes.

```APIDOC
## GET /api/status?action=overview

### Description
Fetches a comprehensive overview of the system status, including memory, disk usage, active sessions, and running processes.

### Method
GET

### Endpoint
/api/status?action=overview

### Query Parameters
- **action** (string) - Required - Must be 'overview'

### Response
#### Success Response (200)
- **memory** (object) - Memory usage details.
- **disk** (object) - Disk usage details.
- **sessions** (object) - Active session information.
- **processes** (object) - Information about running processes.
```

--------------------------------

### Configure Mission Control URL and API Key

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

Sets environment variables for the Mission Control URL and API key, required for agent and task registration.

```bash
export MC_URL=http://localhost:3000
export MC_API_KEY=your-api-key   # shown in Settings after first login
```

--------------------------------

### Run Quality Gate

Source: https://github.com/builderz-labs/mission-control/blob/main/CONTRIBUTING.md

Execute the quality gate command to lint, typecheck, test, run end-to-end tests, and build the project.

```bash
pnpm quality:gate  # lint + typecheck + test + e2e + build
```

--------------------------------

### Update Agent Configuration

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/agent-setup.md

Use this command to update specific fields in an agent's configuration. This example shows how to change the dispatch model for agent ID 1.

```bash
curl -X PUT http://localhost:3000/api/agents \
  -H "Authorization: Bearer $MC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "id": 1,
    "config": {
      "dispatchModel": "9router/cc/claude-opus-4-6"
    }
  }'
```

--------------------------------

### GET /api/events - SSE Event Stream

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/cli-integration.md

Subscribes to a Server-Sent Events (SSE) stream to receive real-time events such as task assignments, mentions, and agent status changes.

```APIDOC
## GET /api/events

### Description
Subscribes to a Server-Sent Events (SSE) stream to receive real-time events such as task assignments, mentions, and agent status changes.

### Method
GET

### Endpoint
/api/events

### Parameters
None

### Response
#### Success Response (200)
- Returns a stream of events.

#### Response Example
(Example not provided in source text)
```

--------------------------------

### Adapters API

Source: https://github.com/builderz-labs/mission-control/blob/main/SKILL.md

Endpoints for listing and executing framework adapter actions.

```APIDOC
## GET /api/adapters

### Description
List the names of available framework adapters.

### Method
GET

### Endpoint
/api/adapters

### Response
#### Success Response (200)
- **adapters** (array of strings) - A list of available adapter names.

#### Response Example
["generic", "openclaw", "crewai", "langgraph", "autogen", "claude-sdk"]

## POST /api/adapters

### Description
Execute an action on a specified framework adapter. This endpoint is used for all agent lifecycle operations.

### Method
POST

### Endpoint
/api/adapters

### Headers
- **Content-Type**: `application/json`
- **x-api-key**: `<your_api_key>`

### Request Body
- **framework** (string) - Required - The name of the adapter framework to use. Allowed values: `generic`, `openclaw`, `crewai`, `langgraph`, `autogen`, `claude-sdk`.
- **action** (string) - Required - The action to perform on the adapter. Allowed values: `register`, `heartbeat`, `report`, `assignments`, `disconnect`.
- **payload** (object) - Required - The data payload for the action. The shape of the payload depends on the `action`.

#### Payload Shapes by Action:

- **`register`**
  - **agentId** (string) - Required - The unique ID of the agent.
  - **name** (string) - Required - The name of the agent.
  - **metadata** (object) - Optional - Additional metadata for the agent.

- **`heartbeat`**
  - **agentId** (string) - Required - The unique ID of the agent.
  - **status** (string) - Optional - The current status of the agent.
  - **metrics** (object) - Optional - Performance metrics for the agent.

- **`report`**
  - **taskId** (string) - Required - The ID of the task being reported on.
  - **agentId** (string) - Required - The unique ID of the agent reporting.
  - **progress** (number) - Optional - The progress of the task (0-100).
  - **status** (string) - Optional - The status of the task execution.
  - **output** (string) - Optional - The output or result of the task.

- **`assignments`**
  - **agentId** (string) - Required - The unique ID of the agent.

- **`disconnect`**
  - **agentId** (string) - Required - The unique ID of the agent.

### Request Example (Registering an agent)
```json
{
  "framework": "autogen",
  "action": "register",
  "payload": {
    "agentId": "agent-123",
    "name": "Code Assistant",
    "metadata": {
      "version": "1.0"
    }
  }
}
```

### Response
#### Success Response (200)
- The response structure varies based on the `action` performed. Typically includes a confirmation message or relevant data.

#### Response Example (for `register` action)
{
  "message": "Agent registered successfully."
}
```

--------------------------------

### Get Mission Control Health Status

Source: https://github.com/builderz-labs/mission-control/blob/main/skills/mission-control-manage/README.md

Use this endpoint for a quick health status of the Mission Control instance. Possible statuses include 'healthy', 'degraded', and 'unhealthy'.

```bash
# Quick health status
curl -H "x-api-key: $API_KEY" http://localhost:3000/api/status?action=health

# Response: { "status": "healthy", "version": "1.3.0", "checks": [...] }
```

--------------------------------

### Watch Task and Agent Events via CLI

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/orchestration.md

Use the Mission Control CLI to stream task and agent events in JSON format. Ensure you have the CLI installed and configured.

```bash
node scripts/mc-cli.cjs events watch --types task,agent --json
```

--------------------------------

### Framework Adapter Protocol

Source: https://github.com/builderz-labs/mission-control/blob/main/SKILL.md

This is the standard structure for interacting with framework adapters. Specify the `framework`, `action`, and relevant `payload`.

```http
POST /api/adapters
Content-Type: application/json
x-api-key: <key>

{
  "framework": "<adapter-name>",
  "action": "<action>",
  "payload": { ... }
}
```

--------------------------------

### Create and Push Git Tag

Source: https://github.com/builderz-labs/mission-control/blob/main/RELEASE.md

Use this command to create an annotated Git tag for a release and push it to the origin. Ensure you are on the main branch and have the latest changes.

```bash
git checkout main
git pull --ff-only origin main
git tag -a vX.Y.Z -m "release: vX.Y.Z"
git push origin vX.Y.Z
```

--------------------------------

### Run OpenClaw Offline Harness

Source: https://github.com/builderz-labs/mission-control/blob/main/tests/README.md

Execute end-to-end tests using the OpenClaw offline harness. This mode does not require a full OpenClaw installation and uses fixture data and mock binaries.

```bash
pnpm test:e2e:openclaw
```

--------------------------------

### Fix better-sqlite3 Build Failure

Source: https://github.com/builderz-labs/mission-control/wiki/Troubleshooting

Run these commands to resolve missing module or native compile errors with better-sqlite3. This involves installing build tools, cleaning the node_modules directory, and reinstalling dependencies.

```bash
sudo apt-get install -y python3 make g++
rm -rf node_modules
pnpm install
```

--------------------------------

### Docker Deployment

Source: https://github.com/builderz-labs/mission-control/blob/main/CLAUDE.md

Commands for deploying Mission Control using Docker Compose.

```bash
docker compose up                 # zero-config
bash install.sh --docker          # full guided setup

Production hardening: docker compose -f docker-compose.yml -f docker-compose.hardened.yml up -d
```

--------------------------------

### Create Task API Response

Source: https://github.com/builderz-labs/mission-control/blob/main/SKILL.md

Example JSON response after successfully creating a task. It includes the task's ID, title, status, priority, assignee, ticket reference, tags, and metadata.

```json
{
  "task": {
    "id": 42, "title": "Fix login bug", "status": "assigned",
    "priority": "high", "assigned_to": "scout", "ticket_ref": "GEN-001",
    "tags": ["bug"], "metadata": {}
  }
}
```

--------------------------------

### Quality Gate Command

Source: https://github.com/builderz-labs/mission-control/blob/main/README.md

Runs all quality checks, including linting and tests.

```bash
pnpm quality:gate
```

--------------------------------

### Register Connection Response

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/cli-integration.md

This is a sample response upon successful registration of a CLI connection. It provides details like connection ID, agent information, and URLs for events and heartbeats.

```json
{
  "connection_id": "550e8400-e29b-41d4-a716-446655440000",
  "agent_id": 42,
  "agent_name": "my-agent",
  "status": "connected",
  "sse_url": "/api/events",
  "heartbeat_url": "/api/agents/42/heartbeat",
  "token_report_url": "/api/tokens"
}
```

--------------------------------

### Complete a Task in Mission Control

Source: https://github.com/builderz-labs/mission-control/blob/main/docs/quickstart.md

Update a task's status and provide a resolution by sending a PUT request to the /api/tasks/{id} endpoint. The example shows marking a task as 'done' with a detailed resolution.

```bash
curl -s -X PUT "$MC_URL/api/tasks/1" \
  -H "Authorization: Bearer $MC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "status": "done",
    "resolution": "Found pricing for Acme ($29/49/99), Widget Corp ($19/39/79), and Gadget Inc ($25/50/100). All use 3-tier SaaS model. Summary doc attached."
  }' | jq
```