ClawSuite: a control plane for OpenClaw agents, and the gateway it cannot run without
All-in-one command center for OpenClaw agents
At a glance
- What is it?
- ClawSuite is a TypeScript PWA that puts orchestration, cost tracking and memory editing in front of an OpenClaw gateway. Its value is real but conditional: without a reachable OCPlatform gateway on port 18789, there is no product.
- Who is it for?
- Adopt ClawSuite if you already run an OCPlatform gateway and want a browser-based view of agent lifecycles, per-agent spend and memory files without building that UI yourself. Skip it if you have no gateway, need a hosted multi-tenant service, or want something that works offline from a single binary.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 116 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
The gap ClawSuite fills between an OpenClaw gateway and a terminal
OpenClaw agents run behind a gateway. The gateway handles connections and auth; it does not give you a dashboard. The README frames the project against that gap directly, describing ClawSuite as "not a chat wrapper" but a command center for orchestrating agents, running missions and tracking costs in one place. The intended user is someone who already has an OCPlatform gateway running and now needs to see what the agents attached to it are doing. That is a narrower audience than a general AI desktop app. The prerequisites make it explicit: Node.js 22 or newer, plus the gateway listening locally on port 18789. Nothing in the material suggests ClawSuite can act as a gateway itself, and the setup wizard that appears on first launch exists to connect to one, not to replace it.
What the v4.0.0 release actually changed
The release notes for v4.0.0 list five things worth separating from marketing language. Mission Control adds multi-agent orchestration with an isometric office view and a lifecycle of spawn, pause, resume and abort. Cost Analytics reports per-agent spend, daily trends, month-to-date totals and a projected end-of-month figure, which the notes say is backed by gateway data rather than local estimates. The theme system now covers 66 or more components across three named themes. Security work added auth middleware on API routes, removed a wildcard CORS policy, and introduced exec approval prompts so sensitive commands can be approved or denied in the UI. A memory browser lets you read, search and edit agent memory files from the interface. The security entry is the one that matters most for anyone exposing this beyond localhost, because a control plane that can spawn agents and approve shell commands is a high-value target.
How the pieces connect: browser, Next.js server, gateway
The data flow is short. Your browser loads the app on port 3000. The server side reads two environment variables and opens a WebSocket to the gateway. Agent output comes back over SSE, which the README contrasts with polling: live streaming to Mission Control and chat. That choice matters for cost visibility, because token streaming and spend reporting both depend on a persistent connection rather than periodic fetches. The gateway token is not configured inside ClawSuite; you retrieve it from the gateway's own config file at ~/.ocplatform/ocplatform.json under gateway.auth.token, or by running ocplatform config get gateway.auth.token. So ClawSuite holds no independent identity system for the gateway. It is a client with a bearer token, and every orchestration action you take in the UI is a request the gateway ultimately authorizes.
Getting it running: clone, env, npm run dev
The README gives a four-command install. Clone the repository, run npm install, copy .env.example to .env, then edit .env. Two keys are marked required. CLAWDBOT_GATEWAY_URL takes a WebSocket URL, with ws://127.0.0.1:18789 as the documented example. CLAWDBOT_GATEWAY_TOKEN takes the gateway auth token. After that, npm run dev starts the app on http://localhost:3000. Verification is deliberately plain: open the URL, and you should see the dashboard, or the setup wizard on a first run. A white screen means the gateway is not reachable or the .env values are wrong. Note the naming inconsistency in the material: the environment variables are prefixed CLAWDBOT_, the gateway is OCPlatform, and the product is ClawSuite. If you are grepping a codebase for configuration, that mismatch will cost you a few minutes.
Where ClawSuite stops being the right tool
The largest constraint is that ClawSuite is a front end with no fallback mode. If the gateway is down, the material offers no offline queue, no cached mission state and no local execution path. The white-screen troubleshooting note confirms the failure mode is total rather than degraded. The second constraint is deployment shape. This is a self-hosted server you run yourself, and mobile access is documented through Tailscale, which means the intended remote pattern is a private network rather than a public URL. The cloud and hosted offering is listed as coming soon, so multi-device session sync, team shared memory and webhook triggers are not available today. The native desktop app is also in development, and the README points you at the PWA install path in the meantime. If you need a single signed binary with tray integration, that does not exist yet in any released form.
How it compares with a general agent workspace
The closest category is a general-purpose agent workspace such as VS Code with an agent extension. The difference is what each one assumes. A code editor extension assumes the agent works on files in a repository you have open, and its state is the editor session. ClawSuite assumes agents are long-running processes attached to a gateway, and its state is the gateway's. That is why it has mission lifecycle controls (spawn, pause, resume, abort), per-agent spend reporting and a memory browser, and why it does not try to be an editor. The trade-off runs the other way too: ClawSuite gives you no code editing surface, so reviewing an artifact an agent produced means opening it elsewhere. If your work is mostly interactive coding, a gateway control plane adds a layer you will not use.
Licence, upgrade cost and what to check before adopting
The repository is MIT licensed, which permits commercial use and modification, but the material does not state how the gateway itself is licensed or distributed, and that is the dependency you actually run. Upgrading is a git pull plus npm install, unless the gateway protocol changes, in which case ClawSuite's WebSocket client is the piece that breaks. There is no version pinning guidance in the README and no compatibility matrix between ClawSuite releases and gateway versions, so track the CHANGELOG before pulling. The practical check is a two-step one: confirm ocplatform config get gateway.auth.token returns a value, then confirm the app loads the dashboard rather than the setup wizard. Everything else in the product depends on those two succeeding.
Editorial conclusion
Adopt ClawSuite if you already run an OCPlatform gateway and want a browser-based view of agent lifecycles, per-agent spend and memory files without building that UI yourself. Skip it if you have no gateway, need a hosted multi-tenant service, or want something that works offline from a single binary. Before committing, verify three things in your own environment: that the gateway answers on ws://127.0.0.1:18789, that the token in ~/.ocplatform/ocplatform.json matches what you put in CLAWDBOT_GATEWAY_TOKEN, and that every API route you expose through Tailscale is behind the auth middleware the v4.0.0 notes describe. If the gateway is not already part of your stack, ClawSuite is the wrong first install.
Community notes