CherryHQ/cherry-studio

Choose upstream unless you need this exact fork namespace for your own customization work. For end users, it is effectively the same product but older.

Choose this fork only if its provider-specific changes match your stack. If you want the broadest assistant coverage, latest fixes, and lower maintenance risk, upstream looks like the safer default.

Choose this fork if you want a more opinionated Cherry Studio with provider and localization tweaks, plus some Linux and export workflow improvements. Avoid it if you want the most current upstream agent, plugin, and maintenance fixes with lower merge risk.

Prefer this fork if you need the HarmonyOS pad direction and can live with upstream lag and some removed integrations. Prefer upstream if you want the broadest feature set, fastest fixes, and lower maintenance risk.

Choose this fork if your priority is provider compatibility and downstream control, especially around Aliyun/Qwen/Kimi-style model support and agent behavior. Choose upstream if you want the broadest feature set, the fastest cadence, and the least maintenance burden.

Adopt this only if you specifically want a near-upstream snapshot to customize. If you want the newest agent, updater, and compatibility fixes, upstream looks like the better default.

Choose this fork only if its extra provider/workflow changes match your needs and you are prepared to maintain a stale, highly divergent codebase. If you want current upstream features, broad assistant coverage, and lower maintenance risk, upstream is the safer choice.

Choose this fork if you want added MCP, prompt, and backup workflow customization and are comfortable owning merge debt. Choose upstream if you want the most current, broadly maintained Cherry Studio with the least compatibility risk.