Browser automation (CDP)

Browser automation uses a CDP session on the guest's Chromium instance. This is distinct from the human noVNC viewer. The returned WebSocket URL contains a session secret: keep it private and do not place it in logs, public issue reports or screenshots.

Connect to the returned session

Create the session through the browser-scoped data API. Use the returned ws_url and expires_at rather than constructing a host or extending the expiry locally. Playwright/Puppeteer reconnects may use that secret URL because they cannot reliably add the access header on every reconnect. Revocation and the parent authorization deadline still apply.

The SDK connect_playwright helper binds to the supplied BrowserType.connect_over_cdp. The synchronous SDK uses the caller's synchronous Playwright client; the asynchronous SDK awaits its asynchronous client. Close the returned browser connection and retained CE session according to their separate ownership. A disconnected transport does not stop a computer or cancel its billing.

Shared page and launch limits

Desktop launch and CDP observe the same guest browser. Launch Chromium rather than assuming Google Chrome is distributed; Chrome installation is the customer's own optional action. See CDP streaming and Playwright guide.

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