/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

zhayujie/chatgpt-on-wechat

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T15:40:10.712Z

1mo ago

zhayujie/chatgpt-on-wechat

zhayujie/chatgpt-on-wechat is a Python-based open source AI agent platform centered on WeChat, with broader support for Feishu, DingTalk, WeCom, QQ, public accounts, and web. It is a large, active project with MIT licensing, substantial community traction, and recent 2026 development focused on agent features, browser tooling, skills, memory, and multi-channel support.

Loading tags...

Stars42,657

Forks9,862

Default branchmaster

Last pushed2026-03-30T13:40:03Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Choose this fork if Dify integration and GeWeChat stability are your priority. Choose upstream if you want the newest agent, browser, skills, and web-console work with less maintenance risk.

Choose this fork only if you want a simpler, legacy WeChat bot and are willing to give up upstream's newer agent, multi-channel, and admin capabilities. If you want the current CowAgent feature set, upstream is the better fit.

Choose this fork only if you specifically want the older, simpler WeChat bot behavior and can live without upstream's newer agent and multi-channel features. For new builds, upstream is the safer and more capable base.

Prefer upstream unless you specifically want a small, legacy WeChat bot. This fork looks stale and materially behind on the newer agent, skills, multi-channel, and tooling capabilities that make the upstream project more capable today.

Choose this fork only if you want an older, more conservative chatbot codebase to customize heavily. If you want the current agent platform, skill system, web console, and browser tooling, upstream is the better choice.

Choose upstream unless you specifically need this older, unmodified baseline. This fork offers no clear added capability and is significantly behind active development.

Choose this fork only if its note-bot customization and open-source-model orientation match your exact use case. For most adopters who want the full, current multi-channel agent platform, the upstream project is the safer choice because this fork is substantially diverged, stale, and appears to remove or lag on major upstream capabilities.

Choose this fork only if its older custom model support is specifically what you need. If you want the current agent platform, broader channel support, and active maintenance, upstream is the safer choice.

Prefer upstream unless you specifically need this older snapshot. This fork offers no visible added value and is far behind the active project, so adopters would mainly inherit maintenance debt.

Choose this fork only if you specifically want a legacy, simplified WeChat bot and are comfortable maintaining a heavily divergent codebase. For most adopters, upstream is the better default because this fork is stale and appears far behind on the modern agent, web, skills, and tooling features.

Fork comparison

hanfangyuan4396/dify-on-wechat

54/100

slowing

substantial

Choose this fork if Dify integration and GeWeChat stability are your priority. Choose upstream if you want the newest agent, browser, skills, and web-console work with less maintenance risk.

Likely purpose

Replace or extend the upstream assistant with a Dify-integrated WeChat deployment, while shifting some channel support toward GeWeChat and related operational tooling.

Best for

Teams already using Dify and wanting a WeChat-facing assistant; Operators who prioritize stable WeChat connectivity over staying close to upstream; Developers comfortable maintaining a highly customized fork; Users who need channel-specific adaptations more than the latest upstream agent features

Additional features

Dify backend integration for LLMOps-style model and workflow management
GeWeChat support for a more stable WeChat connection path than itchat
Expanded channel-specific handling in the WeChat service and message layers
Custom web UI changes for running and managing the bot
Additional bot integrations such as Coze and WeCom service support
Jina-based summarization workflow enhancements

Missing features

The fork is 363 commits behind upstream, so it likely misses newer upstream work and fixes
It likely lacks recent upstream additions such as personal WeChat channel support
It likely lacks upstream QQ channel support and the latest Web Console upgrades
It likely misses newer upstream browser, skills, memory, and Web Search improvements
It likely lags on recent CLI and skill-install fixes, including skill hub mirror support
It trails upstream by 363 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Better fit for teams standardized on Dify
More attractive if WeChat stability is the main deployment concern
Broader customization around specific channels and web tooling
Large divergence suggests the fork is tailored rather than minimally patched

Risks

Significant upstream lag increases merge and maintenance burden
New upstream agent features may be absent or harder to backport
Channel-specific changes can make troubleshooting and upgrades more complex
Operational behavior may differ materially from upstream documentation

zhayujie/chatgpt-on-wechat · Discofork