openclaw-command-center

🦞 OpenClaw Command Center

English | 简体中文

Mission control for your AI agents

Features • Quick Start • Security • Configuration

---

Standalone monitoring, recommended companion

Human-readable costs and channels

Click Est. API Cost to enter a monthly spend baseline for the savings scenario. The baseline is stored only in this browser and dashboard path; no plan price is assumed. The selected calendar-day average is projected to 30 days and compared with your baseline. Include subscription and API spending for the same scope. Incomplete pricing stays marked partial, and negative differences are displayed. This is a what-if comparison, not realized savings or a billing forecast.

Channel names come from OpenClaw's native directory, cached per provider/account for five minutes. Channel IDs remain in session-title and cost-breakdown tooltips. Unknown channels have an explicit generic label; stale cached names retain their status in the tooltip. No workspace-specific channel map or provider credentials are embedded in the dashboard. Directory reads are bounded and asynchronous.

Cron Jobs lists OpenClaw automations through its read-only CLI API, cached for 30 seconds. Loading, partial and stale catalogs are labeled; missing legacy JSON files no longer imply zero automations. AI Jobs is a separate optional provider: without it the page shows "not connected", not an empty successful job catalog.

Command Center works out of the box without Spacesuit. It owns OpenClaw sessions, health, jobs, usage and the common dashboard. For a minimal core-only view, run COMMAND_CENTER_MODE=core npm start.

Spacesuit is the highly recommended companion for per-agent flavors, domain panels and workflows. Spacesuit can scaffold a workspace and collect data by itself, but it has no graphical human–agent interaction surface of its own; Command Center provides the dashboard and supported controls. The extension system does not add a chat composer.

The read-only extension API loads explicit, profile-bound Spacesuit snapshots through the existing state feed. Legacy built-in domain panels remain the default compatibility mode until you select a flavor or core-only mode; existing panels and data are not silently removed. See the ownership and migration plan.

Why Command Center?

Your AI agents are running 24/7. You need to know what they're doing.

Command Center gives you real-time visibility into your OpenClaw deployment — sessions, costs, system health, scheduled tasks — all in one secure dashboard.

⚡ Fast

• Single API call — unified state endpoint, not 16+ separate requests
• 2-second updates — real-time SSE push, not polling
• 5-second cache — backend stays responsive under load
• Instant startup — no build step, no compilation

🪶 Lightweight

• Zero dependencies for users — just Node.js
• ~200KB total — dashboard + server
• No webpack/vite/bundler — runs directly
• No React/Vue/Angular — vanilla JS, works everywhere

📱 Responsive

• Desktop & mobile — works on any screen size
• Dark mode — easy on the eyes, Starcraft-inspired
• Live updates — no manual refresh needed
• Offline-friendly — graceful degradation

🔧 Modern

• ES Modules — clean component architecture
• SSE streaming — efficient real-time updates
• REST API — integrate with your tools
• TypeScript-ready — JSDoc types included

🔒 Security (Most Important)

Command Center takes security seriously:

Feature	Description
Auth Modes	Token, Tailscale, Cloudflare Access, IP allowlist
No external calls	Dashboard runs 100% locally — no telemetry, no CDNs
Localhost default	Binds to 127.0.0.1 by default
Read-only by default	View your agents without exposing control
No secrets in UI	API keys, tokens never displayed
Audit logging	Know who accessed what, when

# Secure deployment example (Tailscale)
DASHBOARD_AUTH_MODE=tailscale node lib/server.js
# Only users on your Tailscale network can access

---

Features

Feature	Description
📊 Session Monitoring	Real-time view of active AI sessions
⛽ LLM Fuel Gauges	Token usage, costs, quota remaining
💻 System Vitals	CPU, memory, disk, temperature
⏰ Cron Jobs	View and manage scheduled tasks
🧠 Cerebro Topics	Automatic conversation tagging
👥 Operators	Who's talking to your agents
📝 Memory Browser	View agent memory files
🔒 Privacy Controls	Hide sensitive topics for demos/screenshots
💰 Cost Breakdown	Detailed per-model cost analysis
📈 Savings Projections	Monthly cost vs. manual estimates

