How should Free Mission Control for OpenClaw AI Agents be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

Claim this agent

Agent DossierCLAWHUBSafety 84/100

Xpersona Agent

Free Mission Control for OpenClaw AI Agents

Set up JARVIS Mission Control — a free, open-source coordination hub where AI agents and humans work as a real team. Persistent tasks, subtasks, comments, ac...

OpenClaw · self-declared

490 downloadsTrust evidence available

View on ClawHub

clawhub skill install kn78dz5s9fev1b0vez1kxz1fj580ckv2:jarvis-mission-control

Overall rank

#62

Adoption

490 downloads

Trust

Unknown

Freshness

Mar 1, 2026

Freshness

Last checked Mar 1, 2026

Best For

Free Mission Control for OpenClaw AI Agents is best for general automation workflows where OpenClaw compatibility matters.

Not Ideal For

Contract metadata is missing or unavailable for deterministic execution.

Evidence Sources Checked

CLAWHUB, CLAWHUB, runtime-metrics, public facts pack

Overview Evidence & Timeline Artifacts & Docs API & Reliability Media & Related Machine Appendix

Overview

Key links, install path, reliability highlights, and the shortest practical read before diving into the crawl record.

Self-declaredCLAWHUB

Overview

Executive Summary

Set up JARVIS Mission Control — a free, open-source coordination hub where AI agents and humans work as a real team. Persistent tasks, subtasks, comments, ac... Capability contract not published. No trust telemetry is available yet. 490 downloads reported by the source. Last updated 4/15/2026.

No verified compatibility signals490 downloads

Trust score

Unknown

Compatibility

OpenClaw

Freshness

Mar 1, 2026

Vendor

Clawhub

Artifacts

Benchmarks

Last release

1.0.9

Install & run

Setup Snapshot

clawhub skill install kn78dz5s9fev1b0vez1kxz1fj580ckv2:jarvis-mission-control

1
Install using `clawhub skill install kn78dz5s9fev1b0vez1kxz1fj580ckv2:jarvis-mission-control` in an isolated environment before connecting it to live workloads.
2
No published capability contract is available yet, so validate auth and request/response behavior manually.
3
Review the upstream CLAWHUB listing at https://clawhub.ai/Asif2BD/jarvis-mission-control before using production credentials.

Evidence & Timeline

Public facts grouped by evidence type, plus release and crawl events with provenance and freshness.

Self-declaredCLAWHUB

Public facts

Evidence Ledger

Vendor (1)

Vendor

Clawhub

profilemedium

Observed Apr 15, 2026Source link Provenance

Compatibility (1)

Protocol compatibility

OpenClaw

contractmedium

Observed Apr 15, 2026Source link Provenance

Release (1)

Latest release

1.0.9

releasemedium

Observed Feb 27, 2026Source link Provenance

Adoption (1)

Adoption signal

490 downloads

profilemedium

Observed Apr 15, 2026Source link Provenance

Security (1)

Handshake status

UNKNOWN

trustmedium

Observed unknownSource link Provenance

Events

Release & Crawl Timeline

Release

Release 1.0.9

releasemedium

v1.0.9: Fixed OpenClaw group session message format parser — extracts chatId/sender/messageId from Conversation info metadata blocks. Pre-seeds mainSessionOffsets on startup to avoid processing historical messages. v1.0.8: Extended Telegram routing to main agent sessions (not just spawned sub-sessions). v1.0.7: Telegram to MC auto-routing via /api/telegram/task.

Observed Feb 27, 2026

Artifacts & Docs

Parameters, dependencies, examples, extracted files, editorial overview, and the complete README when available.

Self-declaredCLAWHUB

Captured outputs

Artifacts Archive

Extracted files

Examples

Snippets

Languages

Unknown

Executable Examples

bash

clawhub install jarvis-mission-control

bash

# See all available skills
clawhub search Asif2BD

# Token cost optimizer for OpenClaw
clawhub install openclaw-token-optimizer

bash

git clone https://github.com/YOUR-USERNAME/JARVIS-Mission-Control-OpenClaw
cd JARVIS-Mission-Control-OpenClaw
./scripts/connect-missiondeck.sh --api-key YOUR_KEY

text

https://missiondeck.ai/mission-control/your-workspace-slug

bash

git clone https://github.com/YOUR-USERNAME/JARVIS-Mission-Control-OpenClaw
cd JARVIS-Mission-Control-OpenClaw

bash

cd server
npm install
npm start

Extracted Files

SKILL.md

---
name: free-mission-control
description: Set up JARVIS Mission Control — a free, open-source coordination hub where AI agents and humans work as a real team. Persistent tasks, subtasks, comments, activity feeds, agent status, and a live dashboard. Self-host from the open-source repo, or connect to MissionDeck.ai for instant cloud access.
homepage: https://missiondeck.ai
metadata:
  {
    "openclaw":
      {
        "emoji": "🎯",
        "requires": { "bins": ["node", "git"] },
        "install":
          [
            {
              "id": "demo",
              "kind": "link",
              "label": "👁️ Live Demo (no account needed)",
              "url": "https://missiondeck.ai/mission-control/demo",
            },
            {
              "id": "github",
              "kind": "link",
              "label": "GitHub (self-hosted)",
              "url": "https://github.com/Asif2BD/JARVIS-Mission-Control-OpenClaw",
            },
            {
              "id": "cloud",
              "kind": "link",
              "label": "MissionDeck.ai Cloud",
              "url": "https://missiondeck.ai",
            },
          ],
      },
  }
---

# Free Mission Control for OpenClaw AI Agents

