Other Chat Platforms

Channels with working integrations but not yet pulled out into dedicated guides. Each is feature-gated; enable the matching channel-<name> feature at build time.

Discord

[channels.discord]
enabled = true
bot_token = "..."                  # create at https://discord.com/developers/applications
allowed_guilds = ["123..."]
allowed_users = []
reply_to_mentions_only = true
draft_update_interval_ms = 750     # bump if hitting Discord rate limits

• Bot intents needed: Message Content Intent, Server Members Intent. Set in the Developer Portal.
• Streaming: full — edits messages in place and splits long replies into multiple messages.
• Tool-call indicator: typing indicator while tools run; visible code-block preview for shell and browser calls.

Slack

[channels.slack]
enabled = true
bot_token = "xoxb-..."            # classic bot token
app_token = "xapp-..."            # for Socket Mode
signing_secret = "..."
allowed_channels = ["C01..."]

• Socket Mode is the default (no public webhook URL needed).
• For HTTP Events API instead, drop app_token and point Slack's event subscription URL at /slack/events on the gateway.
• Supports multi-message streaming, threaded replies, and slash-command ingress.

Telegram

[channels.telegram]
enabled = true
bot_token = "..."                  # from @BotFather
allowed_users = [123456789]
allowed_chats = [-100987...]       # group / channel IDs
use_long_polling = true            # default — no webhook needed

• Long polling is the default; no public URL required. Switch to webhook mode by setting webhook_url (then expose the gateway).
• Streaming draft edits are supported but capped by Telegram's rate limit. Tune draft_update_interval_ms if you see "Too Many Requests".

Signal

[channels.signal]
enabled = true
phone_number = "+14155550123"
signal_cli_rest_url = "http://localhost:8080"   # signal-cli-rest-api service

Signal integration requires running the signal-cli-rest-api container locally — Signal has no official bot API, so we tunnel through signal-cli.

iMessage (macOS only)

[channels.imessage]
enabled = true
provider = "linq"                  # Linq Partner API for iMessage/RCS/SMS
api_key = "..."

macOS-only and requires either Linq as a third-party relay, or direct AppleScript automation (experimental, requires Full Disk Access and Accessibility grants).

WeCom (企业微信)

[channels.wecom]
enabled = true
corp_id = "..."
corp_secret = "..."
agent_id = 1000001

Chinese enterprise WeChat. Custom app required in the corp admin panel.

DingTalk

[channels.dingtalk]
enabled = true
app_key = "..."
app_secret = "..."
robot_code = "..."

Alibaba's enterprise messenger. Same bot shape as WeCom.

Lark / Feishu

[channels.lark]
enabled = true
app_id = "..."
app_secret = "..."

QQ

[channels.qq]
enabled = true
bot_id = "..."
bot_token = "..."

Tencent's consumer messenger. Bot API access requires developer registration.

IRC

[channels.irc]
enabled = true
server = "irc.libera.chat"
port = 6697
tls = true
nickname = "zeroclaw"
channels = ["#mychannel"]
nickserv_password = "..."          # optional

Classic IRC. Supports SASL, NickServ auth, and multiple channels.

Mochat

[channels.mochat]
enabled = true
api_key = "..."
# additional provider-specific fields

Notion

[channels.notion]
enabled = true
integration_token = "..."
databases = ["..."]                # DB IDs the agent can write to

Treats a Notion database as a message surface. Useful for asynchronous workflows where the "channel" is a task inbox.

When to prefer a dedicated guide

Channels with more intricate setup (OAuth flows, end-to-end encryption, multi-device considerations) live in their own pages:

• Matrix — E2EE, device verification, Synapse/Dendrite specifics
• Mattermost
• LINE
• Nextcloud Talk

If you run into configuration friction on any channel above, file an issue with the repro and we'll consider promoting it to a dedicated guide.