Skip to main content
A Channel is a messaging connection. Two relationships keep delivery scope explicit:
  1. A Channel link connects a bot to an Agent.
  2. A chat pairing connects one external chat, server, or direct message to that Channel link.
The Channel concept does not change with Agent software or run location, but linking and pairing actions are availability-gated. The current release exposes them for supported Cloud Agent workflows. See Core concepts and the Cloud Agent overview.

Current provider availability

The released dashboard supports connecting Telegram and Discord bots. WhatsApp linking is unavailable in this release. Use the providers and status shown under Channels as the authority for your account.

Connect a bot

Open Channels in the Clawdi dashboard, choose Connect bot, and select a provider:
  • For Telegram, enter a name and the bot token obtained from BotFather.
  • For Discord, enter a name, bot token, application ID, and interactions public key from the Discord Developer Portal.
Submit once and wait for the Channel to appear under Your bots.
Bot tokens are secrets. Use the dashboard’s credential field. For CLI automation, pass the name of an environment variable with --provider-token-env; do not place the token itself in shell history.
Discord credentials are stored during setup but are not verified with Discord at creation time. Send a test message and check Channel activity and health before relying on it. Open Agents, select the Agent, and open Channels. Under Add a channel, choose an available bot and select Link. If this tab is not available for the Agent workflow, inspect released CLI availability:
Linking alone does not authorize every external chat to reach the Agent. Pair the intended chat next.

Pair Telegram

On the Agent’s connected Channel row, choose Pair Telegram. Use one of the paths shown:
  • Scan the QR code or open the generated Telegram link for a direct chat.
  • For a group, add the bot and send the exact pairing command displayed by the dashboard.
The pairing link and code expire. Generate a new one if the countdown ends before pairing completes.

Pair Discord

Choose Pair Discord, then select Server or Direct message:
  • For a server, add the bot with the generated install link. You need the provider permission stated by the dashboard.
  • In the target server or direct message, run /bot_pair and provide the generated code in its required code option.
After pairing, the chat appears beneath the connected Channel on the Agent page. Check Activity and Health on the Channel page after a test message.

Unpair one chat

Use this when the bot and Agent should stay linked but one external chat should stop reaching it:
  • For Telegram, choose the unpair action beside the paired chat and confirm.
  • For Discord, run /bot_unpair inside the paired server or direct message.
Other paired chats and the Channel link remain active. On the Agent’s Channels section, choose the unlink action beside the bot and confirm. The Agent stops answering through that bot. The Channel remains available and can still be linked to other Agents.

Remove the Channel

Open the Channel detail page and choose Remove only when the bot connection itself should be retired.
Removing a Channel stops linked Agents from sending and receiving through it and cannot be undone. Unpair a chat or unlink one Agent when that narrower action is sufficient.
For CLI inspection and automation, start with:
Avoid copying a full option table into scripts; provider fields and pairing outputs can vary by CLI version and account availability.
Last modified on August 2, 2026