Channels
Channels
OpenClaw can work inside chat applications you already use. All channels connect through the Gateway, with text as the common layer and media, reactions or group behavior varying by channel.
Common Channels
The most common real-world usage pattern, with QR login and more persistent session state on disk.
Telegram
Usually the fastest to configure. A bot token is enough, and direct messages default to pairing approval.
Discord
Good for communities, teams and channel-based collaboration, with support for servers, channels and DMs.
Workspace channels
Useful for company or team workspaces, with some integrations enabled through plugins.
Apple ecosystem path
Usually better through more stable bridges like BlueBubbles. Legacy local iMessage CLI paths remain historical references only.
Web control UI
The fastest way to confirm OpenClaw works at all, without needing any third-party chat platform.
Common Commands
Log in to channels
openclaw channels loginCheck channel status
openclaw channels status --probeHandle DM pairing
openclaw pairing list whatsapp
openclaw pairing approve whatsapp <code>Things to Remember
Multiple channels can run at the same time, and OpenClaw routes by chat context.
Group behavior varies by channel, so mention rules, allowlists and group allowlists usually need explicit configuration.
Keep pairing and allowFrom defaults in place for DM entry points so public channels cannot immediately trigger privileged tools.
If you only want to confirm installation works, start from Dashboard or Control UI before spending time on channel login.
Specialized Pages
QR login, credential directories, self-chat mode and common disconnect symptoms.
BotFather, group mentions, HTML rendering and connectivity requirements.
Intents, guild / channel rules and DM versus channel session isolation.
DM access approval and device admission to the Gateway network.
Which commands to run first and which logs matter when messages stop flowing.