-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Weak Chinese IM integration #2213
Copy link
Copy link
Open
Labels
area: integrationsThird-party service integration behaviorThird-party service integration behaviorintegration: slackSlack integration or channel behaviorSlack integration or channel behaviorintegration: telegramTelegram integration or channel behaviorTelegram integration or channel behaviorintegration: wechatWeChat integration behaviorWeChat integration behaviorintegration: whatsappWhatsApp integration or channel behaviorWhatsApp integration or channel behavior
Metadata
Metadata
Assignees
Labels
area: integrationsThird-party service integration behaviorThird-party service integration behaviorintegration: slackSlack integration or channel behaviorSlack integration or channel behaviorintegration: telegramTelegram integration or channel behaviorTelegram integration or channel behaviorintegration: wechatWeChat integration behaviorWeChat integration behaviorintegration: whatsappWhatsApp integration or channel behaviorWhatsApp integration or channel behavior
Type
Fields
Give feedbackNo fields configured for Enhancement.
Problem Statement
IM/channel support lacks Feishu/WeChat/DingTalk
Nemoclaw’s current IM and channel integration only supports Western platforms such as Telegram, Discord, and Slack, which makes it difficult to use in China-focused enterprise environments. There is no first‑class support for mainstream Chinese messaging apps like Feishu, WeChat, and DingTalk, so customers must build and maintain their own bridge layer to connect Nemoclaw to the tools their users actually use. This significantly increases integration effort, operational risk, and security review overhead for China-based deployments. By contrast, some alternative agent frameworks provide one‑command, QR‑code–based onboarding flows for Feishu/WeChat, greatly reducing friction for real‑world projects.
Proposed Design
Chinese IM channels (Feishu/WeChat/DingTalk) can be integrated as easily as existing supported platforms like Telegram, Discord, or Slack, ideally with a one‑command, QR‑code–style onboarding flow.
Alternatives Considered
No response
Category
enhancement: feature
Checklist