head to head · open source

CloakBrowser vs auto-browser

CloakBrowser has 33,001 GitHub stars, 2,741 forks, 169 open issues and last shipped yesterday. auto-browser has 929 stars, 154 forks, 1 open issues and last shipped 4 days ago. CloakBrowser leads on adoption by 3,452% (33,001 vs 929 stars). CloakBrowser is written in Python under MIT; auto-browser is written in Python under MIT. CloakBrowser has attracted 8% as many forks as stars, auto-browser 17%. CloakBrowser 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, playwright), 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.

CloakBrowser ★ 33K auto-browser ★ 929 category Data & Analytics

← all 20902 open source comparisons

Side by side

CloakBrowser auto-browser
GitHub stars ★ 33K ★ 929
License MIT MIT
Written in Python Python
Last push 2026-11-20 2026-11-17
Forks ⑂ 2.7K ⑂ 154
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

full CloakBrowser profile →

pick auto-browser if

  • You want the auto-browser feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches Python
  • You evaluated both and auto-browser fits your workflow better

full auto-browser profile →

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 auto-browser

Auto Browser Give your AI agent a real browser, with a human in the loop. Auto Browser is an MCP native browser control plane for authorized workflows. It gives MCP clients, LLM agents, and operators a shared Playwright browser with human takeover, reusable auth profiles, approvals, audit trails, and local first deployment. Works with: Claude Code, Codex (CLI, IDE extension, and app), Google Antigravity, Cursor, and VS Code, connected directly over HTTP Claude Desktop, through the bundled stdio bridge any MCP client that can talk HTTP or stdio direct REST callers when you want curl first control Why Auto Browser…

read the full auto-browser 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 auto-browser more popular?

CloakBrowser has 33,001 GitHub stars and auto-browser has 929. CloakBrowser has the larger community by that measure.

Are CloakBrowser and auto-browser free?

Both are open source. CloakBrowser is licensed under MIT and auto-browser under MIT. Neither carries a licence fee.

What is the difference between CloakBrowser and auto-browser?

CloakBrowser is written in Python and auto-browser in Python. 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 auto-browser?

Choose CloakBrowser if you want the larger community (33,001 stars) or its MIT licence terms. Choose auto-browser if its feature set, stack or MIT licence fits better. Both are self-hostable.