What you are running
Clawboo is one Node.js program. It serves the dashboard and the REST API on one port, hosts Clawboo’s MCP servers, and keeps its data in a SQLite file in~/.clawboo. Clawboo Native agents run inside that program. Claude Code and Codex run as programs it starts on the same machine, Hermes agents run in one Hermes gateway it starts and watches there, and OpenClaw agents run in the OpenClaw Gateway.
In this section
The default posture
- Only this machine can connect. The server listens on
127.0.0.1until you setHOST. - The dashboard is locked with an access token. The first start makes a per-install token in
~/.clawboo/access-token, readable only by you, unless you setSTUDIO_ACCESS_TOKENyourself.STUDIO_ACCESS_TOKEN=set blank turns it off; then anyone who can reach the server can use it, and withHOSTset to anything but a loopback address the server refuses to start, but a reverse proxy on the same machine does not trip that check. - Browsers must use a local address. The same-origin guard rejects API calls that arrive under another name, such as your proxy’s domain, until you list it in
CLAWBOO_ALLOWED_HOSTSandCLAWBOO_ALLOWED_ORIGINS. - State lives in
~/.clawboo, and agents’ work in~/clawboo-work. Clawboo also writes provider keys and OpenClaw settings in OpenClaw’s~/.openclawfolder. - Spend is tracked, not capped. Budgets warn by default. A hard cap is something you turn on.
Related
- CLI reference: start, stop and restart the server, find its port, and read its log.
- Environment variables: every variable the server reads.
- Limits and defaults: every number, timeout and cap in one place.
- Troubleshooting: error messages and what to do about each one.