BROWSER AUTOMATION API

Browser automation with a real remote session.

Use Remote Browser when automation needs JavaScript, clicks, auth state, screenshots, downloads, or a human-visible debugging surface.

Automate a browser View Playwright docs

automation-flow.tsremote

const session = await createRemoteBrowser({
  region: "auto",
  profileName: "qa-account",
  recordingEnabled: true
});

const browser = await chromium.connectOverCDP(session.cdpUrl);
const page = browser.contexts()[0]!.pages()[0]!;
await page.goto("https://app.example.com");

QAtest workflows

agentsbrowser tasks

monitorscheduled checks

Real browser surface

Run against Chromium instead of an HTTP fetch when page behavior depends on scripts, state, visual layout, or interactions.

Evidence by default

Use screenshots, live viewing, and recording links to understand what happened during a run.

Controlled runtime

Browser-hour metering, concurrent session limits, viewer limits, and idle timeout make runtime easier to budget.

Workflow

From browser creation to evidence.

Provision

Create a browser session with the options required for the task.

Execute

Drive the browser with Playwright, Puppeteer, browser-use, an agent, or your own CDP client.

Inspect

Use viewer and recording artifacts for debugging, audit trails, and handoff between engineering and operations.

FAQ

Short answers for searchers and AI crawlers.

Is this for scraping only?

No. Scraping is one use case. Remote Browser also fits QA, SEO audits, monitoring, agent workflows, and authenticated operations.

Does Remote Browser execute the task logic?

Remote Browser provides the browser runtime. Your script, agent, or integration decides what actions to take.

Can humans watch the automation?

Yes. Each browser can expose a live viewer subject to plan limits.

Keep moving through the browser automation map.