PLAYWRIGHT

Run Playwright against a hosted Chromium session.

Use Playwright locally while the browser runs remotely. Keep your test code, swap browser launch for connectOverCDP, and gain live viewer, profiles, recordings, and remote infrastructure.

Connect Playwright Open framework docs

playwright.tsremote

import { chromium } from "playwright";

const cdpUrl =
  "wss://brapi.remote-browser.dev/connect?apiKey=YOUR_API_KEY&region=auto";

const browser = await chromium.connectOverCDP(cdpUrl);
const page = browser.contexts()[0]?.pages()[0] ?? await browser.newPage();
await page.goto("https://example.com");
console.log(await page.title());

1 URLCDP endpoint

2Kdefault resolution

idletimeout controls

No local Chrome dependency

Run Playwright from CI, a local agent, or a server while Chromium lives in Remote Browser.

Debug the real session

Open the live viewer to see the page, modal, login prompt, or flaky state that Playwright is interacting with.

Reuse account state

Attach a profile name or profile ID so authenticated test flows can start from a prepared browser state.

Workflow

From browser creation to evidence.

Replace launch

Use chromium.connectOverCDP instead of chromium.launch when you want the browser runtime to be remote.

Keep test logic

Selectors, navigation, screenshots, downloads, and assertions continue to use Playwright APIs.

Collect evidence

Use viewer URLs, recordings, and status endpoints when a run needs human inspection or a reproducible report.

FAQ

Short answers for searchers and AI crawlers.

Does Remote Browser require a custom Playwright SDK?

No. Playwright can connect over CDP with the official chromium.connectOverCDP API.

Can I use it from CI?

Yes. Store the API key as a CI secret, create a browser session, connect over CDP, and terminate the session after the job.

Can Playwright still take screenshots?

Yes. Playwright screenshots work normally, and Remote Browser can also keep session-level recording when enabled.

Keep moving through the browser automation map.