CloakHQ/CloakBrowser is an open source project for browser automation. It is not just a Playwright configuration file or a small JavaScript patch. The project is built around a custom Chromium binary, aiming to make browser fingerprints, WebGL, Canvas, audio, fonts, GPU, screen data, WebRTC, and network timing look closer to a normal browser environment.

Project URL: https://github.com/CloakHQ/CloakBrowser

At the time of writing, the GitHub API showed about 15k stars, Python as the main language, and an MIT license. The README positions it very directly: a Stealth Chromium launcher that can replace the default Playwright or Puppeteer browser launcher.

What Problem Does It Solve

Many automation scripts expose obvious automation signals when they run in a regular Headless Chromium environment, for example:

• navigator.webdriver.
• Headless user agent traces.
• Unnatural plugin, font, screen, and GPU fingerprints.
• CDP behavior that does not match real user input.
• Temporary profiles without normal browsing traces.

CloakBrowser moves part of this work into the Chromium source and binary layer, instead of relying only on runtime configuration or JavaScript patches. For Playwright users, the API still feels close to familiar browser automation, but the underlying browser is replaced with the custom build provided by the project.

This type of tool is suitable for compliant automation testing, site compatibility checks, anti-abuse system self-testing, and agent browser environment experiments. It should not be used for unauthorized access, account abuse, bypassing platform risk controls, or violating service terms.

Basic Usage

Python installation:

1

pip install cloakbrowser

JavaScript / Node.js installation:

1

npm install cloakbrowser playwright-core

The Python example in the README looks close to Playwright:

1
2
3
4
5
6

from cloakbrowser import launch

browser = launch()
page = browser.new_page()
page.goto("https://protected-site.com")
browser.close()

The JavaScript usage is also straightforward:

1
2
3
4
5
6

import { launch } from 'cloakbrowser';

const browser = await launch();
const page = await browser.newPage();
await page.goto('https://protected-site.com');
await browser.close();

Browser Profile Manager

CloakBrowser also provides a Browser Profile Manager. It is meant for managing browser profiles, testing environments, and repeated automation tasks more conveniently.

1

docker run -p 8080:8080 -v cloakprofiles:/data cloakhq/cloakbrowser-manager

After starting it, open:

1

http://localhost:8080

The value of a profile manager is that the browser environment does not have to be a disposable temporary profile every time. For long-running tests, compatibility checks, and agent experiments, stable profiles are often easier to debug.

How It Differs From Regular Playwright

Regular Playwright focuses on reliable browser control. CloakBrowser focuses on making the browser environment itself look more natural.

In practice, the difference is:

• Playwright provides the automation API.
• CloakBrowser provides a custom browser runtime.
• Playwright is suitable for general testing and automation.
• CloakBrowser is more focused on realistic browser behavior and fingerprint consistency.

This does not mean CloakBrowser can magically solve all detection problems. Websites can still use behavior, frequency, account reputation, network environment, and business rules to judge risk.

What To Watch Out For

First, compliance matters. A more realistic automation environment does not mean unrestricted use. Automated access should respect authorization, rate limits, robots or platform rules, and service terms.

Second, the project depends on a custom Chromium build. Teams should pay attention to version compatibility, security updates, and whether the binary source is acceptable for production use.

Third, realistic browser behavior is only one part of the picture. If the script performs unnatural operations, sends requests too frequently, or uses accounts in abnormal ways, the result will still be risky.

Who It Is For

CloakBrowser is more suitable for developers and teams already using Playwright, Puppeteer, browser agents, QA automation, or web compatibility testing. It is less suitable for users who just want a no-code browser automation product.

Summary

CloakBrowser is interesting because it moves browser automation from “just control a headless browser” toward “use a browser environment closer to real users.” For testing, agent experiments, and controlled research, it is worth watching. For real-world use, the important boundary is still compliance, authorization, and risk control.