openclaw-dashboard and clawd-control
Both are dashboards for managing AI agents, with **mudrii/openclaw-dashboard** specifically for OpenClaw AI agents and **Temaki-AI/clawd-control** for Clawdbot AI agents, making them competitors if you are deciding between the OpenClaw and Clawdbot ecosystems, but otherwise complementary for users who need to monitor agents within their respective ecosystems.
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 clawd-control
Temaki-AI/clawd-control
🏰 Real-time dashboard for monitoring and managing Clawdbot AI agents
Provides live fleet monitoring via Server-Sent Events, auto-discovers local Clawdbot agents, and offers deep agent introspection including session history and configuration management. Built as a deliberately minimal Node.js server with vanilla HTML/JS frontend and no build tooling, communicating with Clawdbot agents via WebSocket and polling their metrics at configurable intervals. Supports both local auto-discovery and manual remote agent configuration with token-based authentication.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work