PUPPETEER

Point Puppeteer at a remote browserWSEndpoint.

Remote Browser gives Puppeteer scripts a hosted Chromium endpoint with profile-aware sessions, proxy-ready egress, live viewing, and session recording.

Connect Puppeteer Open framework docs

puppeteer.tsremote

import puppeteer from "puppeteer-core";

const browser = await puppeteer.connect({
  browserWSEndpoint:
    "wss://brapi.remote-browser.dev/connect?apiKey=YOUR_API_KEY"
});
const [page] = await browser.pages();
await page.goto("https://example.com");
await browser.close();

WSSbrowser endpoint

API keysession auth

recordoptional replay

Drop-in connection shape

Use puppeteer.connect with the Remote Browser WebSocket endpoint and continue with normal Puppeteer APIs.

Runtime controls

Set region, profile, recording, proxy, timeout, and launch arguments when the browser is created.

Human-visible debugging

When a script stalls, open the viewer to inspect popups, auth state, visual layout, and page progress.

Workflow

From browser creation to evidence.

Create a session

Start a remote browser through the dashboard API or a plugin and read the cdpUrl from the response.

Attach Puppeteer

Pass the cdpUrl as browserWSEndpoint to puppeteer.connect.

Close cleanly

Call browser.close or terminate the remote session through the API when the workflow is done.

FAQ

Short answers for searchers and AI crawlers.

Do I need full Puppeteer or puppeteer-core?

puppeteer-core is enough because Remote Browser provides the Chromium runtime.

Can I pass Chrome launch arguments?

Yes. Remote Browser accepts launch arguments at browser creation time for workflows that need explicit flags.

Can Puppeteer use persistent profiles?

Yes. Create or select a Remote Browser profile before connecting Puppeteer so the browser starts with stored state.

Keep moving through the browser automation map.