AI agents

Run AI browser agents that pass bot detection.

Connect an AI agent to an AliasMode profile over Playwright CDP. Because every profile opens in CloakBrowser, the agent browses with the signals of a normal human-driven Chrome browser instead of getting stopped by bot checks.

Download AliasMode free Connect an agent over CDP

CDPStandard agent connection

0.9reCAPTCHA v3 score (rated human)

LocalNo cloud browser vendor required

Connect the agent

Start a profile through the Local API, then connect the agent framework to the returned Chrome DevTools Protocol endpoint. Any framework that speaks CDP, including Playwright-based agents, browser-use, or custom loops, can drive the opened profile.

Follow the Playwright connection Read the Local API reference

Why agents get blocked elsewhere

Most agents run on stock Playwright or headless Chrome, which detection services flag quickly: reCAPTCHA v3 scores them as bots, Turnstile fails, and the TLS fingerprint does not match a real browser. CloakBrowser is patched at the browser source level, so the checks below pass.

Read about the runtime

Keep agent work authorized

Point agents only at sites and accounts you are authorized to access, respect each service’s terms, and keep one agent per active profile. The AliasMode acceptable use policy applies to automated sessions too.

Review acceptable use Set up profiles

Bot detection test results

Detection test results

Tested against live bot-detection services.

Every AliasMode profile opens in CloakBrowser, a Chrome-based runtime patched at the source, so websites see a normal human-driven browser, not an automation tool. Here is how it compares on the public detection services that platforms use to screen visitors.

All tests verified against live detection services. Last tested: Jul 2026 (Chromium 150).

Detection service	Standard automated browser	CloakBrowser	Notes
reCAPTCHA v3	0.1 (bot)	0.9 (human)	Server-side verified
Cloudflare Turnstile (non-interactive)	FAIL	PASS	Auto-resolve
Cloudflare Turnstile (managed)	FAIL	PASS	Single click
ShieldSquare	BLOCKED	PASS	Production site
FingerprintJS bot detection	DETECTED	PASS	demo.fingerprint.com
BrowserScan bot detection	DETECTED	NORMAL (4/4)	browserscan.net
bot.incolumitas.com	13 fails	PASS	Bot checks passed
deviceandbrowserinfo.com	6 true flags	0 true flags	isBot: false
`navigator.webdriver`	true	false	Source-level patch
`navigator.plugins.length`	0	5	Real plugin list
`window.chrome`	undefined	object	Present like real Chrome
`UA string`	HeadlessChrome	Chrome/150.0.0.0	No headless leak
`CDP detection`	Detected	Not detected	isAutomatedWithCDP: false
`TLS fingerprint`	Mismatch	Identical to Chrome	ja3n/ja4/akamai match

A standard automated browser is out-of-the-box Playwright or headless Chrome/Chromium, the default setup most automation scripts and bots use.

Point-in-time results from independent public test services; you can reproduce them yourself against a CloakBrowser profile. Detection vendors update their checks continuously, and no browser can guarantee a pass on every service forever.