OpenClaw Dashboard CLI
A local one-page dashboard for OpenClaw agents: gateway, model costs, cron, sessions and sub-agents, with no login and no cloud.
- 462 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The dashboard reads OpenClaw gateway data, costs and configuration, and the server listens on a local port.
- With no login the page is open to anyone who reaches the port if it is exposed to the network.
Install
- Works in
Manual install
brew install mudrii/tap/openclaw-dashboardThen `openclaw-dashboard --refresh` creates `data.json` and `openclaw-dashboard` starts the server on port 8080; ready archives exist for macOS and Linux.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The dashboard reads OpenClaw gateway data, costs and configuration, and the server listens on a local port.
- With no login the page is open to anyone who reaches the port if it is exposed to the network.
This is third-party code. Review the repository files before installing.
What it does
OpenClaw Dashboard gathers in one browser window what serious OpenClaw use scatters across logs and commands: whether the gateway is running, how much was spent today and on which model, which cron jobs ran or failed and when the next fires, which sessions are active and how much context they use and what the sub-agents are doing. CPU load, memory, swap, disk, the OpenClaw version and the gateway are always visible on top. An alerts banner warns about high costs, failed cron jobs, full context and a stopped gateway. It is a single Go binary: `openclaw-dashboard --refresh` creates `data.json` and `openclaw-dashboard` starts a server at `http://localhost:8080`. The page refreshes once a minute and a `GET /api/refresh` request returns the cache and triggers a background refresh. A diagnostics section checks channels, models, plugins and skills, and gateway metadata is read from its lock file, so it works with Homebrew, binary, bun or source installs.
Who it is for. Those who run several OpenClaw agents with schedules and channels in Telegram, Slack and Discord and want costs and failures on one page.
Good fit when
- A quick look is needed at whether the gateway works and which model costs the most today.
- Some agent cron jobs fail and it must be clear which ones and when they fire again.
- Session context grows and it helps to spot which one is about to overflow.
- It must be clear what the sub-agents are doing and whether they have looped.
Not a fit when
- You do not use OpenClaw, and the dashboard reads its data and gateway.
- A replacement for the OpenClaw command line or the Telegram interface is needed, and the dashboard only shows an overview.
- Data must live in the cloud, and the dashboard works only locally.
Example request
Open the OpenClaw Dashboard and tell me how much we spent today, which model costs the most and which cron jobs failed.Limitations
The dashboard shows only an overview and does not replace the OpenClaw command line. It runs locally with no login and no cloud, so data is open to anyone who reaches port 8080 if you expose it to the network. The README notes that compatibility changes for the new OpenClaw runtime sit in the working tree with no release, and screenshots may show the earlier layout. Binaries are built for macOS and Linux on Intel, Apple Silicon and ARM. The last commit in the repository is from September 2026.
How to disable. Stop the server, run `brew uninstall openclaw-dashboard` (or delete the binary) and remove the directory with `config.json` and `data.json`.
FAQ
How do I install OpenClaw Dashboard?
Through Homebrew: `brew install mudrii/tap/openclaw-dashboard`. Ready archives exist for macOS and Linux (Intel, Apple Silicon, ARM64) with a checksum check.
How do I open the dashboard?
Run `openclaw-dashboard --refresh`, then `openclaw-dashboard`. The server listens at `http://localhost:8080` and `--port` sets the port.
Are a login or cloud needed?
No. The dashboard collects everything locally with no login or outside dependencies, and data stays in `data.json` on your machine.
What does the top bar show?
CPU load, memory, swap, disk, the OpenClaw version and gateway state. Color depends on configurable thresholds.
How often does data refresh?
The page refreshes once a minute. A `GET /api/refresh` request returns the `data.json` cache at once and triggers a background refresh when needed.
Discussion
No questions or reviews yet.
Related
CLI toolsA monitoring dashboard for OpenClaw agents: sessions, token and cost use, system load and scheduled jobs in one browser window
A bilingual CLI for OpenClaw: setup, checks, upgrades with a backup, repair and diagnostics from a single command
A CLI that runs Claude Code and Codex in isolated Docker containers with a firewall, worktrees and a no-Dockerfile image.
Claude Watch draws a localhost map of project logic, shows Claude Code tool calls live and answers questions
A local dashboard for Claude Code, Codex CLI, Gemini CLI, Copilot and OpenCode that shows tokens, cost, latency and errors
A Go CLI: plain-language questions to AWS, GCP, Azure, Cloudflare and Kubernetes, change plans and its own MCP server
README in short
An overview panel for OpenClaw: costs, cron, sessions and sub-agents in one window. A single Go binary with no dependencies, login or cloud.