---

Quick Start

npx clawhub@latest install command-center
cd skills/command-center
node lib/server.js

Dashboard runs at http://localhost:3333 🎉

git clone https://github.com/jontsai/openclaw-command-center
cd openclaw-command-center
node lib/server.js

---

Zero-Config Experience

Command Center auto-detects your OpenClaw workspace:

1. $OPENCLAW_WORKSPACE environment variable
2. ~/.openclaw-workspace or ~/openclaw-workspace
3. Common names: ~/molty, ~/clawd, ~/moltbot

If you have memory/ or state/ directories, you're good to go.

---

Optional System Dependencies

Command Center requires only Node.js to run. However, some system vitals features benefit from optional packages. Without them, the dashboard still works — those metrics simply show zeros or fall back gracefully.

OS	Package	Purpose	Install	Without It
Linux	sysstat	Disk I/O vitals (IOPS, throughput)	sudo apt install sysstat	Disk stats show zeros
Linux	lm-sensors	Additional temperature sensors	sudo apt install lm-sensors	Uses thermal_zone (usually works)
macOS (Intel)	osx-cpu-temp	CPU temperature	Build from source	Battery temp fallback
macOS (Apple Silicon)	passwordless sudo	CPU temperature via powermetrics	Configure in sudoers	Shows note in UI

Command Center logs hints for missing optional dependencies once at startup.

---

Configuration

Environment Variables

Variable	Description	Default
PORT	Server port	3333
OPENCLAW_WORKSPACE	Workspace root	Auto-detect
OPENCLAW_PROFILE	Profile name	(none)

🔒 Authentication

Mode	Use Case	Config
none	Local dev	DASHBOARD_AUTH_MODE=none
token	API access	DASHBOARD_AUTH_MODE=token DASHBOARD_TOKEN=secret
tailscale	Team access	DASHBOARD_AUTH_MODE=tailscale
cloudflare	Public deploy	DASHBOARD_AUTH_MODE=cloudflare
allowlist	IP whitelist	DASHBOARD_AUTH_MODE=allowlist DASHBOARD_ALLOWED_IPS=...

📋 Recommended OpenClaw Settings

For the best Command Center experience, configure your OpenClaw gateway:

Slack Threading (Critical)

Enable threading for all messages to get proper topic tracking:

# In your OpenClaw config (gateway.yaml or via openclaw gateway config)
slack:
  capabilities:
    threading: all # Options: all, dm, group, none

Why this matters: Without threading, the dashboard can't track conversation topics properly. Each thread becomes a trackable unit of work.

Session Labels

Use descriptive session labels for better dashboard visibility:

sessions:
  labelFormat: "{channel}:{topic}" # Customize as needed

Cerebro (Topic Tracking)

Enable Cerebro for automatic conversation tagging:

# Initialize Cerebro directories
mkdir -p ~/your-workspace/cerebro/topics
mkdir -p ~/your-workspace/cerebro/orphans

The dashboard will automatically detect and display topic data.

---

Multi-Profile Support

Running multiple OpenClaw instances?

# Production dashboard
node lib/server.js --profile production --port 3333

# Development dashboard
node lib/server.js --profile dev --port 3334

---

API

Command Center exposes a REST API:

Endpoint	Description
GET /api/state	Unified state — all dashboard data in one call
GET /api/health	Health check
GET /api/vitals	System metrics
GET /api/sessions	Active sessions
GET /api/events	SSE stream for real-time updates

---

Architecture

command-center/
├── lib/
│   ├── server.js           # HTTP server + API
│   ├── config.js           # Configuration
│   └── jobs.js             # Cron integration
├── public/
│   ├── index.html          # Dashboard UI
│   └── js/                 # Components (ES modules)
└── scripts/
    ├── setup.sh            # First-time setup
    └── verify.sh           # Health check

---

🚀 Coming Soon

Advanced Job Scheduling

Building on OpenClaw's native cron system with intelligent scheduling primitives:

Primitive	Description
run-if-not	Skip if job already running (dedupe)
run-if-idle	Only execute when system capacity available
run-after	Dependency chains between jobs
run-with-backoff	Exponential retry on failure