WeCom

This is a shipped runtime-backed surface: direct sends are implemented, the serve loop is implemented, and the channel can join gateway run or gateway run.

At A Glance

Field	Value
Catalog id	`wecom`
Config key	`wecom`
Implementation status	`runtime_backed`
Transport	`wecom_aibot_long_connection`
Aliases	`wechat-work`, `qywx`
Default send target kind	`conversation`

Minimal Config

[wecom]
enabled = true
bot_id_env = "WECOM_BOT_ID"
secret_env = "WECOM_SECRET"
allowed_conversation_ids = ["group_demo"]

Smoke Test

loong channels send wecom --target "wmxxxxxxxxxxxxxxxx" --text "hello from loong"
loong channels serve wecom

Command Surface

Operation	Command	Usage or status
proactive send	`channels send wecom`	Usage: loong channels send wecom [OPTIONS] —target <TARGET> —text <TEXT>
long connection reply loop	`channels serve wecom`	Usage: loong channels serve wecom [OPTIONS]

Required Fields For Send

Requirement	Config paths	Env pointer paths	Default env
channel enabled	`wecom.enabled` `wecom.accounts.<account>.enabled`	none	none
aibot bot id	`wecom.bot_id` `wecom.accounts.<account>.bot_id`	`wecom.bot_id_env` `wecom.accounts.<account>.bot_id_env`	`WECOM_BOT_ID`
aibot secret	`wecom.secret` `wecom.accounts.<account>.secret`	`wecom.secret_env` `wecom.accounts.<account>.secret_env`	`WECOM_SECRET`

Required Fields For Serve

Requirement	Config paths	Env pointer paths	Default env
channel enabled	`wecom.enabled` `wecom.accounts.<account>.enabled`	none	none
aibot bot id	`wecom.bot_id` `wecom.accounts.<account>.bot_id`	`wecom.bot_id_env` `wecom.accounts.<account>.bot_id_env`	`WECOM_BOT_ID`
aibot secret	`wecom.secret` `wecom.accounts.<account>.secret`	`wecom.secret_env` `wecom.accounts.<account>.secret_env`	`WECOM_SECRET`
allowed conversation ids	`wecom.allowed_conversation_ids` `wecom.accounts.<account>.allowed_conversation_ids`	none	none

Optional Transport Tuning

Tuning field	Config paths	Why it exists
websocket url override	`wecom.websocket_url` `wecom.accounts.<account>.websocket_url`	controlled environments, bridge setups, or diagnostics
ping interval seconds	`wecom.ping_interval_s` `wecom.accounts.<account>.ping_interval_s`	tune keepalive cadence for the network path
reconnect interval seconds	`wecom.reconnect_interval_s` `wecom.accounts.<account>.reconnect_interval_s`	tune retry behavior after disconnects

Gateway And Ownership

This surface can run directly through channels serve wecom, or under Gateway And Supervision through gateway run.

Operator Notes

Loong documents WeCom as the official AIBot long-connection lane. Do not describe a webhook callback mode as if it were the same shipped contract.
websocket_url, ping_interval_s, and reconnect_interval_s are tuning knobs, not day-zero requirements for a basic rollout.

Continue to Channel Guides for the full shipped channel matrix.
Continue to Channels for the conceptual surface model.
Continue to Channel Setup for the shared public setup contract.
Continue to Gateway And Supervision when this surface needs longer-lived runtime ownership.

Overview

Get Started

Use Loong

Build On Loong

Reference

WeCom

WeCom

At A Glance

Minimal Config

Smoke Test

Command Surface

Required Fields For Send

Required Fields For Serve

Optional Transport Tuning

Gateway And Ownership

Operator Notes

​WeCom

​At A Glance

​Minimal Config

​Smoke Test

​Command Surface

​Required Fields For Send

​Required Fields For Serve

​Optional Transport Tuning

​Gateway And Ownership

​Operator Notes

​Related Docs

WeCom

At A Glance

Minimal Config

Smoke Test

Command Surface

Required Fields For Send

Required Fields For Serve

Optional Transport Tuning

Gateway And Ownership

Operator Notes

Related Docs