Managed runners are in private beta. Contact us for access.
Runner Management
Managed runners are secure OpenClaw containers that run AI agents in isolated sandbox environments. The dashboard provides a full lifecycle management interface — create, configure, monitor, and destroy runners without touching the command line.
Runner Lifecycle
Runners follow a state machine lifecycle:
Creating → Provisioning → Running → Stopping → Stopped → Destroying → Destroyed
↓
Errored| State | Description |
|---|---|
| Creating | Runner record created, container image selected |
| Provisioning | Container starting, OpenClaw booting, governance agent injecting |
| Running | Container ready, accepting messages and executing tasks |
| Stopping | Graceful shutdown in progress |
| Stopped | Container paused, can be restarted |
| Errored | Something went wrong, check logs |
| Destroyed | Container removed, resources freed |
Creating a Runner
From the dashboard sidebar, navigate to Runners and click Create Runner.
Configuration options:
| Option | Description | Default |
|---|---|---|
| Name | Human-readable runner name | Auto-generated |
| Runbook | Container image runbook | openclaw-base |
| Tool Profile | Tools available to the agent | messaging |
| Session Budget | Per-session cost limit (USD) | Org default |
| Idle Timeout | Auto-stop after inactivity | 30 minutes |
Runbooks:
| Runbook | Tools | Use Case |
|---|---|---|
openclaw-base | Shell, git, filesystem | General development tasks |
openclaw-web | Playwright, MCP, browser | Web automation and scraping |
openclaw-locked | Data processing only | Secure data analysis (no tools) |
Tool profiles:
| Profile | Capabilities |
|---|---|
messaging | Chat only — no shell, no filesystem |
standard | Chat + filesystem + git |
full | Chat + filesystem + git + shell + browser |
Monitoring Runners
The runner detail page shows:
- Status — current lifecycle state with uptime
- Resource usage — CPU, memory, disk consumption
- Session logs — real-time log streaming
- Cost tracker — cumulative session cost vs budget
- Activity feed — agent actions, tool calls, messages
Desktop Streaming (private beta)
Desktop streaming is in private beta and only available on managed runners with the desktop tool profile (not BYOVM machines you control). Contact us for access.
For runners with browser or desktop capabilities, click Desktop to view the runner’s screen in real-time via VNC. Supports:
- Live screen viewing (up to 2 concurrent viewers)
- Mouse and keyboard input
- Region screenshots for debugging
Managing Multiple Runners
The Runners list page shows all runners with:
- Status indicators (green = running, yellow = provisioning, red = errored)
- Cost per runner (cumulative session cost)
- Last activity timestamp
- Quick actions (start, stop, destroy)
Fleet View (private beta)
Fleet orchestration is in private beta. For organizations running multiple runners under an allowlisted plan, the fleet view aggregates:
- Total runners by status
- Aggregate cost across all runners
- Capacity — how many more runners your plan allows
- Health — runners with errors or high resource usage
Snapshots
Create point-in-time snapshots of a running container for:
- Backup — save state before risky operations
- Branching — fork a runner to test different approaches
- Rollback — restore to a previous known-good state
From the runner detail page, click Snapshots to create, restore, or branch.
Skills Management
Install skills from ClawHub directly from the dashboard:
- Navigate to the runner detail page
- Click Skills
- Browse or search the ClawHub registry
- Click Install — the skill is installed on the running container
The security scanner checks every skill before installation for malicious patterns.
Runner Configuration
Update runner settings from the detail page under Settings:
- Governance policy — override org-level governance for this runner
- Environment variables — inject secrets and configuration
- Network policy — control egress (which external services the runner can reach)
- Idle timeout — auto-stop to save costs
- Session budget — per-session cost ceiling
Troubleshooting
| Issue | Resolution |
|---|---|
| Runner stuck in “Provisioning” | Check container image availability; see Runbook: Provision Failure |
| Runner in “Errored” state | Check logs for error details; common causes: OOM, disk full, network timeout |
| High resource usage | Check for runaway processes; consider a larger instance or idle timeout |
| Session budget exceeded | Runner auto-stops; increase budget or optimize agent prompts |
Next Steps
- Runners Quickstart — create your first runner
- Runners Security — sandbox isolation and network policies
- Connect Your Machine (BYOVM) — bring your own compute
- Runner Costs — cost tracking in the dashboard
- Runbook: Runner Stuck — troubleshoot stuck runners