Set Up IM Channels in Octop

IM channels let your team talk to Octop agents through the chat tools they already use every day. When someone sends a message on Feishu, WeCom, DingTalk, or Telegram, Octop routes it to the linked agent and replies in the same thread — no need to open the web UI. Each channel belongs to exactly one agent, so you control which agent handles which platform.

Where to configure channels

Channels are configured per agent:

Personalization → Channels

Select the agent at the top of the page, then toggle on the platform you want and enter its credentials.

Platform setup

Feishu

WeCom

DingTalk

Others

Prefer QR registration in the channel drawer: generate a Feishu AI bot QR code, scan it with Feishu Scan, then confirm on the phone. Octop fills in and saves the credentials.

Or create a Feishu app in the Feishu Open Platform and note down the App ID and App Secret.

Enable the channel

Toggle on Feishu under Personalization → Channels.

Bind the bot

Click the QR button and scan with Feishu, or fill in the App ID and App Secret from your Feishu app settings.

Register the webhook

If you created the app yourself, copy the webhook URL shown by Octop and paste it into the Event subscription section of your Feishu app configuration, then save the Feishu app settings.

Verify

Send a message to the bot to confirm the channel is receiving events. Replies inside a Feishu topic use the topic reply API (reply_in_thread).

Octop also ships a guided terminal wizard that walks through the same flow:

octop channel feishu-setup

Set up a WeCom (企业微信) application and gather the Corp ID (企业ID), Agent ID, and Secret.

Enable the channel

Toggle on WeCom under Personalization → Channels.

Enter your credentials

Fill in the Corp ID, Agent ID, and Secret from your WeCom application settings.

Configure the callback URL

Add the callback URL Octop shows to your WeCom app so it can receive messages.

For a quicker bind using a QR-code scan, run octop channel bind and scan the code with the WeCom mobile app.

You can authorize DingTalk from Octop with a QR code, or create a bot manually in the DingTalk Open Platform and collect the Client ID and Client Secret.

Open the channel drawer

Open Personalization → Channels, then select DingTalk.

Use QR setup

Stay on Quick setup (QR code) and click Generate DingTalk QR Code. Scan the application authorization code in the DingTalk app while signed in to the same organization.

Wait for Octop to enable it

After you confirm application creation in DingTalk, Octop creates and enables the channel automatically.

To configure it manually instead, switch to Manual, fill in the Client ID and Client Secret, then copy the callback URL provided by Octop into the Message receive mode settings of your DingTalk app.

Enable the channel

Toggle on QQ under Personalization → Channels.

Bind credentials

Prefer QR bind in the channel drawer (scan with mobile QQ), or fill in App ID and Client Secret manually and save.

Configure group context (optional)

For group chats, set visibility (auto, all, mention_recent, or mention_only) and when the agent should reply (mention or always when visibility is all).

Private-chat streaming

QQ direct chat defaults to official stream_messages. Saving the channel writes c2c_streaming: true. Set c2c_streaming: false only if you want a single static reply. The old keys streaming and response_mode do nothing for C2C. Group, channel, and channel-DM chats have no stream API and stay static. Tool-progress bubbles use extra passive-reply quota (about four per inbound message).

From the terminal:

octop channel bind qq --agent main

Choose how replies appear

Open a channel's settings drawer and use Message display → Response mode:

Final only (Recommended) sends one completed reply after the agent finishes. Progress narration emitted before tool calls is hidden, while generated media is delivered with the final text.
Live progress keeps the staged, streaming updates for workflows where users need to follow execution.

New external IM channels created from the web UI default to Live progress. Show thinking and Show tool hints remain separate display controls. QQ private chat ignores this switch and uses c2c_streaming instead.

TIP

To manage channels from the terminal (list, test, delete, feishu-setup, bind), see Channel & cron commands.

NOTE

Each agent can have multiple channels active at the same time. All messages are processed by the same underlying agent, so the conversation context stays unified regardless of which platform a user messages from.

Set Up IM Channels in Octop#

#Where to configure channels

#Platform setup

Enable the channel

Bind the bot

Register the webhook

Verify

#Choose how replies appear

Set Up IM Channels in Octop

Where to configure channels

Platform setup

Choose how replies appear