SYSTEM Cited by 5 sources

Cloudflare Browser Rendering

Browser Rendering is Cloudflare's managed headless-browser tier: programmatically-controllable Chromium instances running at scale in Cloudflare's edge network, reachable by applications running on Workers and (via proxy) on Containers.

Framework support

Cloudflare ships adapters for the common headless-browser clients:

• Puppeteer
• Playwright
• Stagehand
• Playwright MCP — model-context-protocol wrapper for AI agents driving a browser

Applications talk to Browser Rendering over the Chrome DevTools Protocol (CDP) that Chromium-based browsers already speak.

Node.js compatibility milestone

Cloudflare notes that Playwright on Browser Rendering historically had to rely on memfs to mock a filesystem API, forcing a drift from the upstream Playwright codebase. With Workers' growing Node.js compatibility, node:fs is now natively supported — simplifying the adapter and making Playwright upgrades track upstream.

Seen in

• sources/2026-05-19-cloudflare-announcing-claude-managed-agents-on-cloudflare — canonical wiki instance of Browser Run as the agent-browser tool surface in Claude Managed Agents. The integration ships pre-bundled browser tools (browser_search, browser_execute, screenshot, browse, fetch_to_markdown, and a Cloudflare-specific web_fetch) that route the agent's browsing through Browser Run on Cloudflare infrastructure. Quoting the post: "this not only lets your agent do more, but it also makes it easy to audit every action your agent's browser is taking on the web, apply allowlists and denylist to browser sessions, and save recordings of browser sessions for future debugging." Browser Run becomes a first-class agent-observability surface — the same session-recording substrate that underpins Browser Isolation (BISO) for human users now provides the audit trail for agent-driven web actions; human-in-the-loop flows are composable with the agent's session.
• sources/2026-05-13-cloudflare-browser-run-now-running-on-cloudflare-containers-its-faster — canonical wiki instance of Browser Run's substrate migration off shared Browser Isolation (BISO) onto its own Cloudflare Containers image. Three architectural layers disclosed: (a) Regional pre-warmed pools of DO + Container pairs to bound the DO-Container cross-region RTT (canonical wiki instance of patterns/regional-pre-warmed-do-container-pair-pool); (b) Allocation-state migration from Workers KV to D1 + Queues because KV's eventual consistency (recently reduced minimum cache TTL 60s → 30s, "still too high") caused race-condition overallocation on the hot allocation path under AI-agent-builder demand spikes (canonical wiki instance of concepts/eventual-consistency-too-slow-for-allocation + patterns/transactional-db-over-eventually-consistent-kv-for-claim; the SQL UPDATE...WHERE...IN (SELECT...ORDER BY RANDOM() LIMIT ?5) RETURNING data is canonicalised at concepts/sqlite-transaction-for-atomic-resource-claim); the per-container 5-second state-update writes go through Queues at max_batch_size: 100, max_batch_timeout: 1 to amortise D1's per-row write cost (P95 batch write 0.1 ms), lifting the per-location ceiling from 5,000 → 500,000 containers (100× headroom) at <2-second steady-state queue lag — canonical wiki instance of patterns/queue-batching-amortizes-db-write-throughput; paired with patterns/region-fallback-on-queue-backlog when primary lag exceeds the staleness budget. (c) Quick-action protocol coalesced from chatty WebSocket to single HTTP request (open-page → navigate → wait-for-load → screenshot flow now executes internally on the Container) — canonical wiki instance of patterns/single-http-request-over-chatty-websocket. Headline operational outcomes disclosed verbatim: 60 browsers/min via the Workers binding, 120 concurrent (4× the previous limit), >50% reduction in Quick Action response times, with WebGL + WebMCP unblocked because Browser Run now controls its own image and Chromium-version cadence independent of BISO. Migration ran as gradual ramp via in-path Worker (Quick Actions → free Workers binding → PAYG → contract customers); transition required no customer code change. Framed as a Customer Zero deployment of DO-enabled Containers — "light on documentation, light on observability, light on colleagues in an overlapping timezone" on the Cloudflare-Containers-platform-internals side, with the "feedback loop leading to substantial upgrades" explicitly named as the discipline's payoff.
• sources/2026-01-29-cloudflare-moltworker-self-hosted-ai-agent — canonical wiki instance of the CDP-proxy pattern for browser automation. Moltbot expects a local Chromium over CDP; Moltworker instead ships a thin CDP proxy from the Sandbox container back through the Worker to Browser Rendering (via Puppeteer APIs) + a Browser Rendering skill injected into the Moltbot runtime at Sandbox start (patterns/cdp-proxy-for-headless-browser). Demo workloads: Google Maps route + screenshot to Slack, Asian-food search, ffmpeg-generated video from captured browser frames.
• sources/2026-04-15-cloudflare-project-think-building-the-next-generation-of-ai-agents — positioned as Tier 3 of the Project Think execution ladder. Agents escalate to Browser Rendering when a target system has no MCP / API and needs to be driven via "navigate, click, extract, screenshot." Integrated via createBrowserTools(env.BROWSER) in Think's getTools().
• sources/2026-04-16-cloudflare-ai-search-the-search-primitive-for-your-agents — Browser Run (2026-04-16 rebrand of Browser Rendering) is the built-in website crawler inside every AI Search instance that uses a website as its data source. "When using the website as a data source, website crawling using Browser Run (formerly Browser Rendering) is also now a built-in service, meaning that you won't be billed for it separately." Third framing of the same primitive: agent-facing tool (Moltworker CDP proxy) / generated- code-facing capability (Project Think Tier 3) / invisible-crawl- substrate (AI Search).

