openclaw-mission-control and clawd-control
Both are standalone dashboards for monitoring different AI agent systems (OpenClaw vs Clawdbot), making them **competitors** — they serve the same use case but cannot be used together since they interface with incompatible agent orchestration backends.
About openclaw-mission-control
abhi1693/openclaw-mission-control
AI Agent Orchestration Dashboard - Manage AI agents, assign tasks, and coordinate multi-agent collaboration via OpenClaw Gateway.
Provides unified visibility and approval-driven governance for multi-team agent operations, with built-in activity audit trails and human-in-the-loop execution controls. Supports both Docker and local deployments with dual authentication modes (bearer token and Clerk JWT), exposing the same operational model through web UI and API-first interfaces. Gateway-aware architecture enables distributed runtime control across local and remote execution environments while maintaining a single system of record for organizations, boards, tasks, and approval workflows.
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