Skip to main content
Apart from Telegram Hub, channels are set up inside the agent, in its Control UI. The panel has no pairing screen and no channel list.
This changed with the platform simplification. If you remember a Channels tab on the agent’s page, or a QR code shown by the dashboard, that is what moved — the same setup is now done in the agent’s own interface, where the rest of its behaviour is configured.

​
Why it is done there

A channel is a property of the OpenClaw instance, not of the container it runs in. Running a second copy of the pairing flow on the platform meant two places to change one setting and two things to keep in step with an upstream release.

​
What that means in practice

You need a running agent

Open the Control UI from the agent’s page. A stopped agent cannot be configured — there is nothing to configure.

Credentials stay with the agent

A bot token or a paired session lives in the agent’s own configuration and on its own volume. It survives a redeploy.
For which channels are supported and how each is paired, read OpenClaw’s own documentation at docs.openclaw.ai. It is the one place that tracks the current list, and this page will not restate it.

​
Tokens for a channel

A credential the agent needs at runtime — an API token for a service it talks to — can also be stored on the platform side as an environment variable, which keeps it encrypted and out of the config file. Channel credentials themselves are usually simpler to enter where the channel is set up.
Last modified on August 31, 2026