Skip to content
DevUtils Online

AI Agents

browser-use vs cherry-studio

browser-use leads by 13.4 · clear

browser-use versus cherry-studio is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. browser-use is written mainly in Python; cherry-studio is written mainly in TypeScript. The composite score is 99.1 for browser-use and 85.7 for cherry-studio.

browser-use has 121,292 GitHub stars to cherry-studio's 53,594, a gap of 67,698 (2.26×). Forks are 13,561 for browser-use and 5,231 for cherry-studio. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 90.

Push history: browser-use was last pushed on 17 November 2026 (0 days ago), and cherry-studio was last pushed on 17 November 2026 (0 days ago). Open issues stand at 596 for browser-use (0.005 per star) and 2,788 for cherry-studio (0.052 per star). Issue-health scores are 96 and 52; activity scores are 100 and 100.

browser-use is listed as MIT, 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. 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. License scores in this pair are 96 for browser-use and 52 for cherry-studio. This is a procurement signal, not legal advice.

In AI Agents, both browser-use (121,292 stars) and cherry-studio (53,594 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: browser-use is open source, cherry-studio is open source.

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

browser-use finishes ahead at 99.1 against cherry-studio at 85.7, a 13.4 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.

browser-use versus cherry-studio metrics
Signal browser-use cherry-studio
GitHub stars 121,292 53,594
Forks 13,561 5,231
Open issues 596 2,788
Adoption 100 93
Activity 100 100
Community 100 90
Issue health 96 52
License 96 52
Self-hosting 100 100
Composite 99.1 85.7

browser-use

Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, browser-use or cherry-studio?

browser-use has more GitHub stars: 121,292 versus 53,594 for cherry-studio. The gap is 67,698 stars.

Which was updated more recently, browser-use or cherry-studio?

Both were last pushed on 17 November 2026.

Can I self-host both browser-use and cherry-studio?

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

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

browser-use is listed as MIT, 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the browser-use vs cherry-studio score?

browser-use scores 99.1 and cherry-studio scores 85.7. This page calls that a clear lead for browser-use.

Related comparisons