Skip to content
DevUtils Online

AI Agents

cherry-studio vs gemini-cli

gemini-cli leads by 12.1 · clear

B · leads

gemini-cli

97.9

108,897 stars · Apache-2.0

cherry-studio versus gemini-cli is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 85.8 for cherry-studio and 97.9 for gemini-cli.

gemini-cli has 108,897 GitHub stars to cherry-studio's 53,594, a gap of 55,303 (2.03×). Forks are 5,231 for cherry-studio and 14,956 for gemini-cli. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 89 versus 100.

Push history: cherry-studio was last pushed on 17 November 2026 (0 days ago), and gemini-cli was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,788 for cherry-studio (0.052 per star) and 739 for gemini-cli (0.007 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.

cherry-studio is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. gemini-cli is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 52 for cherry-studio and 96 for gemini-cli. This is a procurement signal, not legal advice.

In AI Agents, both cherry-studio (53,594 stars) and gemini-cli (108,897 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: cherry-studio is open source, gemini-cli is open source.

gemini-cli is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).

gemini-cli finishes ahead at 97.9 against cherry-studio at 85.8, a 12.1 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

cherry-studio versus gemini-cli metrics
Signal cherry-studio gemini-cli
GitHub stars 53,594 108,897
Forks 5,231 14,956
Open issues 2,788 739
Adoption 94 100
Activity 100 100
Community 89 100
Issue health 52 84
License 52 96
Self-hosting 100 100
Composite 85.8 97.9

Questions this page answers

Which has more GitHub stars, cherry-studio or gemini-cli?

gemini-cli has more GitHub stars: 108,897 versus 53,594 for cherry-studio. The gap is 55,303 stars.

Which was updated more recently, cherry-studio or gemini-cli?

Both were last pushed on 17 November 2026.

Can I self-host both cherry-studio and gemini-cli?

Yes. This catalog marks both cherry-studio and gemini-cli as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, cherry-studio or gemini-cli?

cherry-studio is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. gemini-cli is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the cherry-studio vs gemini-cli score?

gemini-cli scores 97.9 and cherry-studio scores 85.8. This page calls that a clear lead for gemini-cli.

Related comparisons