对接企业微信新出的【智能机器人长链接模式】

[williambao]

企业微信刚推出了长链接模式，可以用 BotId + Secret 及 websocket 模式对接机器人了。这极大的方便了内网使用。希望对接这个模式。

具体参考官方文档：
https://developer.work.weixin.qq.com/document/path/101463#%E4%B8%BB%E5%8A%A8%E6%8E%A8%E9%80%81%E6%B6%88%E6%81%AF

[nikolasdehor]

PicoClaw already has a WeCom AI Bot channel implementation in pkg/channels/wecom/aibot.go that uses the "intelligent bot" model with stream tasks and response URLs. However, the new long-connection mode (websocket-based) referenced in the WeCom docs is a different transport mechanism.

Looking at the existing WeCom code:

• pkg/channels/wecom/aibot.go — AI Bot channel (current, uses HTTP callbacks + streaming)
• pkg/channels/wecom/bot.go — Standard bot (webhook-based)
• pkg/channels/wecom/app.go — App message mode

The new long-connection mode (BotId + Secret + WebSocket) would be a separate channel variant. The implementation pattern would be similar to how the Feishu channel uses WebSocket (pkg/channels/feishu/feishu_64.go line 60-77):

c.wsClient = larkws.NewClient(appID, appSecret, ...)
go wsClient.Start(runCtx)

For WeCom long-connection, the equivalent would be:

1. Connect to WeCom WebSocket endpoint using BotId + Secret
2. Handle incoming messages via the WS connection
3. Send replies through the WS connection (proactive push)

PR #1295 (Implement the latest long-connection mode for the WeCom AI Bot) appears to be implementing exactly this feature. It would be worth reviewing that PR to see if it covers the full spec from the WeCom docs (message receive, proactive push, reconnection handling).

The advantage of the long-connection mode is significant for internal network deployments — no callback URL needed, no public endpoint to expose.

[sipeed-bot]

@williambao Hi! This issue has had no activity for over 2 weeks, so I'm closing it for now to keep things tidy. If it's still relevant, feel free to reopen it anytime and we'll pick it back up.