Summary

This project offers a lightweight, real-time web dashboard for monitoring and managing multiple OpenClaw agents across platforms like Feishu and Discord. It simplifies complex operations by providing a unified view of agent status, model usage, and platform connectivity, enabling real-time testing and oversight without a database. It's designed for users managing distributed OpenClaw agent networks, enhancing operational visibility and control.

How It Works

The dashboard directly reads local OpenClaw configuration (~/.openclaw/openclaw.json) and session files, eliminating database dependencies. Built with Next.js, TypeScript, and Tailwind CSS, it features a clean UI and a novel animated "Pixel Office" that visually represents active agents as characters, adding an engaging element to system monitoring.

Quick Start & Requirements

• Installation: Clone the repo, run npm install, then npm run start. Access at http://localhost:3000. Docker deployment is also available.
• Prerequisites: Node.js 18+ and an OpenClaw installation with config at ~/.openclaw/openclaw.json.
• Configuration: Custom OpenClaw paths via OPENCLAW_HOME env var. Operator API access requires OPENCLAW_OPERATOR_TOKEN or OPENCLAW_ALLOW_UNAUTHENTICATED_LOCAL_OPERATOR_UI=true (local dev only).
• Links: Quick Start Guide (mentioned), MiniMax API Reference.

Highlighted Details

• Bot Overview: Card wall with agent status, model, platform bindings, and gateway health.
• Model & Session Management: Detailed lists of models and sessions with status and token usage.
• Performance Statistics: SVG charts for token consumption and response time trends.
• Integrated Features: Skill management, alerts with Feishu notifications, real-time gateway health, and one-click platform connectivity tests.
• Customization: Configurable refresh intervals, dark/light themes, i18n (EN/ZH), and animated "Pixel Office" visualization.

Maintenance & Community

Contact details include Xiaohongshu and WeChat (xmanr123). No explicit community channels or roadmap are provided in the README.

Licensing & Compatibility

The README does not specify a software license. This omission requires further investigation for adoption decisions, especially concerning commercial use or integration with closed-source projects.

Limitations & Caveats

Built-in metadata currently supports only one LLM provider (MiniMax). Operator API security requires careful configuration for local development, with unauthenticated access strictly limited to trusted local environments.