#5353rd of 53 in Gateways and observability

openclaw-control-center

Local dashboard for monitoring and coordinating an existing OpenClaw agent setup

Stars
4k
License
MIT
Last commit
Apr 2026
Language
TypeScript
Stars, last 29 weeks+285
22 Apr 2026: 3,713 stars29 Apr 2026: 3,776 stars6 May 2026: 3,816 stars13 May 2026: 3,846 stars20 May 2026: 3,866 stars27 May 2026: 3,881 stars3 Jun 2026: 3,890 stars10 Jun 2026: 3,900 stars17 Jun 2026: 3,907 stars24 Jun 2026: 3,915 stars1 Jul 2026: 3,924 stars8 Jul 2026: 3,928 stars15 Jul 2026: 3,933 stars22 Jul 2026: 3,935 stars29 Jul 2026: 3,939 stars5 Aug 2026: 3,946 stars12 Aug 2026: 3,949 stars19 Aug 2026: 3,958 stars26 Aug 2026: 3,961 stars2 Sept 2026: 3,964 stars9 Sept 2026: 3,967 stars16 Sept 2026: 3,970 stars23 Sept 2026: 3,973 stars30 Sept 2026: 3,977 stars7 Oct 2026: 3,982 stars14 Oct 2026: 3,987 stars21 Oct 2026: 3,989 stars28 Oct 2026: 3,991 stars4 Nov 2026: 3,995 stars11 Nov 2026: 3,998 stars

3,713 on 22 Apr 20263,998 on 11 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

A TypeScript web UI that reads an existing OpenClaw installation and shows health, usage and spend, staff activity, tasks, approvals, documents and agent memory. A Collaboration page lets agents discuss, assign, hand off and review work in one shared thread, dispatched through the real `openclaw agent` runtime. It starts read-only with local token auth and mutation routes disabled.

Who it is for: OpenClaw users who want a local dashboard for usage, tasks and agents

Strengths

  • Safe defaults: read-only mode, local token auth, mutation and approval actions disabled
  • Uses the live OpenClaw roster from openclaw.json; no agent renaming needed
  • Usage page covers spend, subscription windows, and per-session context pressure
  • Dockerfile and compose example included, plus build, test and smoke scripts

Weaknesses

  • Works only with OpenClaw; not a dashboard for other agent stacks
  • Requires a running OpenClaw Gateway and read access to its home directory
  • No tagged releases; installed from a git clone with npm
  • Docker needs OpenClaw data paths mounted and Gateway URL wired by hand

What it needs

  • no GPU
  • Docker + Compose
  • Needs OpenClaw, OpenClaw Gateway, Node.js, npm
  • port 4310

Also in Gateways and observability

See all 53
Also in Gateways and observability
RankProjectScore
1OmniRouteLLM gateway routing one OpenAI-compatible endpoint across 372 providers86.8k stars+11,398 (+15%) in 30 daysMIT96 out of 100
2headroomCompresses tool outputs, logs and history before they reach the LLM79.5k stars+4,550 (+6.1%) in 30 daysApache-2.092 out of 100
3new-apiGateway that unifies LLM providers behind OpenAI, Anthropic and Gemini APIs51.8k 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.8k starsApache-2.091 out of 100
#5LiteLLMOpenAI-format gateway and Python SDK for calling 100+ LLM providers63.2k starscustom license88 out of 100