Skip to main content
Open Control UI on a running agent’s page opens the agent’s own interface, served by the OpenClaw instance inside its container. It is the primary action on that page, and the reason the rest of the panel is as small as it is.
The button is disabled while the agent is not running, with the reason written next to it rather than hidden in a tooltip. Deploy or start the agent first.

What belongs there rather than here

This split is the platform’s shape, not an omission. The panel used to carry a channel pairing screen, a skills catalogue and a file manager; all three are OpenClaw’s, and running a second copy of them meant two places to change one setting.

Which OpenClaw you are running

Your agent runs a released OpenClaw image, and the platform tracks a recommended version that new deploys and redeploys pick up. The agent’s page shows the version it is actually running. For what OpenClaw itself can do — channels, skills, memory, the gateway, the CLI — read docs.openclaw.ai. This documentation covers the platform underneath it and does not restate the upstream reference.

Reaching an agent without a browser

Telegram Hub

One platform bot, every agent on your account, no per-agent setup.

A channel of your own

A bot token or a paired account, configured inside the agent.

A shell

The agent’s own container, from the panel.

Its config file

Read and edit what the agent is set to, as JSON.
Last modified on August 31, 2026