openclaw control center Skill by [ara.so](https://ara.so) — Daily 2026 Skills collection OpenClaw Control Center transforms OpenClaw from a black box into a local, auditable control center. It provides visibility into agent activity, token spend, task execution chains, cross session collaboration, memory state, and document sources — with security first defaults that keep all mutations off by default. What It Does Overview : System health, pending items, risk signals, and operational summary Usage : Daily/7d/30d token spend, quota, context pressure, subscription window Staff : Who is actively executing vs. queued — not just "has tasks" Collaboration : Parent child session handoffs and verified cross session messages (e.g. Main ⇄ Pandas ) Tasks : Task board, approvals, execution chains, run evidence Memory : Per agent memory health, searchability, and source file editing Documents : Shared and agent core documents opened from actual source files Settings : Connector wiring status, security risk summary, update status Installation Open: http://127.0.0.1:4310/?section=overview&lang=zh http://127.0.0.1:4310/?section=overview&lang=en Use npm run dev:ui over UI MODE=true npm run dev — more stable, especially on Windows shells. Project Structure Critical constraint : Only modify files inside control center/ . Never modify ~/.openclaw/openclaw.json . Environment Configuration Copy .env.example to .env and configure: Security Flag Meanings Flag Default Effect READONLY MODE true All state changing endpoints disabled LOCAL TOKEN AUTH REQUIRED true Import/export and write APIs require local token IMPORT MUTATION ENABLED false Import mutations blocked entirely IMPORT MUTATION DRY RUN false Dry run mode for imports when enabled APPROVAL ACTIONS ENABLED false Approval actions hard disabled APPROVAL ACTIONS DRY RUN true Approval actions run as dry run when enabled Key Commands TypeScript Code Examples Connecting to the Runtime Monitor Reading Agent Staff Status Tracing Cross Session Collaboration Fetching Token Usage and Spend Reading Memory State Checking Wiring Status Approving Tasks (Gated Endpoint) UI Section Navigation Navigate via query params: Sections: overview usage staff collaboration tasks memory documents settings Languages: zh (Chinese, default) en (English) Integration Patterns Embedding in an Existing OpenClaw Workflow If your OpenClaw agent needs to hand off instructions to the control center for setup, use the documented install block: Adding a Custom Connector All connectors live in control center/src/runtime/connectors/ . Follow this pattern: Custom UI Section Troubleshooting "Missing src/runtime" or "Missing core source" This almost always means the working directory is wrong: If cloned correctly but still missing: the clone was incomplete. Re clone: UI Doesn't Start / Port Conflicts Data Not Showing (Partial or Empty Sections) 1. Open Settings → 接线状态 (Wiring Status) — it lists exactly which connectors are connected, partial, or missing. 2. Common causes: OPENCLAW GATEWAY URL not set or wrong port OPENCLAW HOME doesn't point to actual ~/.openclaw OpenClaw subscription snapshot not at default path Token Auth Failures Approval Actions Silently Do Nothing Check your .env : Both must be explicitly set. Default is disabled + dry run. Memory Section Shows Inactive Agents The memory section is scoped to agents listed in openclaw.json . If deleted agents still appear: Remove stale entries from openclaw.json — the memory section will update on next load. Windows Shell Issues Prefer npm run dev:ui over UI MODE=true npm run dev . Cross env variable setting behaves differently in PowerShell/CMD. The dev:ui script handles this internally. Prerequisites Node.js + npm A running OpenClaw installation with accessible Gateway Read access to ~/.openclaw on the local machine (Optional) ~/.codex and OpenClaw subscription snapshot for full usage data

openclaw-control-center