Cloudflare renamed its Browser Rendering product to Browser Run on April 15, 2026 and shipped a set of capabilities that turn it into a managed browser service built specifically for AI agents, according to the Cloudflare engineering blog. The update includes real-time observability, a formal human handoff protocol, direct Chrome DevTools Protocol access, and a fourfold increase in concurrency limits.
What Shipped
Browser Run now includes six new capabilities, per Cloudflare:
Live View lets developers see what their agent sees in real time. Instead of waiting for a screenshot or log after the fact, builders can watch the agent navigate, click, and interact with web pages as it happens.
Human in the Loop is the most architecturally significant addition. When an agent hits a blocker it cannot resolve on its own, such as a login page requiring credentials or an unexpected edge case, it hands off control to a human operator. The human resolves the issue, then hands control back to the agent, which resumes where it left off. StartupHub.ai confirmed the feature enables “an agent to hand off control to a human operator when encountering unexpected roadblocks, such as login pages or complex edge cases, before resuming automation.”
Chrome DevTools Protocol (CDP) endpoint exposes the underlying browser control protocol directly, giving agents maximum control over browser sessions. Existing CDP automation scripts work on Browser Run with a one-line configuration change, per Cloudflare.
MCP Client Support enables AI coding tools including Claude Desktop, Cursor, and OpenCode to use Browser Run as their remote browser through the Model Context Protocol.
Session Recordings capture every browser session with DOM changes, user interactions, and page navigation for post-execution debugging.
Concurrency limits increased from 30 to 120 simultaneous browsers, a 4x jump for production workloads.
Why the Human-in-the-Loop Protocol Matters
The formal handoff mechanism addresses one of the most common failure modes in agent browser automation: the agent encounters something it cannot handle, fails silently or loops, and the developer only discovers the problem after the fact. Browser Run’s approach creates a defined pause state where the agent explicitly recognizes it needs help, surfaces the issue, and waits for human resolution before continuing.
This is distinct from general-purpose agent supervision tools. The handoff happens within the browser session itself, preserving state, cookies, and context. The human picks up exactly where the agent stopped, and the agent resumes from where the human left off.
Builder Integration
Browser Run runs on Cloudflare’s global network, meaning browser sessions open near users for low latency, according to Cloudflare. The service supports Puppeteer, Playwright, and direct CDP connections. Combined with the Cloudflare Agents SDK announced earlier during Agents Week, Browser Run is positioned as the browser layer for long-running agents that need web access, state persistence, and human oversight in a single managed service.