01
One fleet, clear boundaries
See every connected Gateway in one place while keeping its agents, placement, runtime, and identity distinct.
fleetMorrowScruffyZoidberg
OpenClaw / fleet view
A map for work in motion.
Clawtop keeps the shape of a distributed OpenClaw fleet in view: Gateways, agents, sessions, child runs, and the signal trail that connects them.
$ self-hosted · multi-Gateway · read-only
clawtop / fleet● live
FLEET / 03 GATEWAYS
18active sessions+4 today
MorrowLantern7 sessions
ScruffyUnraid8 sessions
ZoidbergMac Mini3 sessions
GATEWAYS→AGENTS→SESSIONS→CHILD RUNS→HISTORY
The useful middle layer
More context than a log.
Less noise than a console.
When work spans multiple Gateways, the hard part is knowing what belongs together. Clawtop turns scattered activity into a calm, navigable view without taking control of anything.
Follow the signal ↘02
Follow the work
Parent sessions expose their direct and nested child runs, so a busy thread still has a shape.
◉ Clawtop Development└─ ◆ website build└─ ◇ visual review
03
Useful signal, safely projected
Activity, progress, placement, and history—without retaining prompts, credentials, or raw payloads.
✓ read-only access✓ sanitized activity✓ server-side credentials
“
It’s the difference between asking ‘is it working?’ and knowing where the work is.Clawtop / OpenClaw fleet monitor
Bring your own surface
Built to run
where your fleet runs.
Clawtop is a small self-hosted Node service. Connect it to one or more OpenClaw Gateways, put it behind your trusted network, and keep the view close to the work.
Read the setup guide ↗quick startbash
$ git clone github.com/kylejschultz/clawtop
$ cd clawtop
$ npm ci
$ npm run dev
◌ connecting to your fleet...
✓ Clawtop is ready