#5050th of 57 in Gateways and observability

openclaw-bot-review

Web dashboard for monitoring OpenClaw agents, models, sessions and token usage

Stars
2k
License
MIT
Last commit
Jul 2026
Last release
Jul 2026
Language
TypeScript
Stars, last 29 weeks+197
25 Apr 2026: 1,828 stars2 May 2026: 1,848 stars9 May 2026: 1,864 stars16 May 2026: 1,876 stars23 May 2026: 1,888 stars30 May 2026: 1,910 stars6 Jun 2026: 1,918 stars13 Jun 2026: 1,926 stars20 Jun 2026: 1,934 stars27 Jun 2026: 1,938 stars4 Jul 2026: 1,944 stars11 Jul 2026: 1,949 stars18 Jul 2026: 1,974 stars25 Jul 2026: 1,977 stars1 Aug 2026: 1,981 stars8 Aug 2026: 1,984 stars15 Aug 2026: 1,987 stars22 Aug 2026: 1,993 stars29 Aug 2026: 1,994 stars5 Sept 2026: 1,996 stars12 Sept 2026: 1,999 stars19 Sept 2026: 2,001 stars26 Sept 2026: 2,002 stars3 Oct 2026: 2,007 stars10 Oct 2026: 2,011 stars17 Oct 2026: 2,016 stars24 Oct 2026: 2,017 stars31 Oct 2026: 2,020 stars7 Nov 2026: 2,022 stars14 Nov 2026: 2,025 stars

1,828 on 25 Apr 20262,025 on 14 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

A Next.js dashboard that reads ~/.openclaw/openclaw.json and local session files to show OpenClaw agents, their models, platform bindings (Feishu, Discord), sessions and gateway health. It adds token and response-time charts, connectivity tests, Feishu alert rules, and an animated pixel-art office where agents appear as characters. No database is used.

Who it is for: OpenClaw users running several agents who want a status and usage view

Strengths

  • No database; derives everything from the OpenClaw config and local session files
  • Per-model, per-session and per-platform connectivity tests from the UI
  • Token and response-time charts with daily, weekly and monthly views
  • Operator write APIs require a token by default

Weaknesses

  • Only works with OpenClaw; needs its config at ~/.openclaw/openclaw.json or OPENCLAW_HOME
  • Alert notifications are delivered only through Feishu
  • Built-in model metadata lists only MiniMax models
  • Docker run needs the OpenClaw directory mounted to read real config

What it needs

  • no GPU
  • Docker
  • Needs OpenClaw, Node.js 18+
  • Models: MiniMax-M2.7, MiniMax-M2.7-highspeed, OpenAI-compatible providers via OpenClaw config
  • port 3000

What changed

From the release notes. No flag means the note does not say so, not that the upgrade is safe.

Also in Gateways and observability

See all 57
Also in Gateways and observability
RankProjectScore
1OmniRouteLLM gateway routing one OpenAI-compatible endpoint across 372 providers88.5k starsMIT96 out of 100
2headroomCompresses tool outputs, logs and history before they reach the LLM79.9k starsApache-2.092 out of 100
3new-apiGateway that unifies LLM providers behind OpenAI, Anthropic and Gemini APIs52.1k starsAGPL-3.0known advisory in latest version91 out of 100
#4MLflowTracing, evaluation and prompt registry for LLM apps, plus ML tracking Live demo ↗ (opens in a new tab)28.9k starsApache-2.091 out of 100
#5LiteLLMOpenAI-format gateway and Python SDK for calling 100+ LLM providers63.5k starscustom license88 out of 100