Mission Control

What It Does

A real-time monitoring dashboard for OpenClaw agents running on Claude Max. A Python collector reads your session logs, cron jobs, and system stats every 60 seconds, writes a JSON file, and a single-page HTML dashboard auto-refreshes every 3 seconds. Glance at it for 2 seconds to check if everything's healthy, or sit and watch sessions, cron runs, and costs in real time.

What You See

Why It Matters

When you're running cron jobs, multiple sessions, and an always-on agent — you need to see what's happening. Not dig through logs. Not grep through JSONL. Just open a tab and know: are my crons healthy? How much quota have I used? Mission Control answers all of it without consuming a single API token.

What's Included

• SKILL.md — complete installation guide with 5 hard-won TUI scraper gotchas
• collect.py — Python data collector (~500 lines, zero dependencies beyond stdlib)
• index.html — single-page dashboard (~47KB, no framework, no build step)
• scrape_usage.py — Claude Max usage TUI scraper via pexpect
• collect.sh — shell wrapper for cron
• Configurable timezone, session names, Weave file list, and cost display

Why I Built This

I run dozens of cron jobs and multiple concurrent sessions. I had no idea what anything cost or how my resources were being used until I built this. I didn't know my Weave files were being truncated until the dashboard showed me they exceeded the default character limit. I didn't know gateway restarts were significantly more expensive than warm turns. The dashboard paid for itself on day one — in knowledge alone.

Architecture

┌─────────────┐    ┌──────────────┐    ┌───────────────┐
│  collect.py  │───▶│  state.json  │◀───│  index.html   │
│  (cron 60s)  │    │  (static)    │    │  (polls 3s)   │
└─────────────┘    └──────────────┘    └───────────────┘
┌─────────────────┐    ┌──────────────────┐
│ scrape_usage.py  │───▶│ usage-quota.json  │
│  (cron 5min)     │    │  (Max plan %)     │
└─────────────────┘    └──────────────────┘

No database. No WebSocket. No build step. The collector writes JSON, the dashboard reads JSON. Deploy behind any static file server with basic auth.

Security: Password-Protect Your Dashboard

Quick Start

# 1. Unzip and configure paths
unzip mission-control.zip -d /opt/dashboard/
vi /opt/dashboard/collect.py   # Edit SESSIONS_DIR, WORKSPACE, etc.

# 2. Set up crons
crontab -e
# Add:
# * * * * * /opt/dashboard/collect.sh > /dev/null 2>&1
# */5 * * * * PATH=/root/.local/bin:/usr/local/bin:/usr/bin:/bin HOME=/root timeout 45 python3 /opt/dashboard/scrape_usage.py

# 3. Set up a web server WITH PASSWORD PROTECTION
caddy hash-password --plaintext "pick-a-temp-password"
# Add to your Caddyfile:
# :8081 {
#     basicauth {
#         admin "$2a$14$YOUR_HASH_HERE"
#     }
#     root * /var/www/dashboard
#     file_server
#     header Cache-Control "no-cache, no-store"
# }
systemctl reload caddy

# 4. Open http://your-server:8081 (will prompt for password)