bytepioneer-ai/openclaw-china

OpenClaw中国插件:支持飞书,钉钉,QQ,企业微信,微信

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 43 minutes ago
Added to GitGenius on September 17th, 2026
Created on January 28th, 2026
Open Issues & Pull Requests: 30 (+0)
GitHub issues: Enabled
Number of forks: 340
Total Stargazers: 3,965 (+0)
Total Subscribers: 31 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.8 hours
Mean response time: 21.7 hours
90th percentile: 46.3 hours
Tracked items: 163

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 4% of issues opened in the past year have never received a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 84% of issues opened in the past year have been closed, leaving a working backlog. Three people close 88% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 27
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 171 days
Stale 30+ days: 26
Stale 90+ days: 26

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

OpenClaw China is a plugin collection that extends OpenClaw with support for Chinese instant messaging platforms.

The tool solves the problem of integrating AI assistants into messaging services widely used in China. It provides channel extensions for platforms including DingTalk, WeChat Work, WeChat Official Accounts, WeChat Customer Service, QQ, and Feishu. The approach focuses on stable message sending and receiving, a unified plugin interface, and a low-friction configuration process.

Teams building AI assistants for Chinese markets should consider this tool if they need to deploy across multiple domestic messaging platforms simultaneously. The project is particularly suited for organizations that want to avoid building separate integrations for each channel and prefer a standardized plugin architecture. The tool handles the platform-specific complexity, allowing developers to focus on assistant logic rather than channel-specific implementation details.

Development activity shows active engagement with the community through a dedicated discussion group for installation support, development questions, and architecture discussions. The project maintains a clear separation between bug reports, which are directed to issue tracking, and community support questions, which are handled through group channels. Documentation includes quickstart guides, architecture overview, feature support matrices, and a changelog, indicating structured maintenance practices.