Runtime overview
Learn what the ClawControl runtime is, what it needs, and what it does once it is connected.
A runtime is the service that connects ClawControl to the machine where OpenClaw is running.
What the runtime does
Once installed and paired, the runtime helps ClawControl:
- identify and register the host machine
- maintain a live connection back to the app
- talk to the local OpenClaw gateway
- verify the machine is ready before starting work
- reconcile the Mission Control plugin and patch its runtime-side config
- report runtime health, linkage state, and software versions
What the runtime does not do
The runtime is not the same thing as the ClawControl app, and it is not the same thing as OpenClaw itself.
- It is not the main web application your team signs into.
- It is not the AI model provider.
- It is not the OpenClaw gateway.
- It is not the place where team members manage tasks directly.
Its job is to connect those parts together safely and reliably.
When you need a runtime
You need a runtime whenever you want ClawControl to coordinate a real OpenClaw environment.
That usually means:
- before you create your first working agent
- before you expect tasks to execute
- before runtime health or connectivity indicators mean anything
What the runtime expects
For a standard setup, the runtime expects:
- Node.js 20 or later
- an OpenClaw environment running on the host
- access to the OpenClaw gateway
- a gateway bootstrap token for first-time connection
- an auth-capable OpenClaw agent on the host so provider auth can be reused
The runtime reads these details during onboarding and configuration.
At the moment, provider auth still comes from the local OpenClaw side on the host machine rather than a generally available ClawControl-managed provider auth flow.
Supported service managers
The runtime can run in the foreground for testing, but the recommended setup is to install it as a background service:
- macOS:
launchd - Linux:
systemd --user
Files and paths you should know
| Item | Default location |
|---|---|
| Runtime config | ~/.clawcontrol/config.json |
| Runtime state directory | ~/.clawcontrol |
| macOS launchd log file | ~/.clawcontrol/logs/runtime.launchd.log |
| OpenClaw directory | ~/.openclaw |
On Linux, service logs are normally read through journald with
clawcontrol runtime logs.
Runtime readiness checks
Before a runtime is considered ready, ClawControl checks for basics such as:
- runtime pairing credentials
- gateway bootstrap access
- a selected auth base agent
- a readable
auth-profiles.jsonfile with at least one profile
The runtime also reports service, readiness, and linkage details through
clawcontrol runtime status and clawcontrol doctor so operators can see
whether the machine is healthy enough to trust.
If something is missing, clawcontrol doctor tells you what to fix.