Channels
Connect Slack, Discord, Telegram, Lark, and other messaging platforms so agents can work where your team already communicates.
Channels let the desktop agent receive messages, run tasks, deliver results, and coordinate with users from team chat. The active channel runtime supports Slack, Discord, Telegram, and Lark, with additional gateway adapters available as they mature.
Open Channel Settings
- Open Settings
- Select Channels
- Choose the platform you want to configure
- Add the bot credentials required by that platform
- Save the configuration
- Start or restart the channel runtime if prompted
The app stores channel configuration locally and starts configured channel bots through the backend runtime.
Platform Guide
| Platform | Main Setup Items | Useful For |
|---|---|---|
| Slack | Bot token, signing secret, app token or socket mode, workspace pairing | App Home, assistant threads, file upload, reactions, interactive forms |
| Discord | Bot token, guild and channel permissions | Team channels, command-style task routing, file delivery |
| Telegram | Bot token and chat targets | Personal or small-team task control |
| Lark | App credentials and target configuration | Enterprise chat workflows |
Provider details differ, but the workflow is the same: create a bot in the provider console, copy the credentials into Settings, then verify that the bot can receive and send messages.
Access Modes
Channels can run in a more open mode or a gated mode.
Use open access when the bot is limited to a trusted workspace or private chat.
Use gated access when you need explicit user or workspace approval before people can start agent tasks. Gated access is better for shared workspaces, public channels, or bots that can reach sensitive tools.
Slack App Home
Slack has the richest channel surface.
From Slack App Home, users can:
- Pair their Slack user with the desktop agent
- Review bot status
- Configure user-level credentials
- Discover MCP presets exposed to Slack
- Start interactive task flows
- Return to active assistant threads
Slack threads keep agent work grouped with the request that started it. The bot also tracks its own thread state so replies resume the right task context.
Files, Media, and Formatting
Channels can deliver more than plain text:
- Upload files and generated media
- Suppress or allow link unfurls when supported
- Render markdown or provider-native blocks
- Send reactions or status updates while work is running
- Preserve thread context for follow-up messages
When sending generated files, make sure the destination channel has permission to view the content and that any required attribution or disclosure is included.
Automations and Channels
Automations can deliver results to configured messaging channels. Use this for recurring reports, daily summaries, incident checks, or scheduled media tasks.
- Create or edit an automation
- Choose the delivery platform
- Select the target chat, channel, or thread
- Save the automation
- Run it manually once to verify delivery
Troubleshooting
- If messages do not arrive, check bot token validity and provider app permissions
- If a bot starts but cannot post, verify channel membership and write scopes
- If Slack App Home is empty, check Slack app event subscriptions and socket mode settings
- If files fail to upload, check file size limits and provider upload scopes
- If the wrong user is linked, remove the pairing and pair again from the provider surface