head to head · open source
Browser Use vs page-agent
Browser Use has 120,062 GitHub stars, 13,388 forks, 421 open issues and last shipped yesterday. page-agent has 29,634 stars, 2,642 forks, 94 open issues and last shipped 2 days ago. Browser Use leads on adoption by 305% (120,062 vs 29,634 stars). Browser Use is written in Python under MIT; page-agent is written in TypeScript under MIT. Browser Use has attracted 11% as many forks as stars, page-agent 9%. Browser Use was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 3 topic tags (ai-agents, browser-automation, mcp), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| Browser Use | page-agent | |
|---|---|---|
| GitHub stars | ★ 120K | ★ 30K |
| License | MIT | MIT |
| Written in | Python | TypeScript |
| Last push | 2026-11-05 | 2026-11-04 |
| Forks | ⑂ 13K | ⑂ 2.6K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Browser Use if
- You weight community size — 120K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick page-agent if
- You want the page-agent feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches TypeScript
- You evaluated both and page-agent fits your workflow better
About Browser Use
Navigate the web like a human does. Find an available slot, pick a date and time, handle the CAPTCHA, and book a driving test. Explore more demos and prompts ↗ Which Browser Use do I need? Path 1: Fully Hosted Cloud: Scale up with a fully hosted agent and browser. Path 2: CLI: Automate your own browser tasks. Path 3: Python Library: Run the open source Browser Use agent locally from your own code. Quickstart Path 1: Fully Hosted Cloud Scale browser automation with our hosted agent, stealth browsers, and infrastructure for profiles, recordings, and data policies. Get started with the API ↗ New Google, GitHub, or…
read the full Browser Use overview →
About page-agent
Page Agent The GUI Agent Living in Your Webpage. One script gives any web page its own AI agent. 🌐 English 中文 🚀 Demo 📖 Docs 📢 HN Discussion 𝕏 Follow on X ✨ Features 🎯 Easy integration No need for browser extension / python / headless browser . Just in page javascript. Everything happens in your web page. 📖 Text based DOM manipulation No screenshots. No multi modal LLMs or special permissions needed. 🧠 Bring your own LLMs Works with most mainstream models, including locally deployed ones. See supported models. 🐙 Optional chrome extension for multi page tasks. And an MCP Server (Beta) to control it from…
read the full page-agent overview →
More in Data & Analytics
Related comparisons
More Data Extraction & Web Scraping projects
Compare either of these against the rest of the Data Extraction & Web Scraping field.
Frequently asked questions
Is Browser Use or page-agent more popular?
Browser Use has 120,062 GitHub stars and page-agent has 29,634. Browser Use has the larger community by that measure.
Are Browser Use and page-agent free?
Both are open source. Browser Use is licensed under MIT and page-agent under MIT. Neither carries a licence fee.
What is the difference between Browser Use and page-agent?
Browser Use is written in Python and page-agent in TypeScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Browser Use or page-agent?
Choose Browser Use if you want the larger community (120,062 stars) or its MIT licence terms. Choose page-agent if its feature set, stack or MIT licence fits better. Both are self-hostable.