openclaw-dashboard and openclaw-trace
The first tool provides a dashboard to visualize data, while the second offers end-to-end tracing, making them complementary for observability within OpenClaw multi-agent systems.
About openclaw-dashboard
mudrii/openclaw-dashboard
A beautiful, zero-dependency command center for OpenClaw AI agents
Provides real-time operational visibility into OpenClaw AI agent deployments through 12 dashboard panels covering gateway health, cost breakdown (daily/monthly projections), cron job status, active sessions with token usage, and sub-agent activity — all refreshed automatically every 60 seconds. Built as a single Go binary backend with pure HTML/CSS/JS frontend, it polls OpenClaw's `/healthz`, `/readyz`, and `status --json` endpoints locally over HTTP, featuring 6 themeable interfaces, rate-limited natural-language chat queries, and per-metric CPU/RAM/disk thresholds. Designed specifically for multi-agent, multi-model OpenClaw setups running dozens of cron jobs across Telegram, Slack, Discord, and WhatsApp integrations.
About openclaw-trace
Tell-Me-Mo/openclaw-trace
End-to-end tracing and observability for OpenClaw multi-agent systems
Provides real-time dashboards and REST APIs for tracking token consumption, costs, and tool usage across OpenClaw agent sessions by parsing local JSONL files. Features budget monitoring with daily/monthly limits, 7-day historical trends, A/B heartbeat comparison, and optimization hints like cache hit rates and waste detection. Runs as a standalone Node.js server with no external dependencies, accessible at localhost:3141.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work