OpenClaw-China Brings One-Click AI Integration to DingTalk, QQ, and Enterprise WeChat
The open-source openclaw-china plugin (2.2K Stars) adds seamless AI assistant integration for DingTalk, QQ, and Enterprise WeChat, offering multi‑format messaging, proactive pushes, streaming responses, and a layered plugin architecture that keeps the core OpenClaw framework untouched.
What the project does
openclaw-china (GitHub: BytePioneer-AI/openclaw-china) is an open‑source plugin that extends the OpenClaw AI assistant with native support for Chinese instant‑messaging platforms. It does not modify the core framework; it mounts as a plugin, allowing a single AI assistant to serve multiple domestic office scenarios.
Supported platforms
DingTalk – ✅ Available, easy configuration, supports file transfer and scheduled tasks.
QQ Bot – ✅ Available, easy configuration, same capabilities as DingTalk.
Enterprise WeChat (smart robot) – ✅ Available, medium difficulty, file transfer only.
Enterprise WeChat (custom app) – ✅ Available, medium+ difficulty, adds proactive message push and WeChat integration.
Feishu – ✅ Available, medium+ difficulty, but marked "maintenance stopped" because Feishu now provides its own AI assistant.
DingTalk and QQ offer the smoothest onboarding—just fill in an ID and secret. The custom‑app mode of Enterprise WeChat unlocks a "proactive push" capability, letting the AI send scheduled reports without waiting for user input.
Key capabilities beyond simple chat
Multi‑format messages : plain text, Markdown rendering, images, file exchange, and optional voice messages (via Tencent Cloud ASR).
Group + private modes : trigger the bot with @ in a group or converse one‑on‑one; @ detection is built‑in.
Streaming response : some platforms stream partial replies as they are generated, mimicking the ChatGPT web experience.
Multi‑account support : a single OpenClaw instance can connect multiple DingTalk or QQ accounts, avoiding the need for separate deployments.
Scheduled tasks & proactive push : define rules so the AI automatically posts daily code‑review summaries, weekly progress reports, etc.
Installation steps
If OpenClaw is already running, add the plugin in two commands:
# Step 1: install the plugin
openclaw plugins install @openclaw-china/channels
# Step 2: run the interactive setup wizard
openclaw china setupThe wizard guides you through platform selection and key entry without editing configuration files.
For manual control, the CLI can set each option individually, e.g. for DingTalk:
openclaw config set channels.dingtalk.enabled true
openclaw config set channels.dingtalk.clientId dingxxxxxx
openclaw config set channels.dingtalk.clientSecret your-secretWindows users may encounter npm compatibility issues; the official recommendation is to clone the repository and build with pnpm, then link locally for hot‑reload support.
Architectural design
Host layer : the unchanged OpenClaw core framework.
Scheduler center : @openclaw-china/channels aggregates and manages all channel plugins.
Plugin layer : one isolated plugin per IM platform, ensuring no cross‑interference.
Shared infrastructure : @openclaw-china/shared provides common logic used across channels.
This layered approach enables dynamic registration—plugins can be enabled or disabled at runtime, and existing Skills, automation flows, and model configurations remain unaffected.
The project uses a pnpm monorepo workspace with TypeScript compilation. Link‑mode installation allows code changes to take effect instantly, which is convenient for contributors or custom development.
Conclusion
For OpenClaw users who need Chinese IM integration, openclaw-china offers a ready‑made, low‑effort solution. New users should first clarify their AI‑in‑messaging goals before adding the plugin.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