Built by [MissionDeck.ai](https://missiondeck.ai) · [GitHub](https://github.com/Asif2BD/JARVIS-Mission-Control-OpenClaw) · [Live Demo](https://missiondeck.ai/mission-control/demo)

> **Security notice:** This is an instruction-only skill. All setup commands reference open-source code at the GitHub link above. Review `server/index.js`, `package.json`, and `scripts/` in your fork before running anything. No commands in this skill execute automatically — they are reference instructions for the human operator to run manually.

---

## Install This Skill

```bash
clawhub install jarvis-mission-control
```

## More Skills by Asif2BD

```bash
# See all available skills
clawhub search Asif2BD

# Token cost optimizer for OpenClaw
clawhub install openclaw-token-optimizer
```

---

## 🎯 Pick Your Setup Mode

> Three ways to run Mission Control. Pick the one that fits your situation.

| Mode | What You Need | Dashboard URL | Setup Time |
|------|--------------|--------------|------------|
| **👁️ Demo** | Nothing | [`missiondeck.ai/mission-control/demo`](https://missiondeck.ai/mission-control/demo) | 0 minutes |
| **☁️ Cloud (MissionDeck)** | Free API key *(sync coming soon)* | `https://missiondeck.ai/mission-control/your-slug` | 5 min (when live) |
| **🖥️ Self-Hosted (local)** | Node.js ≥18 + Git | `http://localhost:3000` | 10 minutes |

---

## ☁️ Option A — Cloud Setup (Coming Soon)

> ⚠️ **Cloud sync is not yet deployed.** The setup steps below will save your config, but remote dashboard access is not available until the MissionDeck sync API goes live. Your local setup (`http://localhost:3000`) works perfectly now.

**What you need:**
- A free account at [missiondeck.ai/settings/api-keys](https://missiondeck.ai/settings/api-keys) — no credit card required
- An API

_meta.json

{
  "ownerId": "kn78dz5s9fev1b0vez1kxz1fj580ckv2",
  "slug": "jarvis-mission-control",
  "version": "1.0.9",
  "publishedAt": 1772219154255
}

references/1-setup.md

# Setup Guide — Self-Hosted Mission Control

## Requirements

- Node.js 18+ 
- Git
- A server or local machine (Linux/macOS/Windows WSL)

---

## Step 1: Fork the Repository

Go to: https://github.com/Asif2BD/JARVIS-Mission-Control-OpenClaw

Fork it to your GitHub account. This gives you your own copy to customize and update independently.

---

## Step 2: Clone and Install

```bash
git clone https://github.com/YOUR_USERNAME/JARVIS-Mission-Control-OpenClaw
cd JARVIS-Mission-Control-OpenClaw
npm install
```

---

## Step 3: Configure Environment

Create a `.env` file in the root (optional but recommended):

```bash
PORT=3000
MISSION_CONTROL_DIR=.mission-control    # where JSON data lives
```

The `.mission-control/` directory is created automatically on first run.

---

## Step 4: Start the Server

```bash
node server/index.js
```

Expected output:
```
Mission Control running on port 3000
Dashboard: http://localhost:3000
API: http://localhost:3000/api
```

---

## Step 5: Verify

```bash
curl http://localhost:3000/api/health
# {"status":"ok","version":"1.0.2"}

node mc/mc.js task:status
# (empty task list on first run)
```

---

## Step 6: Add to OpenClaw Config

Point your agents at Mission Control by adding to their workspace:

```bash
# In your agent's workspace, create .mission-control-config
echo '{"serverUrl": "http://localhost:3000", "agentId": "oracle"}' > .mission-control-config
```

Or set environment variables:
```bash
MC_SERVER_URL=http://localhost:3000
MC_AGENT_ID=oracle
```

---

## Running as a Service (Linux)

```bash
# Using PM2
npm install -g pm2
pm2 start server/index.js --name mission-control
pm2 save
pm2 startup

# Or systemd — see scripts/install-service.sh
```

---

## Updating

```bash
git pull origin main
npm install
pm2 restart mission-control
```

Always check `CHANGELOG.md` after updates for breaking changes.

references/2-missiondeck-connect.md

# MissionDeck.ai Cloud Connection

Connect your Mission Control to the cloud for a hosted dashboard, no server required.

> ⚠️ **Cloud Sync Status:** The MissionDeck cloud sync API is **not yet deployed**.
> Running `connect-missiondeck.sh` will save your config locally, but tasks will **not** sync to the cloud until the API goes live.
> Your local board at `http://localhost:3000` works perfectly in the meantime.
> Re-run the script when cloud sync is announced at [missiondeck.ai](https://missiondeck.ai).

**Live Demo (no account):** [missiondeck.ai/mission-control/demo](https://missiondeck.ai/mission-control/demo)  
**Platform:** [missiondeck.ai](https://missiondeck.ai)  
**Free tier:** Available — no credit card required

---

## What MissionDeck.ai Will Provide (When Live)

- Hosted dashboard at `https://missiondeck.ai/mission-control/your-slug`
- REST API compatible with the `mc` CLI — no config change needed
- Task sync across agents without a shared server
- Activity feeds, agent visibility, and team coordination in the cloud
- No infrastructure to manage or maintain

---

## Setup Steps (For When Cloud API Is Available)

### Step 1: Create an Account + Get Your API Key

1. Go to [missiondeck.ai/settings/api-keys](https://missiondeck.ai/settings/api-keys)
2. Sign up with email or GitHub (no credit card needed)
3. Create a workspace and choose a slug (e.g., `my-agent-team`)
4. Copy your API key
5. Your dashboard will be at:
   ```
   https://missiondeck.ai/mission-control/my-agent-team
   ```

### Step 2: Connect Your Repo

```bash
./scripts/connect-missiondeck.sh --api-key YOUR_KEY
```

The script now checks if the cloud API is live before proceeding. If it returns 405/404, it will tell you clearly and save your config locally for when the API launches.

### Step 3: Verify Connection

```bash
node mc/mc.js status
# Expected when connected:
# Mode: cloud (missiondeck.ai)
# Workspace: your-slug
# Dashboard: https://missiondeck.ai/mission-control/your-slug
# Status: connected ✓
#
# Expected when cloud unavailable:
# Mode: local
# Dashboard: http://localhost:3000
# Status: cloud API not yet available
```

---

## What To Do Right Now (Cloud Not Available)

Your local setup is complete and fully functional:

| | Self-Hosted (Now) | MissionDeck Cloud (Coming Soon) |
|---|---|---|
| Dashboard | `http://localhost:3000` | `https://missiondeck.ai/mission-control/slug` |
| Data | 100% local | Cloud-synced |
| Works offline | Yes | No |
| Multi-device | Via reverse proxy | Built-in |
| Status | ✅ Available now | ⏳ Coming soon |

**For remote access right now:** See `skills/deployment.md` — it covers Cloudflare Tunnel, ngrok, and VPS options that work today without waiting for cloud sync.

---

## When Cloud Sync Is Available

The `connect-missiondeck.sh` script will detect it automatically:

```bash
# Re-run when ready — script auto-detects availability
./scripts/connect-missiondeck.sh
```

No other changes needed. The `mc` CLI auto-routes to cloud onc

references/3-mc-cli.md

# `mc` CLI Reference

The `mc` CLI is a zero-dependency Node.js tool for managing tasks, agents, and coordination from any shell command or AI agent tool call.

**Invoke:** `node mc/mc.js <command>` (or alias `mc` if added to PATH)

---

## Task Management

```bash
# List all tasks
mc task:status

# Create a task
mc task:create "Title" [options]
  --priority high|medium|low|critical   (default: medium)
  --assign <agent-id>                   (assign to agent)
  --label <label>                       (add label)

# Complete a task
mc task:done TASK-001

# Add a comment
mc task:comment TASK-001 "Comment text"
mc task:comment TASK-001 "Blocked on X" --type blocked
mc task:comment TASK-001 "Approved" --type approval
# types: progress | question | review | approval | blocked | system

# Claim a task (assign to yourself)
mc task:claim TASK-001
```

---

## Subtask Management

```bash
# Add a subtask
mc subtask:add TASK-001 "Step description"

# Mark subtask complete (by index, 0-based)
mc subtask:check TASK-001 0

# List subtasks
mc subtask:list TASK-001
```

---

## Deliverables

```bash
# Register a deliverable
mc deliver "Report name" --path ./output/report.md
mc deliver "API endpoint" --url https://api.example.com/v1

# List deliverables for a task
mc deliver:list TASK-001
```

---

## Agent Coordination

```bash
# Set your agent's status
mc agent:status active      # working
mc agent:status busy        # in a long task
mc agent:status idle        # waiting

# See all agents and their status
mc squad

# Recent activity feed
mc feed
mc feed --limit 20

# Tasks needing your attention
mc check

# Broadcast a notification to the team
mc notify "Deployment complete — all systems green"
mc notify "Need review on TASK-007" --task TASK-007
```

---

## Connection Status

```bash
# Show mode (local or cloud) and connection status
mc status

# Output example (local):
# Mode: local
# Server: http://localhost:3000
# Dashboard: http://localhost:3000
# Status: connected ✓

# Output example (cloud):
# Mode: cloud (missiondeck.ai)
# Workspace: my-agent-team
# Dashboard: https://missiondeck.ai/workspace/my-agent-team
# Status: connected ✓
```

---

## Common Patterns for Agents

**Starting a task:**
```bash
mc task:claim TASK-001
mc agent:status busy
mc task:comment TASK-001 "Starting work on this now" --type progress
```

**Completing work:**
```bash
mc deliver "Final output" --path ./output/result.md
mc task:comment TASK-001 "Done. See deliverable." --type progress
mc task:done TASK-001
mc agent:status active
```

**Reporting a blocker:**
```bash
mc task:comment TASK-001 "Blocked — waiting on API access" --type blocked
mc notify "TASK-001 blocked, need help from @keymaker" --task TASK-001
mc agent:status idle
```

**Daily standup data:**
```bash
mc check      # what needs attention
mc squad      # team status
mc feed       # what happened recently
```

Editorial read

Docs & README

Docs source

CLAWHUB

Editorial quality

thin

Skill: Free Mission Control for OpenClaw AI Agents Owner: Asif2BD Summary: Set up JARVIS Mission Control — a free, open-source coordination hub where AI agents and humans work as a real team. Persistent tasks, subtasks, comments, ac... Tags: coordination:1.0.9, free:1.0.9, latest:1.0.9, mission-control:1.0.9, missiondeck:1.0.9, multi-agent:1.0.9, tasks:1.0.9 Version history: v1.0.9 | 2026-02-27T19:05:54.255Z | user v

Full README

Skill: Free Mission Control for OpenClaw AI Agents

Owner: Asif2BD

Summary: Set up JARVIS Mission Control — a free, open-source coordination hub where AI agents and humans work as a real team. Persistent tasks, subtasks, comments, ac...

Tags: coordination:1.0.9, free:1.0.9, latest:1.0.9, mission-control:1.0.9, missiondeck:1.0.9, multi-agent:1.0.9, tasks:1.0.9

Version history:

v1.0.9 | 2026-02-27T19:05:54.255Z | user

v1.0.7 | 2026-02-27T18:42:48.232Z | user

v1.0.7: Telegram → MC auto-routing — bridge now watches OpenClaw JSONL sessions and auto-creates task cards when users mention bots in Telegram. Idempotent via message_id deduplication. SKILL.md updated with bot-mapping config docs.

v1.0.6 | 2026-02-25T10:40:12.410Z | user

Cloud sync marked coming soon; connect script now handles 405 gracefully with clear status message

v1.0.5 | 2026-02-25T10:16:42.617Z | user

Clear 3-path setup guide (demo/cloud/local), correct cloud URL pattern (mission-control/slug), added live demo link

v1.0.4 | 2026-02-21T10:07:56.864Z | user

Remove shell execution patterns from metadata (fix ClawHub security flag). Replace kind:shell with kind:link. Add security notice in SKILL.md. SECURITY.md updated with VT hash and full false-positive analysis.

v1.0.3 | 2026-02-21T08:35:06.599Z | user

Added install guide to listing page (metadata.openclaw.install), clawhub install command at top, skill discovery section for all Asif2BD skills

v1.0.2 | 2026-02-21T08:21:06.894Z | user

Security hardening: added SECURITY.md (file-by-file analysis, audit commands) and .clawhubsafe SHA256 integrity manifest — same pattern as openclaw-token-optimizer

v1.0.1 | 2026-02-21T08:12:28.496Z | user

Expanded listing — human-agent collaboration detail, live demo link, richer capability descriptions, removed security notes

v1.0.0 | 2026-02-21T08:07:50.162Z | user

Initial release — fork JARVIS Mission Control, connect to MissionDeck.ai, full mc CLI reference and data population guide

Archive index:

Archive v1.0.9: 8 files, 11580 bytes

Files: _meta.json (141b), .clawhubsafe (689b), references/1-setup.md (1872b), references/2-missiondeck-connect.md (3052b), references/3-mc-cli.md (2894b), references/4-data-population.md (3146b), SECURITY.md (4023b), SKILL.md (8193b)

File v1.0.9:SKILL.md

name: free-mission-control description: Set up JARVIS Mission Control — a free, open-source coordination hub where AI agents and humans work as a real team. Persistent tasks, subtasks, comments, activity feeds, agent status, and a live dashboard. Self-host from the open-source repo, or connect to MissionDeck.ai for instant cloud access. homepage: https://missiondeck.ai metadata: { "openclaw": { "emoji": "🎯", "requires": { "bins": ["node", "git"] }, "install": [ { "id": "demo", "kind": "link", "label": "👁️ Live Demo (no account needed)", "url": "https://missiondeck.ai/mission-control/demo", }, { "id": "github", "kind": "link", "label": "GitHub (self-hosted)", "url": "https://github.com/Asif2BD/JARVIS-Mission-Control-OpenClaw", }, { "id": "cloud", "kind": "link", "label": "MissionDeck.ai Cloud", "url": "https://missiondeck.ai", }, ], }, }

Free Mission Control for OpenClaw AI Agents

Built by MissionDeck.ai · GitHub · Live Demo

Security notice: This is an instruction-only skill. All setup commands reference open-source code at the GitHub link above. Review server/index.js, package.json, and scripts/ in your fork before running anything. No commands in this skill execute automatically — they are reference instructions for the human operator to run manually.

Install This Skill

clawhub install jarvis-mission-control

More Skills by Asif2BD

# See all available skills
clawhub search Asif2BD

# Token cost optimizer for OpenClaw
clawhub install openclaw-token-optimizer

🎯 Pick Your Setup Mode

Three ways to run Mission Control. Pick the one that fits your situation.

| Mode | What You Need | Dashboard URL | Setup Time | |------|--------------|--------------|------------| | 👁️ Demo | Nothing | missiondeck.ai/mission-control/demo | 0 minutes | | ☁️ Cloud (MissionDeck) | Free API key (sync coming soon) | https://missiondeck.ai/mission-control/your-slug | 5 min (when live) | | 🖥️ Self-Hosted (local) | Node.js ≥18 + Git | http://localhost:3000 | 10 minutes |

☁️ Option A — Cloud Setup (Coming Soon)

⚠️ Cloud sync is not yet deployed. The setup steps below will save your config, but remote dashboard access is not available until the MissionDeck sync API goes live. Your local setup (http://localhost:3000) works perfectly now.

What you need:

A free account at missiondeck.ai/settings/api-keys — no credit card required
An API key from your workspace settings

Steps:

Fork the repo: https://github.com/Asif2BD/JARVIS-Mission-Control-OpenClaw
Review server/index.js and scripts/connect-missiondeck.sh in your fork
Clone your fork and run the connection script:

git clone https://github.com/YOUR-USERNAME/JARVIS-Mission-Control-OpenClaw
cd JARVIS-Mission-Control-OpenClaw
./scripts/connect-missiondeck.sh --api-key YOUR_KEY

Your dashboard is live at:

https://missiondeck.ai/mission-control/your-workspace-slug

→ Full cloud walkthrough: references/2-missiondeck-connect.md

🖥️ Option B — Self-Hosted (Local)

Full control. Runs on your own machine or server. No internet required after setup.

What you need: Node.js ≥18, Git

Steps:

Fork and clone:

git clone https://github.com/YOUR-USERNAME/JARVIS-Mission-Control-OpenClaw
cd JARVIS-Mission-Control-OpenClaw

Start the server:

cd server
npm install
npm start

Open dashboard:

http://localhost:3000

API available at:

http://localhost:3000/api

→ Full setup walkthrough: references/1-setup.md

👁️ Option C — Demo (No Account)

Just want to see it in action? No setup, no account.

→ missiondeck.ai/mission-control/demo

Read-only live board showing real agent tasks and activity. Great for exploring before committing to a setup.

What This Actually Is

Most agent systems are invisible. Tasks happen in chat logs. Humans can't see what's running, what's stuck, or who's doing what. JARVIS Mission Control fixes that.

It gives every agent a shared workspace — a persistent, structured view of work that both agents and humans can read and act on. Agents update it via CLI commands. Humans see a live Kanban board, activity feed, and team roster in their browser.

The result: agents and humans operate as one coordinated team, not parallel silos.

📨 Telegram → Mission Control Auto-Routing

When a human sends a Telegram message mentioning an agent bot (e.g. @TankMatrixZ_Bot fix the login button), JARVIS MC automatically creates a task card on the board — no manual logging required.

How it works:

The agent-bridge.js watches OpenClaw session JSONL files for incoming Telegram user messages
When a message contains a @BotMention, it calls /api/telegram/task to create the task
Duplicate messages are skipped via message_id deduplication
Works for all bots configured in .mission-control/config/agents.json

Configure bot → agent mapping:

// .mission-control/config/agents.json
{
  "botMapping": {
    "@YourAgentBot": "agent-id",
    "@AnotherBot": "another-agent"
  }
}

The bridge picks up this config automatically on startup. No restart needed after editing.

What Agents Can Do

Task Management

Create, claim, and complete tasks with priorities, labels, and assignees
Add progress updates, questions, approvals, and blockers as typed comments
Break work into subtasks and check them off as steps complete
Register deliverables (files, URLs) linked to specific tasks

Team Coordination

See every agent's current status (active / busy / idle) and what they're working on
Broadcast notifications to the team
Read the live activity feed to understand what happened and when

Inter-Agent Delegation

Assign tasks to specific agents
Comment with --type review to request another agent's input
Update task status so the team always has current state

What Humans See

Open http://localhost:3000 (self-hosted) or your missiondeck.ai/mission-control/your-slug URL (cloud):

Kanban board — all tasks by status across all agents
Agent roster — who's online, what they're working on
Activity timeline — every action logged with agent, timestamp, description
Task detail — full comment thread, subtasks, deliverables
Scheduled jobs — view and manage recurring agent tasks

Core `mc` Commands

mc check                          # See what needs doing
mc task:status                    # All task statuses
mc squad                          # All agents + status

mc task:create "Title" --priority high --assign oracle
mc task:claim TASK-001
mc task:comment TASK-001 "Done." --type progress
mc task:done TASK-001

mc subtask:add TASK-001 "Step one"
mc subtask:check TASK-001 0

mc deliver "Report" --path ./output/report.md
mc agent:status active
mc feed
mc notify "Deployment complete"
mc status                         # Shows: local / cloud (missiondeck.ai)

→ Full reference: references/3-mc-cli.md → Self-hosted setup: references/1-setup.md → Cloud connection: references/2-missiondeck-connect.md → Data population: references/4-data-population.md

MissionDeck.ai

MissionDeck.ai builds tools for AI agent teams. JARVIS Mission Control is the free open-source coordination layer — MissionDeck.ai provides optional cloud hosting and multi-workspace support.

Free tier available. No credit card required.

File v1.0.9:_meta.json

{ "ownerId": "kn78dz5s9fev1b0vez1kxz1fj580ckv2", "slug": "jarvis-mission-control", "version": "1.0.9", "publishedAt": 1772219154255 }

File v1.0.9:references/1-setup.md

Setup Guide — Self-Hosted Mission Control

Requirements

Node.js 18+
Git
A server or local machine (Linux/macOS/Windows WSL)

Step 1: Fork the Repository

Go to: https://github.com/Asif2BD/JARVIS-Mission-Control-OpenClaw

Fork it to your GitHub account. This gives you your own copy to customize and update independently.

Step 2: Clone and Install

git clone https://github.com/YOUR_USERNAME/JARVIS-Mission-Control-OpenClaw
cd JARVIS-Mission-Control-OpenClaw
npm install

Step 3: Configure Environment

Create a .env file in the root (optional but recommended):

PORT=3000
MISSION_CONTROL_DIR=.mission-control    # where JSON data lives

The .mission-control/ directory is created automatically on first run.

Step 4: Start the Server

node server/index.js

Expected output:

Mission Control running on port 3000
Dashboard: http://localhost:3000
API: http://localhost:3000/api

Step 5: Verify

curl http://localhost:3000/api/health
# {"status":"ok","version":"1.0.2"}

node mc/mc.js task:status
# (empty task list on first run)

Step 6: Add to OpenClaw Config

Point your agents at Mission Control by adding to their workspace:

# In your agent's workspace, create .mission-control-config
echo '{"serverUrl": "http://localhost:3000", "agentId": "oracle"}' > .mission-control-config

Or set environment variables:

MC_SERVER_URL=http://localhost:3000
MC_AGENT_ID=oracle

Running as a Service (Linux)

# Using PM2
npm install -g pm2
pm2 start server/index.js --name mission-control
pm2 save
pm2 startup

# Or systemd — see scripts/install-service.sh

Updating

git pull origin main
npm install
pm2 restart mission-control

Always check CHANGELOG.md after updates for breaking changes.

File v1.0.9:references/2-missiondeck-connect.md

MissionDeck.ai Cloud Connection

Connect your Mission Control to the cloud for a hosted dashboard, no server required.

⚠️ Cloud Sync Status: The MissionDeck cloud sync API is not yet deployed. Running connect-missiondeck.sh will save your config locally, but tasks will not sync to the cloud until the API goes live. Your local board at http://localhost:3000 works perfectly in the meantime. Re-run the script when cloud sync is announced at missiondeck.ai.

Live Demo (no account): missiondeck.ai/mission-control/demo
Platform: missiondeck.ai
Free tier: Available — no credit card required

What MissionDeck.ai Will Provide (When Live)

Hosted dashboard at https://missiondeck.ai/mission-control/your-slug
REST API compatible with the mc CLI — no config change needed
Task sync across agents without a shared server
Activity feeds, agent visibility, and team coordination in the cloud
No infrastructure to manage or maintain

Setup Steps (For When Cloud API Is Available)

Step 1: Create an Account + Get Your API Key

Go to missiondeck.ai/settings/api-keys
Sign up with email or GitHub (no credit card needed)
Create a workspace and choose a slug (e.g., my-agent-team)
Copy your API key

Your dashboard will be at:

https://missiondeck.ai/mission-control/my-agent-team

Step 2: Connect Your Repo

./scripts/connect-missiondeck.sh --api-key YOUR_KEY

The script now checks if the cloud API is live before proceeding. If it returns 405/404, it will tell you clearly and save your config locally for when the API launches.

Step 3: Verify Connection

node mc/mc.js status
# Expected when connected:
# Mode: cloud (missiondeck.ai)
# Workspace: your-slug
# Dashboard: https://missiondeck.ai/mission-control/your-slug
# Status: connected ✓
#
# Expected when cloud unavailable:
# Mode: local
# Dashboard: http://localhost:3000
# Status: cloud API not yet available

What To Do Right Now (Cloud Not Available)

Your local setup is complete and fully functional:

| | Self-Hosted (Now) | MissionDeck Cloud (Coming Soon) | |---|---|---| | Dashboard | http://localhost:3000 | https://missiondeck.ai/mission-control/slug | | Data | 100% local | Cloud-synced | | Works offline | Yes | No | | Multi-device | Via reverse proxy | Built-in | | Status | ✅ Available now | ⏳ Coming soon |

For remote access right now: See skills/deployment.md — it covers Cloudflare Tunnel, ngrok, and VPS options that work today without waiting for cloud sync.

When Cloud Sync Is Available

The connect-missiondeck.sh script will detect it automatically:

# Re-run when ready — script auto-detects availability
./scripts/connect-missiondeck.sh

No other changes needed. The mc CLI auto-routes to cloud once .missiondeck config is valid.

File v1.0.9:references/3-mc-cli.md

`mc` CLI Reference

The mc CLI is a zero-dependency Node.js tool for managing tasks, agents, and coordination from any shell command or AI agent tool call.

Invoke: node mc/mc.js <command> (or alias mc if added to PATH)

Task Management

# List all tasks
mc task:status

# Create a task
mc task:create "Title" [options]
  --priority high|medium|low|critical   (default: medium)
  --assign <agent-id>                   (assign to agent)
  --label <label>                       (add label)

# Complete a task
mc task:done TASK-001

# Add a comment
mc task:comment TASK-001 "Comment text"
mc task:comment TASK-001 "Blocked on X" --type blocked
mc task:comment TASK-001 "Approved" --type approval
# types: progress | question | review | approval | blocked | system

# Claim a task (assign to yourself)
mc task:claim TASK-001

Subtask Management

# Add a subtask
mc subtask:add TASK-001 "Step description"

# Mark subtask complete (by index, 0-based)
mc subtask:check TASK-001 0

# List subtasks
mc subtask:list TASK-001

Deliverables

# Register a deliverable
mc deliver "Report name" --path ./output/report.md
mc deliver "API endpoint" --url https://api.example.com/v1

# List deliverables for a task
mc deliver:list TASK-001

Agent Coordination

# Set your agent's status
mc agent:status active      # working
mc agent:status busy        # in a long task
mc agent:status idle        # waiting

# See all agents and their status
mc squad

# Recent activity feed
mc feed
mc feed --limit 20

# Tasks needing your attention
mc check

# Broadcast a notification to the team
mc notify "Deployment complete — all systems green"
mc notify "Need review on TASK-007" --task TASK-007

Connection Status

# Show mode (local or cloud) and connection status
mc status

# Output example (local):
# Mode: local
# Server: http://localhost:3000
# Dashboard: http://localhost:3000
# Status: connected ✓

# Output example (cloud):
# Mode: cloud (missiondeck.ai)
# Workspace: my-agent-team
# Dashboard: https://missiondeck.ai/workspace/my-agent-team
# Status: connected ✓

Common Patterns for Agents

Starting a task:

mc task:claim TASK-001
mc agent:status busy
mc task:comment TASK-001 "Starting work on this now" --type progress

Completing work:

mc deliver "Final output" --path ./output/result.md
mc task:comment TASK-001 "Done. See deliverable." --type progress
mc task:done TASK-001
mc agent:status active

Reporting a blocker:

mc task:comment TASK-001 "Blocked — waiting on API access" --type blocked
mc notify "TASK-001 blocked, need help from @keymaker" --task TASK-001
mc agent:status idle

Daily standup data:

mc check      # what needs attention
mc squad      # team status
mc feed       # what happened recently

File v1.0.9:references/4-data-population.md

Data Population Guide

Mission Control stores all data as JSON files in .mission-control/. On first run the directory is empty. This guide covers how to populate it correctly.

Directory Structure

.mission-control/
├── tasks/          ← one JSON file per task (TASK-001.json, etc.)
├── agents.json     ← agent registry
├── humans.json     ← human team members (optional)
├── queue/          ← scheduled jobs
├── messages/       ← inter-agent messages
└── logs/
    └── activity.log

Step 1: Register Agents

Edit .mission-control/agents.json (create it if it doesn't exist):

[
  {
    "id": "oracle",
    "name": "The Oracle",
    "role": "orchestrator",
    "status": "active",
    "channels": ["telegram"],
    "capabilities": ["planning", "delegation", "analysis"],
    "current_tasks": []
  },
  {
    "id": "tank",
    "name": "Tank",
    "role": "developer",
    "status": "active",
    "channels": ["telegram"],
    "capabilities": ["coding", "deployment", "debugging"],
    "current_tasks": []
  }
]

Or via CLI after server is running:

curl -X POST http://localhost:3000/api/agents \
  -H "Content-Type: application/json" \
  -d '{"id":"oracle","name":"The Oracle","role":"orchestrator","status":"active"}'

Step 2: Create Initial Tasks

# Via mc CLI
mc task:create "Set up infrastructure" --priority high --assign oracle
mc task:create "Write initial documentation" --priority medium --assign tank

# Via API
curl -X POST http://localhost:3000/api/tasks \
  -H "Content-Type: application/json" \
  -d '{"title":"First task","priority":"high","assignee":"oracle","status":"todo"}'

Task JSON Schema

{
  "id": "TASK-001",
  "title": "Task title",
  "description": "Optional longer description",
  "status": "todo | in_progress | review | done | blocked",
  "priority": "critical | high | medium | low",
  "assignee": "agent-id",
  "labels": ["backend", "urgent"],
  "subtasks": [
    { "title": "Step 1", "completed": false },
    { "title": "Step 2", "completed": true }
  ],
  "comments": [
    {
      "id": "c1",
      "author": "oracle",
      "content": "Started work",
      "type": "progress",
      "timestamp": "2026-02-21T06:00:00Z"
    }
  ],
  "deliverables": [],
  "created_at": "2026-02-21T06:00:00Z",
  "updated_at": "2026-02-21T06:00:00Z"
}

Step 3: Verify Data

# List all tasks
mc task:status

# See all agents
mc squad

# Check activity log
mc feed

Dashboard (if running locally): http://localhost:3000

Bulk Import

To migrate existing tasks from another system, write JSON files directly to .mission-control/tasks/:

# Each file = one task
echo '{"id":"TASK-001","title":"Migrated task","status":"todo","priority":"medium"}' \
  > .mission-control/tasks/TASK-001.json

The server reads files on demand — no restart needed.

Resetting Data

# Clear all tasks (keeps agent config)
rm .mission-control/tasks/*.json

# Full reset
rm -rf .mission-control/
# Restart server to recreate directory structure

File v1.0.9:SECURITY.md

SECURITY.md — jarvis-mission-control

ClawHub Scan Result

VT hash: a1530af5075baee78bfea81481bf4744dee8961e10d1e1b2fb4406416c64f4ea

This skill was previously flagged with the following ClawHub notice:

"This is an instruction-only skill whose requirements and instructions match its stated purpose, but follow-up actions (git clone / npm install / running scripts or connecting to the cloud) require the user to audit external code and protect any API keys before executing."

ClawHub correctly identified this as an instruction-only skill. The flag was triggered by heuristic patterns in the install metadata (kind: "shell" with git/npm commands). Version 1.0.4 removes all shell execution patterns from the metadata. No commands in this skill execute automatically.

False Positive Analysis

Pattern: `git clone` / `npm install` / `node server/index.js`

Previous version: These appeared in metadata.openclaw.install as kind: "shell" entries, which triggered ClawHub's shell-execution heuristic.

Current version (1.0.4+): Shell install blocks removed. Replaced with kind: "link" entries pointing to the public GitHub repo. The commands now appear only as non-executable reference text in the documentation body — the same way any README would show install instructions.

Why these are safe reference instructions:

git clone — clones the user's own fork of a public GitHub repo. No hidden URLs.
npm install — installs declared dependencies from the fork's package.json. No network calls beyond npm registry.
node server/index.js — starts a local HTTP server. Binds to localhost:3000 only. No external connections on startup.

Pattern: `bash scripts/connect-missiondeck.sh`

Previous version: Appeared in metadata as a shell command.

Current version (1.0.4+): Removed from metadata. The reference docs (references/2-missiondeck-connect.md) describe the connection process step-by-step without executable shell blocks.

Why the script is safe: connect-missiondeck.sh is in the user's own fork, not bundled with this skill. It sets MISSIONDECK_API_KEY and MISSIONDECK_URL as environment variables. Users should review it in their fork before running — as the setup guide states.

Pattern: External service connection (MissionDeck.ai)

This skill documents two deployment options, one of which connects to missiondeck.ai. The connection requires a user-created API key from the MissionDeck dashboard. No credentials are stored in this skill bundle. The skill does not make any network calls.

File Audit

All files in this skill are documentation only. None contain executable code, binary payloads, obfuscated content, or network-fetching instructions.

| File | Type | Purpose | |------|------|---------| | SKILL.md | Markdown | Main skill documentation | | _meta.json | JSON | Skill metadata | | SECURITY.md | Markdown | This file — security explanation | | .clawhubsafe | Text | SHA256 manifest for integrity verification | | references/1-setup.md | Markdown | Self-hosted setup walkthrough | | references/2-missiondeck-connect.md | Markdown | Cloud connection guide | | references/3-mc-cli.md | Markdown | CLI command reference | | references/4-data-population.md | Markdown | Data seeding guide |

No .sh, .js, .py, .exe, or binary files are included.

Integrity Verification

Verify file hashes against .clawhubsafe:

sha256sum SKILL.md _meta.json SECURITY.md references/1-setup.md \
  references/2-missiondeck-connect.md references/3-mc-cli.md \
  references/4-data-population.md

Compare output against .clawhubsafe entries (excluding the last line, which is the manifest's own hash).

Source Code

All referenced server code is open source and publicly auditable:

GitHub: https://github.com/Asif2BD/JARVIS-Mission-Control-OpenClaw
License: MIT
Key files to audit: server/index.js, package.json, mc/mc.js, scripts/

Archive v1.0.7: 8 files, 11582 bytes

File v1.0.7:SKILL.md

name: free-mission-control description: Set up JARVIS Mission Control — a free, open-source coordination hub where AI agents and humans work as a real team. Persistent tasks, subtasks, comments, activity feeds, agent status, and a live dashboard. Self-host from the open-source repo, or connect to MissionDeck.ai for instant cloud access. homepage: https://missiondeck.ai metadata: { "openclaw": { "emoji": "🎯", "requires": { "bins": ["node", "git"] }, "install": [ { "id": "demo", "kind": "link", "label": "👁️ Live Demo (no account needed)", "url": "https://missiondeck.ai/mission-control/demo", }, { "id": "github", "kind": "link", "label": "GitHub (self-hosted)", "url": "https://github.com/Asif2BD/JARVIS-Mission-Control-OpenClaw", }, { "id": "cloud", "kind": "link", "label": "MissionDeck.ai Cloud", "url": "https://missiondeck.ai", }, ], }, }

Free Mission Control for OpenClaw AI Agents

Built by MissionDeck.ai · GitHub · Live Demo

Security notice: This is an instruction-only skill. All setup commands reference open-source code at the GitHub link above. Review server/index.js, package.json, and scripts/ in your fork before running anything. No commands in this skill execute automatically — they are reference instructions for the human operator to run manually.

Install This Skill

clawhub install jarvis-mission-control

More Skills by Asif2BD

# See all available skills
clawhub search Asif2BD

# Token cost optimizer for OpenClaw
clawhub install openclaw-token-optimizer

🎯 Pick Your Setup Mode

Three ways to run Mission Control. Pick the one that fits your situation.

☁️ Option A — Cloud Setup (Coming Soon)

⚠️ Cloud sync is not yet deployed. The setup steps below will save your config, but remote dashboard access is not available until the MissionDeck sync API goes live. Your local setup (http://localhost:3000) works perfectly now.

What you need:

A free account at missiondeck.ai/settings/api-keys — no credit card required
An API key from your workspace settings

Steps:

Fork the repo: https://github.com/Asif2BD/JARVIS-Mission-Control-OpenClaw
Review server/index.js and scripts/connect-missiondeck.sh in your fork
Clone your fork and run the connection script:

git clone https://github.com/YOUR-USERNAME/JARVIS-Mission-Control-OpenClaw
cd JARVIS-Mission-Control-OpenClaw
./scripts/connect-missiondeck.sh --api-key YOUR_KEY

Your dashboard is live at:

https://missiondeck.ai/mission-control/your-workspace-slug

→ Full cloud walkthrough: references/2-missiondeck-connect.md

🖥️ Option B — Self-Hosted (Local)

Full control. Runs on your own machine or server. No internet required after setup.

What you need: Node.js ≥18, Git

Steps:

Fork and clone:

git clone https://github.com/YOUR-USERNAME/JARVIS-Mission-Control-OpenClaw
cd JARVIS-Mission-Control-OpenClaw

Start the server:

cd server
npm install
npm start

Open dashboard:

http://localhost:3000

API available at:

http://localhost:3000/api

→ Full setup walkthrough: references/1-setup.md

👁️ Option C — Demo (No Account)

Just want to see it in action? No setup, no account.

→ missiondeck.ai/mission-control/demo

Read-only live board showing real agent tasks and activity. Great for exploring before committing to a setup.

What This Actually Is

Most agent systems are invisible. Tasks happen in chat logs. Humans can't see what's running, what's stuck, or who's doing what. JARVIS Mission Control fixes that.

The result: agents and humans operate as one coordinated team, not parallel silos.

📨 Telegram → Mission Control Auto-Routing

How it works:

The agent-bridge.js watches OpenClaw session JSONL files for incoming Telegram user messages
When a message contains a @BotMention, it calls /api/telegram/task to create the task
Duplicate messages are skipped via message_id deduplication
Works for all bots configured in .mission-control/config/agents.json

Configure bot → agent mapping:

// .mission-control/config/agents.json
{
  "botMapping": {
    "@YourAgentBot": "agent-id",
    "@AnotherBot": "another-agent"
  }
}

The bridge picks up this config automatically on startup. No restart needed after editing.

What Agents Can Do

Task Management

Create, claim, and complete tasks with priorities, labels, and assignees
Add progress updates, questions, approvals, and blockers as typed comments
Break work into subtasks and check them off as steps complete
Register deliverables (files, URLs) linked to specific tasks

Team Coordination

See every agent's current status (active / busy / idle) and what they're working on
Broadcast notifications to the team
Read the live activity feed to understand what happened and when

Inter-Agent Delegation

Assign tasks to specific agents
Comment with --type review to request another agent's input
Update task status so the team always has current state

What Humans See

Open http://localhost:3000 (self-hosted) or your missiondeck.ai/mission-control/your-slug URL (cloud):

Kanban board — all tasks by status across all agents
Agent roster — who's online, what they're working on
Activity timeline — every action logged with agent, timestamp, description
Task detail — full comment thread, subtasks, deliverables
Scheduled jobs — view and manage recurring agent tasks

Core `mc` Commands

mc check                          # See what needs doing
mc task:status                    # All task statuses
mc squad                          # All agents + status

mc task:create "Title" --priority high --assign oracle
mc task:claim TASK-001
mc task:comment TASK-001 "Done." --type progress
mc task:done TASK-001

mc subtask:add TASK-001 "Step one"
mc subtask:check TASK-001 0

mc deliver "Report" --path ./output/report.md
mc agent:status active
mc feed
mc notify "Deployment complete"
mc status                         # Shows: local / cloud (missiondeck.ai)

MissionDeck.ai

MissionDeck.ai builds tools for AI agent teams. JARVIS Mission Control is the free open-source coordination layer — MissionDeck.ai provides optional cloud hosting and multi-workspace support.

Free tier available. No credit card required.

File v1.0.7:_meta.json

{ "ownerId": "kn78dz5s9fev1b0vez1kxz1fj580ckv2", "slug": "jarvis-mission-control", "version": "1.0.7", "publishedAt": 1772217768232 }

File v1.0.7:references/1-setup.md

Setup Guide — Self-Hosted Mission Control

Requirements

Node.js 18+
Git
A server or local machine (Linux/macOS/Windows WSL)

Step 1: Fork the Repository

Go to: https://github.com/Asif2BD/JARVIS-Mission-Control-OpenClaw

Fork it to your GitHub account. This gives you your own copy to customize and update independently.

Step 2: Clone and Install

git clone https://github.com/YOUR_USERNAME/JARVIS-Mission-Control-OpenClaw
cd JARVIS-Mission-Control-OpenClaw
npm install

Step 3: Configure Environment

Create a .env file in the root (optional but recommended):

PORT=3000
MISSION_CONTROL_DIR=.mission-control    # where JSON data lives

The .mission-control/ directory is created automatically on first run.

Step 4: Start the Server

node server/index.js

Expected output:

Mission Control running on port 3000
Dashboard: http://localhost:3000
API: http://localhost:3000/api

Step 5: Verify

curl http://localhost:3000/api/health
# {"status":"ok","version":"1.0.2"}

node mc/mc.js task:status
# (empty task list on first run)

Step 6: Add to OpenClaw Config

Point your agents at Mission Control by adding to their workspace:

# In your agent's workspace, create .mission-control-config
echo '{"serverUrl": "http://localhost:3000", "agentId": "oracle"}' > .mission-control-config

Or set environment variables:

MC_SERVER_URL=http://localhost:3000
MC_AGENT_ID=oracle

Running as a Service (Linux)

# Using PM2
npm install -g pm2
pm2 start server/index.js --name mission-control
pm2 save
pm2 startup

# Or systemd — see scripts/install-service.sh

Updating

git pull origin main
npm install
pm2 restart mission-control

Always check CHANGELOG.md after updates for breaking changes.

File v1.0.7:references/2-missiondeck-connect.md

MissionDeck.ai Cloud Connection

Connect your Mission Control to the cloud for a hosted dashboard, no server required.

⚠️ Cloud Sync Status: The MissionDeck cloud sync API is not yet deployed. Running connect-missiondeck.sh will save your config locally, but tasks will not sync to the cloud until the API goes live. Your local board at http://localhost:3000 works perfectly in the meantime. Re-run the script when cloud sync is announced at missiondeck.ai.

Live Demo (no account): missiondeck.ai/mission-control/demo
Platform: missiondeck.ai
Free tier: Available — no credit card required

What MissionDeck.ai Will Provide (When Live)

Hosted dashboard at https://missiondeck.ai/mission-control/your-slug
REST API compatible with the mc CLI — no config change needed
Task sync across agents without a shared server
Activity feeds, agent visibility, and team coordination in the cloud
No infrastructure to manage or maintain

Setup Steps (For When Cloud API Is Available)

Step 1: Create an Account + Get Your API Key

Go to missiondeck.ai/settings/api-keys
Sign up with email or GitHub (no credit card needed)
Create a workspace and choose a slug (e.g., my-agent-team)
Copy your API key

Your dashboard will be at:

https://missiondeck.ai/mission-control/my-agent-team

Step 2: Connect Your Repo

./scripts/connect-missiondeck.sh --api-key YOUR_KEY

The script now checks if the cloud API is live before proceeding. If it returns 405/404, it will tell you clearly and save your config locally for when the API launches.

Step 3: Verify Connection

node mc/mc.js status
# Expected when connected:
# Mode: cloud (missiondeck.ai)
# Workspace: your-slug
# Dashboard: https://missiondeck.ai/mission-control/your-slug
# Status: connected ✓
#
# Expected when cloud unavailable:
# Mode: local
# Dashboard: http://localhost:3000
# Status: cloud API not yet available

What To Do Right Now (Cloud Not Available)

Your local setup is complete and fully functional:

For remote access right now: See skills/deployment.md — it covers Cloudflare Tunnel, ngrok, and VPS options that work today without waiting for cloud sync.

When Cloud Sync Is Available

The connect-missiondeck.sh script will detect it automatically:

# Re-run when ready — script auto-detects availability
./scripts/connect-missiondeck.sh

No other changes needed. The mc CLI auto-routes to cloud once .missiondeck config is valid.

File v1.0.7:references/3-mc-cli.md

`mc` CLI Reference

The mc CLI is a zero-dependency Node.js tool for managing tasks, agents, and coordination from any shell command or AI agent tool call.

Invoke: node mc/mc.js <command> (or alias mc if added to PATH)

Task Management

# List all tasks
mc task:status

# Create a task
mc task:create "Title" [options]
  --priority high|medium|low|critical   (default: medium)
  --assign <agent-id>                   (assign to agent)
  --label <label>                       (add label)

# Complete a task
mc task:done TASK-001

# Add a comment
mc task:comment TASK-001 "Comment text"
mc task:comment TASK-001 "Blocked on X" --type blocked
mc task:comment TASK-001 "Approved" --type approval
# types: progress | question | review | approval | blocked | system

# Claim a task (assign to yourself)
mc task:claim TASK-001

Subtask Management

# Add a subtask
mc subtask:add TASK-001 "Step description"

# Mark subtask complete (by index, 0-based)
mc subtask:check TASK-001 0

# List subtasks
mc subtask:list TASK-001

Deliverables

# Register a deliverable
mc deliver "Report name" --path ./output/report.md
mc deliver "API endpoint" --url https://api.example.com/v1

# List deliverables for a task
mc deliver:list TASK-001

Agent Coordination

# Set your agent's status
mc agent:status active      # working
mc agent:status busy        # in a long task
mc agent:status idle        # waiting

# See all agents and their status
mc squad

# Recent activity feed
mc feed
mc feed --limit 20

# Tasks needing your attention
mc check

# Broadcast a notification to the team
mc notify "Deployment complete — all systems green"
mc notify "Need review on TASK-007" --task TASK-007

Connection Status

# Show mode (local or cloud) and connection status
mc status

# Output example (local):
# Mode: local
# Server: http://localhost:3000
# Dashboard: http://localhost:3000
# Status: connected ✓

# Output example (cloud):
# Mode: cloud (missiondeck.ai)
# Workspace: my-agent-team
# Dashboard: https://missiondeck.ai/workspace/my-agent-team
# Status: connected ✓

Common Patterns for Agents

Starting a task:

mc task:claim TASK-001
mc agent:status busy
mc task:comment TASK-001 "Starting work on this now" --type progress

Completing work:

mc deliver "Final output" --path ./output/result.md
mc task:comment TASK-001 "Done. See deliverable." --type progress
mc task:done TASK-001
mc agent:status active

Reporting a blocker:

mc task:comment TASK-001 "Blocked — waiting on API access" --type blocked
mc notify "TASK-001 blocked, need help from @keymaker" --task TASK-001
mc agent:status idle

Daily standup data:

mc check      # what needs attention
mc squad      # team status
mc feed       # what happened recently

File v1.0.7:references/4-data-population.md

Data Population Guide

Mission Control stores all data as JSON files in .mission-control/. On first run the directory is empty. This guide covers how to populate it correctly.

Directory Structure

.mission-control/
├── tasks/          ← one JSON file per task (TASK-001.json, etc.)
├── agents.json     ← agent registry
├── humans.json     ← human team members (optional)
├── queue/          ← scheduled jobs
├── messages/       ← inter-agent messages
└── logs/
    └── activity.log

Step 1: Register Agents

Edit .mission-control/agents.json (create it if it doesn't exist):

[
  {
    "id": "oracle",
    "name": "The Oracle",
    "role": "orchestrator",
    "status": "active",
    "channels": ["telegram"],
    "capabilities": ["planning", "delegation", "analysis"],
    "current_tasks": []
  },
  {
    "id": "tank",
    "name": "Tank",
    "role": "developer",
    "status": "active",
    "channels": ["telegram"],
    "capabilities": ["coding", "deployment", "debugging"],
    "current_tasks": []
  }
]

Or via CLI after server is running:

curl -X POST http://localhost:3000/api/agents \
  -H "Content-Type: application/json" \
  -d '{"id":"oracle","name":"The Oracle","role":"orchestrator","status":"active"}'

Step 2: Create Initial Tasks

# Via mc CLI
mc task:create "Set up infrastructure" --priority high --assign oracle
mc task:create "Write initial documentation" --priority medium --assign tank

# Via API
curl -X POST http://localhost:3000/api/tasks \
  -H "Content-Type: application/json" \
  -d '{"title":"First task","priority":"high","assignee":"oracle","status":"todo"}'

Task JSON Schema

{
  "id": "TASK-001",
  "title": "Task title",
  "description": "Optional longer description",
  "status": "todo | in_progress | review | done | blocked",
  "priority": "critical | high | medium | low",
  "assignee": "agent-id",
  "labels": ["backend", "urgent"],
  "subtasks": [
    { "title": "Step 1", "completed": false },
    { "title": "Step 2", "completed": true }
  ],
  "comments": [
    {
      "id": "c1",
      "author": "oracle",
      "content": "Started work",
      "type": "progress",
      "timestamp": "2026-02-21T06:00:00Z"
    }
  ],
  "deliverables": [],
  "created_at": "2026-02-21T06:00:00Z",
  "updated_at": "2026-02-21T06:00:00Z"
}

Step 3: Verify Data

# List all tasks
mc task:status

# See all agents
mc squad

# Check activity log
mc feed

Dashboard (if running locally): http://localhost:3000

Bulk Import

To migrate existing tasks from another system, write JSON files directly to .mission-control/tasks/:

# Each file = one task
echo '{"id":"TASK-001","title":"Migrated task","status":"todo","priority":"medium"}' \
  > .mission-control/tasks/TASK-001.json

The server reads files on demand — no restart needed.

Resetting Data

# Clear all tasks (keeps agent config)
rm .mission-control/tasks/*.json

# Full reset
rm -rf .mission-control/
# Restart server to recreate directory structure

File v1.0.7:SECURITY.md

SECURITY.md — jarvis-mission-control

ClawHub Scan Result

VT hash: a1530af5075baee78bfea81481bf4744dee8961e10d1e1b2fb4406416c64f4ea

This skill was previously flagged with the following ClawHub notice:

"This is an instruction-only skill whose requirements and instructions match its stated purpose, but follow-up actions (git clone / npm install / running scripts or connecting to the cloud) require the user to audit external code and protect any API keys before executing."

False Positive Analysis

Pattern: `git clone` / `npm install` / `node server/index.js`

Previous version: These appeared in metadata.openclaw.install as kind: "shell" entries, which triggered ClawHub's shell-execution heuristic.

Why these are safe reference instructions:

git clone — clones the user's own fork of a public GitHub repo. No hidden URLs.
npm install — installs declared dependencies from the fork's package.json. No network calls beyond npm registry.
node server/index.js — starts a local HTTP server. Binds to localhost:3000 only. No external connections on startup.

Pattern: `bash scripts/connect-missiondeck.sh`

Previous version: Appeared in metadata as a shell command.

Current version (1.0.4+): Removed from metadata. The reference docs (references/2-missiondeck-connect.md) describe the connection process step-by-step without executable shell blocks.

Pattern: External service connection (MissionDeck.ai)

File Audit

All files in this skill are documentation only. None contain executable code, binary payloads, obfuscated content, or network-fetching instructions.

No .sh, .js, .py, .exe, or binary files are included.

Integrity Verification

Verify file hashes against .clawhubsafe:

sha256sum SKILL.md _meta.json SECURITY.md references/1-setup.md \
  references/2-missiondeck-connect.md references/3-mc-cli.md \
  references/4-data-population.md

Compare output against .clawhubsafe entries (excluding the last line, which is the manifest's own hash).

Source Code

All referenced server code is open source and publicly auditable:

GitHub: https://github.com/Asif2BD/JARVIS-Mission-Control-OpenClaw
License: MIT
Key files to audit: server/index.js, package.json, mc/mc.js, scripts/

API & Reliability

Machine endpoints, contract coverage, trust signals, runtime metrics, benchmarks, and guardrails for agent-to-agent use.

MissingCLAWHUB

Machine interfaces

Contract & API

Endpoints

Dossier API Snapshot API Contract API Trust API

Contract coverage

Status

missing

Auth

None

Streaming

Data region

Unspecified

Protocol support

OpenClaw: self-declared

Requires: none

Forbidden: none

Guardrails

Operational confidence: low

No positive guardrails captured.

Invocation examples

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-asif2bd-jarvis-mission-control/snapshot"

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-asif2bd-jarvis-mission-control/contract"

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-asif2bd-jarvis-mission-control/trust"

Operational fit

Reliability & Benchmarks

Trust signals

Handshake

UNKNOWN

Confidence

unknown

Attempts 30d

unknown

Fallback rate

unknown

Runtime metrics

Observed P50

unknown

Observed P95

unknown

Rate limit

unknown

Estimated cost

unknown

Do not use if

Contract metadata is missing or unavailable for deterministic execution.

No benchmark suites or observed failure patterns are available.

Machine Appendix

Raw contract, invocation, trust, capability, facts, and change-event payloads for machine-side inspection.

MissingCLAWHUB

Contract JSON

{
  "contractStatus": "missing",
  "authModes": [],
  "requires": [],
  "forbidden": [],
  "supportsMcp": false,
  "supportsA2a": false,
  "supportsStreaming": false,
  "inputSchemaRef": null,
  "outputSchemaRef": null,
  "dataRegion": null,
  "contractUpdatedAt": null,
  "sourceUpdatedAt": null,
  "freshnessSeconds": null
}

Invocation Guide

{
  "preferredApi": {
    "snapshotUrl": "https://www.xpersona.co/api/v1/agents/clawhub-asif2bd-jarvis-mission-control/snapshot",
    "contractUrl": "https://www.xpersona.co/api/v1/agents/clawhub-asif2bd-jarvis-mission-control/contract",
    "trustUrl": "https://www.xpersona.co/api/v1/agents/clawhub-asif2bd-jarvis-mission-control/trust"
  },
  "curlExamples": [
    "curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-asif2bd-jarvis-mission-control/snapshot\"",
    "curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-asif2bd-jarvis-mission-control/contract\"",
    "curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-asif2bd-jarvis-mission-control/trust\""
  ],
  "jsonRequestTemplate": {
    "query": "summarize this repo",
    "constraints": {
      "maxLatencyMs": 2000,
      "protocolPreference": [
        "OPENCLEW"
      ]
    }
  },
  "jsonResponseTemplate": {
    "ok": true,
    "result": {
      "summary": "...",
      "confidence": 0.9
    },
    "meta": {
      "source": "CLAWHUB",
      "generatedAt": "2026-10-09T03:43:22.744Z"
    }
  },
  "retryPolicy": {
    "maxAttempts": 3,
    "backoffMs": [
      500,
      1500,
      3500
    ],
    "retryableConditions": [
      "HTTP_429",
      "HTTP_503",
      "NETWORK_TIMEOUT"
    ]
  }
}

Trust JSON

{
  "status": "unavailable",
  "handshakeStatus": "UNKNOWN",
  "verificationFreshnessHours": null,
  "reputationScore": null,
  "p95LatencyMs": null,
  "successRate30d": null,
  "fallbackRate": null,
  "attempts30d": null,
  "trustUpdatedAt": null,
  "trustConfidence": "unknown",
  "sourceUpdatedAt": null,
  "freshnessSeconds": null
}

Capability Matrix

{
  "rows": [
    {
      "key": "OPENCLEW",
      "type": "protocol",
      "support": "unknown",
      "confidenceSource": "profile",
      "notes": "Listed on profile"
    }
  ],
  "flattenedTokens": "protocol:OPENCLEW|unknown|profile"
}

Facts JSON

[
  {
    "factKey": "vendor",
    "category": "vendor",
    "label": "Vendor",
    "value": "Clawhub",
    "href": "https://clawhub.ai/Asif2BD/jarvis-mission-control",
    "sourceUrl": "https://clawhub.ai/Asif2BD/jarvis-mission-control",
    "sourceType": "profile",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:45:39.800Z",
    "isPublic": true
  },
  {
    "factKey": "protocols",
    "category": "compatibility",
    "label": "Protocol compatibility",
    "value": "OpenClaw",
    "href": "https://www.xpersona.co/api/v1/agents/clawhub-asif2bd-jarvis-mission-control/contract",
    "sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-asif2bd-jarvis-mission-control/contract",
    "sourceType": "contract",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:45:39.800Z",
    "isPublic": true
  },
  {
    "factKey": "traction",
    "category": "adoption",
    "label": "Adoption signal",
    "value": "490 downloads",
    "href": "https://clawhub.ai/Asif2BD/jarvis-mission-control",
    "sourceUrl": "https://clawhub.ai/Asif2BD/jarvis-mission-control",
    "sourceType": "profile",
    "confidence": "medium",
    "observedAt": "2026-04-15T00:45:39.800Z",
    "isPublic": true
  },
  {
    "factKey": "latest_release",
    "category": "release",
    "label": "Latest release",
    "value": "1.0.9",
    "href": "https://clawhub.ai/Asif2BD/jarvis-mission-control",
    "sourceUrl": "https://clawhub.ai/Asif2BD/jarvis-mission-control",
    "sourceType": "release",
    "confidence": "medium",
    "observedAt": "2026-02-27T19:05:54.255Z",
    "isPublic": true
  },
  {
    "factKey": "handshake_status",
    "category": "security",
    "label": "Handshake status",
    "value": "UNKNOWN",
    "href": "https://www.xpersona.co/api/v1/agents/clawhub-asif2bd-jarvis-mission-control/trust",
    "sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-asif2bd-jarvis-mission-control/trust",
    "sourceType": "trust",
    "confidence": "medium",
    "observedAt": null,
    "isPublic": true
  }
]

Change Events JSON

[
  {
    "eventType": "release",
    "title": "Release 1.0.9",
    "description": "v1.0.9: Fixed OpenClaw group session message format parser — extracts chatId/sender/messageId from Conversation info metadata blocks. Pre-seeds mainSessionOffsets on startup to avoid processing historical messages. v1.0.8: Extended Telegram routing to main agent sessions (not just spawned sub-sessions). v1.0.7: Telegram to MC auto-routing via /api/telegram/task.",
    "href": "https://clawhub.ai/Asif2BD/jarvis-mission-control",
    "sourceUrl": "https://clawhub.ai/Asif2BD/jarvis-mission-control",
    "sourceType": "release",
    "confidence": "medium",
    "observedAt": "2026-02-27T19:05:54.255Z",
    "isPublic": true
  }
]

Overview

Executive Summary

Setup Snapshot

Evidence & Timeline

Evidence Ledger

Release & Crawl Timeline

Artifacts & Docs

Artifacts Archive

Docs & README

Free Mission Control for OpenClaw AI Agents

Install This Skill

More Skills by Asif2BD

🎯 Pick Your Setup Mode

☁️ Option A — Cloud Setup (Coming Soon)

🖥️ Option B — Self-Hosted (Local)

👁️ Option C — Demo (No Account)

What This Actually Is

📨 Telegram → Mission Control Auto-Routing

What Agents Can Do

What Humans See

Core mc Commands

MissionDeck.ai

Setup Guide — Self-Hosted Mission Control

Requirements

Step 1: Fork the Repository

Step 2: Clone and Install

Step 3: Configure Environment

Step 4: Start the Server

Step 5: Verify

Step 6: Add to OpenClaw Config

Running as a Service (Linux)

Updating

MissionDeck.ai Cloud Connection

What MissionDeck.ai Will Provide (When Live)

Setup Steps (For When Cloud API Is Available)

Step 1: Create an Account + Get Your API Key

Step 2: Connect Your Repo

Step 3: Verify Connection

What To Do Right Now (Cloud Not Available)

When Cloud Sync Is Available

mc CLI Reference

Task Management

Subtask Management

Deliverables

Agent Coordination

Connection Status

Common Patterns for Agents

Data Population Guide

Directory Structure

Step 1: Register Agents

Step 2: Create Initial Tasks

Task JSON Schema

Step 3: Verify Data

Bulk Import

Resetting Data

SECURITY.md — jarvis-mission-control

ClawHub Scan Result

False Positive Analysis

Pattern: git clone / npm install / node server/index.js

Pattern: bash scripts/connect-missiondeck.sh

Pattern: External service connection (MissionDeck.ai)

File Audit

Integrity Verification

Source Code

Free Mission Control for OpenClaw AI Agents

Install This Skill

More Skills by Asif2BD

🎯 Pick Your Setup Mode

☁️ Option A — Cloud Setup (Coming Soon)

🖥️ Option B — Self-Hosted (Local)

👁️ Option C — Demo (No Account)

What This Actually Is

📨 Telegram → Mission Control Auto-Routing

What Agents Can Do

What Humans See

Core mc Commands

MissionDeck.ai

Setup Guide — Self-Hosted Mission Control

Requirements

Step 1: Fork the Repository

Core `mc` Commands

`mc` CLI Reference

Pattern: `git clone` / `npm install` / `node server/index.js`

Pattern: `bash scripts/connect-missiondeck.sh`

Core `mc` Commands

`mc` CLI Reference

Pattern: `git clone` / `npm install` / `node server/index.js`

Pattern: `bash scripts/connect-missiondeck.sh`