WeCom push channel support

[wzxjohn]

What feature would you like to see?

Add WeCom as push channel for hub, and allowing approvals to be processed directly within the WeCom dialog box.

Additional information

The ServerChan channel can only send one-way notifications.

[github-actions]

Thanks for the request. WeCom is not currently implemented as a hub push channel; I did not find any WeCom/WeChat/QYAPI notification integration in the codebase.

The current hub notification path is channel-based, so WeCom would fit as a new NotificationChannel implementation registered by the hub config. Existing registered channels are web push, ServerChan, and Telegram.

Relevant code:

• hub/src/notifications/notificationTypes.ts:9 - NotificationChannel interface: ready, permission request, task notification, optional session completion.
• hub/src/notifications/notificationHub.ts:184 - fan-out to all configured notification channels.
• hub/src/index.ts:198 - builds the notification channel list.
• hub/src/index.ts:202 - registers ServerChan when SERVERCHAN_SENDKEY and SERVERCHAN_NOTIFICATION are enabled.
• hub/src/index.ts:207 - initializes Telegram and registers it when Telegram notifications are enabled.
• hub/src/configuration.ts:8 - documented hub notification environment variables; no WeCom variables are present.
• hub/src/config/serverSettings.ts:13 - persisted hub settings currently include Telegram and ServerChan notification config only.
• hub/src/serverchan/channel.ts:15 - small webhook-style channel example implementing NotificationChannel.

Need more info:

• Which WeCom delivery mode do you want: group robot webhook, or WeCom app message using corp ID / secret / agent ID?
• Should WeCom receive all current notification types: ready, permission request, task notifications, and session completion?

---

HAPI Bot

[tiann]

We support ServerChan, which you can use to support WeCom.

[wzxjohn]

We support ServerChan, which you can use to support WeCom.

@tiann These two implementations are completely different. ServerChan’s WeCom push notifications are one-way only. In contrast, the WeCom feature in PR uses a smart bot WebSocket to enable two-way interaction, allowing approvals to be processed directly within the WeCom dialog box, like Telegram.

这两个实现是完全不同的。ServerChan 的通知是单向的，无法直接审批。而 PR 内的企业微信通知用的是智能机器人的双向 WebSocket，允许直接在智能机器人的对话框中处理权限审批，与 Telegram 的效果类似。