Skip to main content
Browser Sessions are currently in invite-only preview. Access is enabled for approved organizations, and API routes, SDK method names, response fields, limits, and pricing may change before general availability.
Browser Sessions create managed Chromium sessions for web agents and browser automation. OpenComputer handles API-key auth and org ownership, then returns browser connection URLs for tools such as Playwright and Magnitude. If your organization has not been invited to the preview, Browser Session API calls may fail even when your OpenComputer API key is valid. Use Browser Sessions when you want a cloud browser without installing Chromium inside an OpenComputer sandbox. Use sandboxes when you need a full Linux VM with your own browser runtime and filesystem.

Create a Browser

Headful browsers return a live-view URL. Headless browsers are lighter, but do not provide a live view. Telemetry is enabled by default for all browser sessions. Set telemetry: false / telemetry=False to disable it, or pass a Kernel telemetry configuration object directly. Replay recording is disabled by default. Set recording: true / recording=True to enable replay recording for a headful browser session.

Profile Auth Checks

Saved profiles can start an asynchronous auth check for a site. The SDK returns a run immediately; wait() polls with short requests until the run completes.
TypeScript
Auth checks are read-only. They create temporary browser sessions with profile saving disabled and compare the saved profile against a fresh browser when compareFresh is enabled.

Playwright

The browser response includes a CDP WebSocket URL. Pass it directly to Playwright’s connectOverCDP.

Magnitude

Magnitude can use a Playwright-connected browser. Create the OpenComputer browser first, connect over CDP, then hand the page to your Magnitude agent.
TypeScript
Magnitude package names and constructors can vary by version. The OpenComputer-specific step is stable: create a Browser, connect to cdpWsUrl with Playwright, then pass the resulting page or browser object to Magnitude.

Save and Load Profiles

Profiles persist browser state such as cookies and local storage across browser sessions. Profiles are scoped to your OpenComputer org; another org cannot list, load, or delete your profiles. Create a profile once:
Use the profile when creating a browser:
Load the same profile later by ID or name:

Authentication

The SDK uses your OpenComputer API key:
For local development against a non-production Browser Sessions endpoint, set OPENCOMPUTER_BROWSER_API_URL.