Columbus said:Interesting, another stealth browser. They still use playwright. Every stealth/multi-login browser uses playwright or puppeteer.
They just modify some flags😁.
Anyways there will always be ways to bypass antibot systems😁.
What matter is the source code is public open available.
They support both : Puppeteer & Playwright. FAQ they mentioned them.
They support Python:
from cloakbrowser import launch
browser = launch()
page = browser.new_page()
page.goto("protected-site.com") # no more blocks
browser.close()
JavaScript (Playwright):
import { launch } from 'cloakbrowser';
const browser = await launch();
const page = await browser.newPage();
await page.goto('https://protected-site.com');
await browser.close();
Also works with Puppeteer: import { launch } from 'cloakbrowser/puppeteer
Why CloakBrowser?
Config-level patches break — playwright-stealth, undetected-chromedriver, and puppeteer-extra inject JavaScript or tweak flags. Every Chrome update breaks them. Antibot systems detect the patches themselves.
CloakBrowser patches Chromium source code — fingerprints are modified at the C++ level, compiled into the binary. Detection sites see a real browser because it is a real browser.
Source-level stealth — C++ patches handle fingerprints (GPU, screen, UA, hardware reporting) at the binary level. No JavaScript injection, no config-level hacks. Most stealth tools only patch at the surface.
Same behavior everywhere — works identically local, in Docker, and on VPS. No environment-specific patches or config needed.
Works with AI agents and automation frameworks — drop-in stealth for browser-use, Crawl4AI, Scrapling, Stagehand, LangChain, Selenium, and more. See integrations.
CloakBrowser doesn't solve CAPTCHAs — it prevents them from appearing. No CAPTCHA-solving services, no proxy rotation built in — bring your own proxies, use the Playwright API you already know.
