Skip to main content
Use this page before you run Clawboo for anyone but yourself. It lists the defaults that decide who can reach the server, how much it accepts, what limits spending, and what leaves the machine, with how to change each one. Every other number, such as breaker thresholds and timeouts, is in Limits and defaults.

At a glance

The server reads environment variables when it starts, so restart it after you change one. Settings > System Health shows three of these defaults in its Production defaults card: the log level, the budget posture and observability.

Request limits

Clawboo counts requests per client address over a one-minute window, in memory. Over a limit it answers 429 with Too many requests. Wait a moment and retry., or on a sensitive route Too many requests for this operation. Wait a moment and retry., and sends standard RateLimit-* headers. The sensitive routes are the ones that install, connect, disconnect or sign out of a runtime; start a CLI sign-in; start, restart or stop the Hermes gateway; install, set up or edit OpenClaw, control its Gateway or approve a device; update Clawboo; connect, authorize, configure or disconnect a connector, add or remove a custom connector, or set the Composio key; change a native agent’s shell switch; revoke a command-allowlist entry; and reindex or install memory embeddings. The 60-a-minute limit applies on top of the general one. The address is the connection’s own, and forwarding headers are ignored. Behind a reverse proxy on the same machine, every request comes from 127.0.0.1, so all your users share one count. The dashboard’s page files have a separate limit of 3,000 a minute and do not count against the API.

Budgets

A fresh install has no budgets, so nothing caps spend. To set a ceiling, open Settings > Insights > Governance, create a budget for an agent or a team, and choose hard cap. When spend reaches the cap, the budget pauses and that scope gets no new work; how fast a running agent stops depends on its runtime. A warn only budget tracks spend against its limit and never stops work. See Budgets and spend for what each runtime reports and how a cap stops each kind of run. There is no install-wide cap. The API also accepts a tenant scope, but nothing charges or enforces it, and the Governance form does not offer it. Through the API, a new budget saved without a mode is warn only, and an existing one keeps its mode. System Health’s budget posture row always shows the shipped default, track-and-warn, not the budgets you create.

OpenTelemetry

Clawboo keeps traces in its local event log. To also send them to an OTLP collector, set OTEL_EXPORTER_OTLP_ENDPOINT (or OTEL_EXPORTER_OTLP_TRACES_ENDPOINT); OTEL_SERVICE_NAME defaults to clawboo. Traces cover runs that go through the task runner, which are agent routines and POST /api/runtimes/:id/run. Team chat turns produce none. The clawboo npm package does not include the OpenTelemetry SDK, so on an npm install the export does not start. System Health’s OTel exporter check then reports that the exporter failed to initialize, and traces stay local, even though the observability row reads that the exporter is active. Export works when you run Clawboo from a source checkout, where the SDK is installed.

What leaves the machine

Prompts go only to the providers and apps you connect. No Clawboo account, and Clawboo itself sends no telemetry. Besides your providers, the server makes three requests of its own. It fetches the Marketplace catalog from GitHub. It asks registry.npmjs.org for the latest Clawboo version when the dashboard checks for updates. And when the dashboard shows a model picker, it fetches OpenRouter’s public model list, which sends no key. In your browser, the dashboard also loads its font from Google Fonts and its GitHub star count from api.github.com.
Last modified on November 14, 2026