The WeChat Work plugin that outgrew its official parent

What it does

@sunnoy/wecom plugs OpenClaw into Enterprise WeChat (WeCom) via WebSocket long-connection, turning the chat platform into an AI bot interface. It handles direct messages, group chats, streaming replies, and slash commands — the usual chatbot mechanics, but tuned for corporate IT environments where “usual” means “needs twenty access-control knobs.”

The interesting bit

The plugin started as a community enhancement of the official @wecom/wecom-openclaw-plugin, then aggressively expanded scope. The feature-comparison table in the README runs to twenty-five rows: multi-bot management, dynamic agent isolation per user or group, quota-aware rate limiting, pending-reply retry on disconnect, even reasoning-stream throttling to stop the SDK queue from overflowing. It’s the kind of defensive coding you write after watching a production bot spam a 500-person group chat at 3 AM.

Version 2.1 added an optional HTTP callback inbound channel that runs parallel to the WebSocket — useful for self-built apps that need the old callback path. Version 3.x dropped support for older OpenClaw releases and aligned with WeCom’s MCP (doc auth, SmartPage) as of April 2026.

Key highlights

• Multi-account bot management with shared-field inheritance across configurations
• Dynamic agent routing: each user or group can be siloed into separate workspaces with templated onboarding files
• Command allowlisting with admin bypass, plus DM and group-chat admission policies (pairing, allowlist, open, disabled)
• Outbound enhancements: Agent API for proactive messages, webhook bot notifications, department/tag targeting (party:, tag:)
• Resilience features: pending-reply retry on WS disconnect, 800ms reasoning-stream throttling, reqId+msgId deduplication
• Egress proxy support and custom API base URLs for air-gapped or regional deployments

Caveats

• The README notes that “large enterprises commonly only open doc-class MCP capabilities” — so SmartPage and document features may be partially locked depending on your WeCom contract tier
• Dynamic agent persistence to config (persistToConfig: true) can trigger gateway reloads, which the docs flag as a potential disruption
• Migration from HTTP callback to WebSocket long-connection requires manual reconfiguration in the WeCom admin console

Verdict

Worth a look if you’re running OpenClaw in a WeCom environment and the official plugin’s single-bot, single-workspace model is already creaking. Skip it if you just need a quick one-off chatbot — the configuration surface is enterprise-grade deep, and the README assumes you’re comfortable managing botId, secret, corpId, and callback tokens simultaneously.