Playwright and Puppeteer over CDP

Use the browser already running in your computer when you need a human and an automation client to see the same pages. A CDP session grants control of that browser; it is not a general access token.

Connect to the existing browser

Create or resume the computer and wait for running plus ready. Request a browser session through POST /computers/{id}/browser/sessions, retaining the returned ws_url and expiry privately. Python Playwright uses chromium.connect_over_cdp with that URL; TypeScript uses chromium.connectOverCDP. Puppeteer uses connect with browserWSEndpoint. The SDK's browser.connect_playwright / browser.connectPlaywright helpers own the same exchange. See the generated Python, TypeScript and browser API signatures before adapting a call.

Work in the browser's existing context and page rather than launching another local browser. A session URL can contain a credential: never put it in logs, shell history, reports or shared configuration. Close the Playwright/Puppeteer connection in finally; delete the CE browser session when finished.

Expiry, revocation and recovery

The effective authorization deadline is capped by the parent credential. Session revocation or account suspension ends the socket. A reconnect requires fresh authorization; retrying an expired URL does not renew it. Resolve the computer's current state, obtain a new session and reconnect. Do not replay a page action whose outcome is unknown merely because the connection failed.

Observe the same work

A separate view-only desktop session lets a person watch the browser. Use a control session only when the person needs to act. Human control arbitration is independent of CDP authorization; a 4009 conflict needs explicit handoff rather than competing clicks. See Browser streaming, Desktop and Agent handoff.

Dory is in development; these pages describe the planned service and may change. Questions: support@computeengines.com.