claw-dashboard CLI
The clawdash terminal panel shows an OpenClaw gateway: sessions, schedule, activity feed and log on one screen, read-only
- 122 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The panel reads the gateway token from `~/.openclaw/openclaw.json` and creates a device key under `~/.openclaw/clawdash/`.
- Read-only rights: the `operator.read` role.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/claw-dashboardDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The panel reads the gateway token from `~/.openclaw/openclaw.json` and creates a device key under `~/.openclaw/clawdash/`.
- Read-only rights: the `operator.read` role.
This is third-party code. Review the repository files before installing.
What it does
The `clawdash` command connects to a local OpenClaw gateway over WebSocket and draws a terminal panel. The header shows the gateway version, uptime, session count, token throughput per minute and an estimated cost for the day. Below is a session list with status, model, context pressure and age, with subagents nested under the parent, plus an activity feed and a cron schedule with countdowns and error streaks. A gateway log tail with a level filter runs along the bottom. The `--once` flag prints a plain-text snapshot for scripts and smoke tests. The command reads the port and token from `~/.openclaw/openclaw.json`; `--port` and `--token` override them.
Who it is for. People who run OpenClaw agents on their own machine and watch sessions, token use and scheduled jobs.
Good fit when
- You want to see which gateway sessions and subagents run now and how much context they use.
- A cron job failed and you need its countdown and error streak.
- The gateway log is easier to read with a level filter than in a raw file.
- A script needs a state snapshot: `clawdash --once` prints it as text.
Not a fit when
- The OpenClaw gateway is older than 2026.11 or uses another protocol: the panel targets protocol v4.
- You need to stop sessions or run jobs: the panel only reads.
- You want a web page in a browser: `clawdash` draws its interface in the terminal.
Example request
Run `clawdash --once` and tell me which gateway sessions are running and which cron job failed in its latest runs.Limitations
It needs Node.js 22.19 or newer (the built-in WebSocket is used) and a local OpenClaw gateway 2026.11 with protocol v4. On first connect the command creates an Ed25519 device key in `~/.openclaw/clawdash/device.json` and pairs itself, which is auto-approved on loopback. The connection role is `operator.read`, so the panel cannot write anything to the gateway. Sessions are polled every 15 seconds, cron every 30, usage data every 15 minutes, and the cost in the header is only an estimate. The README screenshot is still a placeholder.
How to disable. Remove the package with `npm uninstall -g claw-dashboard`. The device key sits in `~/.openclaw/clawdash/device.json`; delete it manually if you no longer need the panel.
FAQ
How do I install and run clawdash?
Run `npm i -g claw-dashboard`, then `clawdash` for the full panel or `clawdash --once` for a text snapshot. The OpenClaw gateway has to run on this machine.
Can the panel stop a session or run a cron job?
No. It connects with the `operator.read` role and only reads: it aborts, runs and writes nothing.
What should I do about `no gateway token`?
Set `gateway.auth.token` in `~/.openclaw/openclaw.json` or pass the token with `--token`.
What does `device signature invalid` mean?
The machine clock is far off or the device key was re-issued on the gateway side. Delete `~/.openclaw/clawdash/device.json` and reconnect: the panel pairs again.
Which keys does the panel have?
`j` and `k` or arrows move the selection, `tab` switches sessions and automations, `enter` opens the session chat history, `l` cycles the log filter, `a` keeps only errors in the feed, `r` refreshes, `q` quits.
Discussion
No questions or reviews yet.
Related
CLI toolsClawMetry reads the session files agents already write and shows the timeline, tool calls, tokens and cost in one dashboard.
The clawctl CLI manages a fleet of AI agents on local machines over SSH and Ansible: install, start, upgrade and token tracking.
A CLI that connects local agents to a shared cloud store of sessions, memory, skills and MCP connectors.
A CLI agent swarm: a leader spawns workers in separate git worktrees, and they share tasks and exchange messages via files.
One runtime for Claude Code, Codex, OpenCode and more: a run counts as done only when checks the agent did not write pass
Open-source personal AI assistant on your own machine: answers in Telegram, Slack, Discord and WhatsApp, extended with skills and plugins
README in short
The panel is written small: no runtime dependencies, Node built-ins only. It keeps a single connection, polls sparingly and reconnects with backoff.