
from OpenClaw Command Center238
A local dashboard for monitoring OpenClaw AI sessions, resource vitals, model usage and cost insights; run locally or deploy for remote teams.
An operational dashboard that centralises OpenClaw agent sessions, model usage, system vitals, scheduled cron jobs, and cost tracking. It provides live session monitoring (SSE), health endpoints, and role-based authentication modes so teams can run or demo agent fleets safely.
Use this skill when you need real-time visibility into agent activity, want to track LLM consumption and costs, or need a local/remote dashboard to manage scheduled tasks and privacy controls during demos. Useful for debugging agent behavior, capacity planning, and demo environments.
Likely compatible with OpenClaw agents and tooling that emit session events and model usage metrics (Claude, Codex, Ollama, OpenAI-friendly integrations).
OpenClaw Command Center is a local dashboard for monitoring AI sessions, LLM usage, system vitals, and cost tracking. The skill has 12 scripts covering setup, start/stop, verification, release, tmux dashboard, and Node.js modules for Linear sync and topic classification. Scripts are well-written with good error handling but most fail in DRY_RUN isolation due to missing runtime dependencies (server.js, config files, npm packages). Only stop.sh ran successfully. No security concerns found.
node module: ../src/config (linear-sync.js)node module: lib/server.js (server core)config/system-deps.jsontmux (for tmux-dashboard.sh)Well-architected skill for a real product (OpenClaw Command Center). Good documentation, clear separation of concerns, proper error handling. The scripts are operational tools for a dashboard product rather than agent-task scripts, which explains why most fail in DRY_RUN isolation. No security red flags. The pkill in stop.sh is slightly aggressive but acceptable for a stop script.