Runtime Guide
OpenClaw Dashboard and Skill Setup
This page explains how to read Mission Control, what “skills with missing dependencies” actually means, and how Agentbot users should move between Runtime, Skills Manager, Config, and broadcasting without getting lost.
What The Dashboard Means
Runtime tells you whether the managed OpenClaw machine is alive.
Skills Manager tells you what capabilities are installed.
Config is where external channels and keys get finished.
FFmpeg matters for autonomous baseFM DJ output and pre-rendered broadcasts.
Missing Dependencies Explained
If you see a list like 1Password, Apple Notes, Apple Reminders +43 more, the agent is not broken. Those are optional integrations that need something extra before they can work.
Recommended Flow
Check Mission Control first
Look at Agentbot API, X402 Gateway, and Agentbot Runtime. If the runtime is healthy, use Open. If the runtime is stopped, use Start Machine or Recovery before chasing anything else.
Use Skills Manager second
Install or remove skills from the dashboard, but remember that some skills need external apps, local binaries, API keys, or desktop connectors before they can run.
Treat missing dependencies as setup tasks
A missing dependency message does not mean the runtime is broken. It means that skill depends on something extra that is not configured yet.
Use Config for channel setup
If a skill depends on Slack, Telegram, WhatsApp, Apple apps, 1Password, or other tools, the next stop is your runtime config and environment, not repeated installs.
baseFM DJ Tip
Human DJs usually only need three things: access, go live, and end set. Advanced Mux and relay diagnostics are there for recovery, not as the main workflow.
Open DJ Stream →Managed Runtime Tip
If the runtime is healthy but a skill still complains, the problem is usually that skill setup, not the machine. That is why the next move after Mission Control is usually Skills Manager or Config.
Open Mission Control →Paid Broadcast Service
Upload a Mix Set and Let Agentbot Broadcast It
This is the clean next product step for DJs who do not want to go live manually every time. It should be sold as a managed broadcast service, not a free storage sink.
Official replay and asset reference: Mux Assets API
- • Upload a finished mix file instead of going live from OBS.
- • Choose a title, artwork loop, schedule, and whether replay stays available after broadcast.
- • Agentbot renders the ffmpeg path, starts the broadcast at the scheduled time, and tears it down automatically after the set.
- • Replay retention is paid. Default cleanup should remove stored assets unless the DJ explicitly pays to keep them.
Billing Rule
Charge for ingest, scheduled broadcast, and replay retention separately. Default behavior should delete stored assets after playback unless the DJ explicitly pays to keep them.
Operator Rule
Treat uploaded sets as a scheduled automation path with strong cleanup guarantees. The platform should never silently keep Mux storage running for free.