Related

• systems/cloudflare-workers — the compute tier that drives Browser Rendering.
• systems/cloudflare-containers — Browser Run's post-2026-05-13 substrate (migrated off shared BISO image).
• systems/cloudflare-browser-isolation — pre-2026-05-13 shared substrate; rebrand of "Browser Isolation" / BISO.
• systems/cloudflare-durable-objects — actor-substrate paired with each browser Container in the regional pool.
• systems/cloudflare-d1 — post-2026-05-13 allocation-state store (replaces KV for the claim hot path).
• systems/cloudflare-kv — pre-2026-05-13 allocation-state store; recently reduced minimum cache TTL was "still too high" for this workload.
• systems/cloudflare-queues — batching layer for per- container 5-second state-update writes (max_batch_size: 100).
• systems/chrome-devtools-protocol — the wire protocol Browser Rendering exposes.
• systems/project-think — agent SDK that exposes Browser Rendering as Tier 3 of the execution ladder.
• systems/dynamic-workers — paired in Project Think; the generated TypeScript driving the browser runs in a Dynamic Worker with Browser Rendering as a granted capability.
• concepts/execution-ladder — Tier 3 capability.
• concepts/customer-zero — the discipline framing the 2026-05-13 Containers migration.
• concepts/do-to-container-cross-region-rtt — the latency asymmetry the regional pool architecture bounds.
• concepts/eventual-consistency-too-slow-for-allocation — the failure mode that drove KV → D1 migration.
• concepts/sqlite-transaction-for-atomic-resource-claim — the SQL primitive at the heart of the post-migration claim.
• patterns/cdp-proxy-for-headless-browser — the CDP-proxy-from- container-to-managed-browser shape Moltworker realises.
• patterns/additive-capability-ladder — the ladder pattern Browser Rendering slots into.
• patterns/regional-pre-warmed-do-container-pair-pool — the placement pattern for the new substrate.
• patterns/transactional-db-over-eventually-consistent-kv-for-claim — the migration pattern.
• patterns/queue-batching-amortizes-db-write-throughput — the throughput-amortisation pattern for state updates.
• patterns/region-fallback-on-queue-backlog — failsafe for primary-queue staleness excursions.
• patterns/single-http-request-over-chatty-websocket — the Quick Action protocol-coalescing optimisation.
• companies/cloudflare — operator.