head to head · open source
CloakBrowser vs page-agent
CloakBrowser has 32,726 GitHub stars, 2,720 forks, 164 open issues and last shipped 3 days ago. page-agent has 29,634 stars, 2,642 forks, 94 open issues and last shipped 2 days ago. CloakBrowser leads on adoption by 10% (32,726 vs 29,634 stars). CloakBrowser is written in Python under MIT; page-agent is written in TypeScript under MIT. CloakBrowser has attracted 8% as many forks as stars, page-agent 9%. page-agent was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (ai-agents, browser-automation), 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
| CloakBrowser | page-agent | |
|---|---|---|
| GitHub stars | ★ 33K | ★ 30K |
| License | MIT | MIT |
| Written in | Python | TypeScript |
| Last push | 2026-11-03 | 2026-11-04 |
| Forks | ⑂ 2.7K | ⑂ 2.6K |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick CloakBrowser if
- You weight community size — 33K 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 CloakBrowser
Stealth Chromium that passes every bot detection test. Not a patched config. Not a JS injection. A real Chromium binary with fingerprints modified at the C++ source level. Antibot systems score it as a normal browser — because it is a normal browser. Cloudflare Turnstile — 3 live tests passing (headed mode, macOS) Drop in Playwright/Puppeteer replacement for Python and JavaScript. Same API, same code — just swap the import. 3 lines of code, 30 seconds to unblock. 87 source level C++ patches — canvas, WebGL, audio, fonts, GPU, screen, WebRTC, network timing, automation signals, CDP input behavior humanize=True —…
read the full CloakBrowser 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 CloakBrowser or page-agent more popular?
CloakBrowser has 32,726 GitHub stars and page-agent has 29,634. CloakBrowser has the larger community by that measure.
Are CloakBrowser and page-agent free?
Both are open source. CloakBrowser is licensed under MIT and page-agent under MIT. Neither carries a licence fee.
What is the difference between CloakBrowser and page-agent?
CloakBrowser 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, CloakBrowser or page-agent?
Choose CloakBrowser if you want the larger community (32,726 stars) or its MIT licence terms. Choose page-agent if its feature set, stack or MIT licence fits better. Both are self-hostable.