​

WeCom Rollout

• WeCom is documented as the official AIBot long-connection lane
• it is not documented as a webhook callback integration
• gateway run comes after channels serve wecom, not instead of the basic runtime validation

​

When This Is The Right Playbook

• the deployment is already standardized on WeCom
• one hosted provider should back the runtime clearly
• proactive sends and reply-loop behavior should share the same account identity
• you want stable work versus alerts accounts before gateway selectors enter the story

​

Use A Different Playbook If

​

Step 1: Bring Up The Provider First

active_provider = "volcengine"

[providers.volcengine]
kind = "volcengine"
api_key = { env = "ARK_API_KEY" }
model = "auto"

loong doctor
loong runtime models list
loong ask --message "Confirm that the active provider path is healthy."

​

Step 2: Start With A Single WeCom Account

[wecom]
enabled = true
bot_id = { env = "WECOM_BOT_ID" }
secret = { env = "WECOM_SECRET" }
ping_interval_s = 45
reconnect_interval_s = 12
allowed_conversation_ids = ["group_demo"]

loong channels send wecom --target "group_demo" --text "hello wecom"
loong channels serve wecom

• the official websocket URL is used by default
• override websocket_url only for controlled environments or bridge setups
• ping_interval_s and reconnect_interval_s are the right knobs when the network path needs tuning

​

Step 3: Move To Stable Named Accounts

[wecom]
enabled = true
default_account = "work"
ping_interval_s = 45
reconnect_interval_s = 12

[wecom.accounts.work]
bot_id = { env = "WECOM_WORK_BOT_ID" }
secret = { env = "WECOM_WORK_SECRET" }
allowed_conversation_ids = ["group_work"]

[wecom.accounts.alerts]
bot_id = { env = "WECOM_ALERTS_BOT_ID" }
secret = { env = "WECOM_ALERTS_SECRET" }
allowed_conversation_ids = ["group_alerts"]

• default_account makes the normal lane explicit
• accounts.<id> creates stable selector targets such as work and alerts
• gateway ownership stays legible instead of depending on whichever secret was most recently pasted into the top level

​

Step 4: Choose Serve Or Gateway Ownership

loong channels serve wecom --account work

loong gateway run \
  --session daemon-gateway \
  --channel-account wecom=work
loong gateway status --json

​

Step 5: Keep The Public Contract Truthful

• WeCom is the shipped AIBot long-connection lane
• it should not be described as if a webhook callback mode were the same supported path
• outbound-only surfaces still do not join this reply-loop ownership model

​

Troubleshooting

​

Continue Reading

• Continue to Common Setups for other end-to-end rollout shapes.
• Continue to Gateway And Supervision for the owner contract and selectors without the WeCom-specific rollout path.
• Continue to Channel Guides for the full shipped channel matrix.
• Continue to Channel Recipes for the broader channel recipe set.