Integrations / Automation libraries

Your automation library, in a real profile.

Start a Browz profile through the local API and attach your library over the Chrome DevTools Protocol. Your code stays the same; the browser it drives keeps its own cookies, fingerprint and proxy.

See the guides Download Browz

Start a profile, then attach

const session = await browz.browser.start(id);
const browser = await chromium.connectOverCDP(session.cdpEndpoint);

Automation libraries

Pick your library.

Playwright

connectOverCDP to a Browz profile: its own cookies, fingerprint and proxy.

Read the guide

Playwright for Python

connect_over_cdp from Python, with a profile that keeps its sign-in.

Read the guide

Puppeteer

puppeteer.connect to a running profile; disconnect, never close.

Read the guide

Selenium

ChromeDriver attaches with debuggerAddress; match its major version.

Read the guide

browser-use

Hand browser-use a Browz profile’s CDP URL instead of its own browser.

Read the guide

Stagehand

Stagehand 3 attaches to a Browz profile with cdpUrl.

Read the guide

Raw CDP

Plain WebSocket and fetch to a profile’s DevTools endpoint, no library.

Read the guide

Local REST API

Create, start, navigate, screenshot and stop profiles with curl.

Read the guide

browz CLI

Create, start and stop profiles from a shell script.

Read the guide

How it works

Start, attach, stop.

Start the profile through Browz
The local API (or the SDK, or the CLI) starts the profile with its fingerprint and proxy and answers with its DevTools endpoint.
Attach your library
connectOverCDP, puppeteer.connect, ChromeDriver’s debuggerAddress, or a CDP URL for agent frameworks. Never let the library launch its own browser.
Stop it through Browz
Disconnect the library, then stop the profile through Browz so it saves its cookies and storage cleanly.

FAQ

About automation libraries.

Why not just use the library’s own browser?

A library-launched browser is fresh every time, carries automation flags and looks like the same machine for every run. A Browz profile keeps its sign-ins and has its own fingerprint and proxy.

Do I need to change my scripts?

Only how the browser starts: replace launch() with a start call and a connect. Page code stays the same.

Which engines can I attach to?

The Browz engine and Installed Chrome profiles both expose CDP. Installed Chrome profiles always open a window.