A · leads
browser-use
99.0
121,292 stars · MIT
AI Agents
browser-use leads by 1.4 · narrow
A · leads
99.0
121,292 stars · MIT
B
97.6
108,897 stars · Apache-2.0
browser-use 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. browser-use is written mainly in Python; gemini-cli is written mainly in TypeScript. The composite score is 99.0 for browser-use and 97.6 for gemini-cli.
browser-use has 121,292 GitHub stars to gemini-cli's 108,897, a gap of 12,395 (1.11×). Forks are 13,561 for browser-use and 14,956 for gemini-cli. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 99 versus 100.
Push history: browser-use 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 596 for browser-use (0.005 per star) and 739 for gemini-cli (0.007 per star). Issue-health scores are 96 and 84; 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. 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 96 for browser-use and 96 for gemini-cli. This is a procurement signal, not legal advice.
In AI Agents, both browser-use (121,292 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: browser-use is open source, gemini-cli is open source.
The lead is split. browser-use is furthest ahead on issue health (96 to 84), while gemini-cli is furthest ahead on fork community (100 to 99). Choose the dimension a rollout cannot compromise on.
browser-use finishes ahead at 99.0 against gemini-cli at 97.6, a 1.4 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | browser-use | gemini-cli |
|---|---|---|
| GitHub stars | 121,292 | 108,897 |
| Forks | 13,561 | 14,956 |
| Open issues | 596 | 739 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 99 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 99.0 | 97.6 |
Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.
An open-source AI agent that brings the power of Gemini directly into your terminal.
browser-use has more GitHub stars: 121,292 versus 108,897 for gemini-cli. The gap is 12,395 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both browser-use and gemini-cli as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
browser-use scores 99.0 and gemini-cli scores 97.6. This page calls that a narrow lead for browser-use.