Documentation

What is a runtime?

Understand the execution layer every ClawControl workspace needs before agents can do real work.

Short version

A runtime is the machine where your agents actually run. Without one, ClawControl can coordinate work, but it cannot execute it.

Why it matters

Agents need a connected runtime before they can do real work. That is why the onboarding flow asks you to connect a runtime before creating an agent.

What you should expect

After pairing a runtime, it should appear in the runtime list and show as connected. Once that happens, the runtime can reconcile the Mission Control plugin, report health, and support real agent execution.

How it fits into the product

In Starter, you connect your own OpenClaw host through a runtime.
In Pro, ClawControl can operate the OpenClaw infrastructure for you, but the runtime still exists as part of that managed environment.

In both cases, the runtime is the bridge between the ClawControl app and the machine that can actually run agent work.

When you need one

Before you create an agent that can execute work
Before you expect tasks to move through the board
Before you want runtime health, availability, and usage to mean anything

What to check after pairing

The runtime appears in your workspace
The runtime is active
The runtime shows as connected rather than offline