CCloud Releases
Home
Following

Cloud Releases

Service catalogues and updates come from each provider's public product listing and announcements.

Explore

  • Home
  • Latest updates
  • Following

About

  • About
  • Contact
  • Privacy Policy
  • Terms of Use

Providers

  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud
  • Cloudflare

Not affiliated with any cloud provider. Product names and logos belong to their owners.

  1. Providers
  2. ›Cloudflare
  3. ›Browser Run
  4. ›Update

Feature•Sep 29, 2026

Connect multiple clients to one Browser Run session

Browser RunCloudflare · Developer platform

Browser Run sessions now accept multiple concurrent connections. Before, a session accepted only one connection at a time, and other Workers had to wait until that connection closed. Now multiple Workers can connect to the same browser at the same time.

Each puppeteer.connect() call opens its own Chrome DevTools Protocol (CDP) connection. Create a separate browser context for each request to keep its pages, cookies, and storage apart from other clients.

const browser = await puppeteer.connect(env.MYBROWSER, sessionId); const context = await browser.createBrowserContext(); try { const page = await context.newPage(); await page.goto("https://example.com"); // ... } finally { await context.close(); await browser.disconnect(); // keep the shared browser running }

const browser = await puppeteer.connect(env.MYBROWSER, sessionId); const context = await browser.createBrowserContext(); try { const page = await context.newPage(); await page.goto("https://example.com"); // ... } finally { await context.close(); await browser.disconnect(); // keep the shared browser running }

Sharing sessions means fewer new browsers to launch, less cold-start time, and fewer concurrent browsers counted against your limits.

Concurrent connections require @cloudflare/puppeteer version 1.1.0 or later.

Refer to Reuse sessions for a full example.

Read the original announcement↗

More from Browser Run

All Browser Run updates →
  1. Browser Run adds WebMCP to Kitesurf and moves to document.modelContext

    WebMCP now works in Kitesurf sessions as well as Lab sessions. Both backends use the document.modelContext API from the WebMCP Community Group draft. Lab sessions no longer expose navigator.modelContextTesting.

    Browser Run•Feature•Sep 28, 2026
  2. Subscribe to Browser Run crawl events

    Browser Run crawl jobs can publish lifecycle events to Cloudflare Queues. Subscribe to started, updated, and finished events to track progress or trigger downstream processing without polling.

    Browser Run•Feature•Sep 25, 2026
  3. Browser Run adds session and DevTools methods to browser bindings

    Browser Run browser bindings now provide typed methods for session management and DevTools operations. You can acquire a session, connect a browser client, create Live View URLs, manage targets, and close sessions without constructing HTTP requests.

    Browser Run•Feature•Sep 21, 2026
  4. Inspect logs, network requests, and DOM in Session Recordings

    Browser Run Session Recordings now include an Inspect panel, giving you more context to understand what happened during a browser session without having to reproduce it.

    Browser Run•Feature•Sep 18, 2026
  5. Control which hostnames Browser Run sessions can access

    Browser Run now supports guardrails, which limit a browser session's HTTP and HTTPS requests to permitted hostnames.

    Browser Run•Feature•Sep 14, 2026