techlist.io
KREN
cloudflare

Browser Run: give your agents a browser (opens in new tab)

ai-agentcloudflarehuman-in-the-looppuppeteerplaywrightwebmcpbrowser-automationchrome-devtools-protocol

Cloudflare is renaming Browser Rendering to Browser Run and positioning it as a full browser platform for AI agents. It provides remotely hosted Chrome sessions that agents can control, observe, debug, record, and scale globally, while allowing humans to intervene when necessary. The update expands access through CDP and MCP, making existing automation tools and AI coding assistants compatible with Cloudflare’s browser infrastructure.

Browser Run for AI Agents

  • Agents can navigate websites, read content, fill out forms, extract data, take screenshots, and verify results.
  • Browser sessions run on Cloudflare’s global network, reducing infrastructure and browser-maintenance requirements.
  • Sessions can scale dynamically and open near users for lower latency.
  • The platform now supports up to 120 concurrent browsers, up from 30.

Observability and Human Intervention

  • Live View shows an agent’s browser session in real time, making it easier to confirm success or diagnose failures.
  • Human in the Loop allows agents to transfer control when they encounter login screens or unusual edge cases.
  • A human can resolve the issue and return control to the agent.
  • Session Recordings capture DOM changes, interactions, and navigation for debugging and postmortem analysis.

Browser Control Options

Browser Run supports several levels of automation:

  • Low-level control through the Chrome DevTools Protocol (CDP).
  • Higher-level automation with Puppeteer and Playwright.
  • Quick Actions for simpler tasks.
  • WebMCP for websites that expose agent-discoverable actions.

Chrome DevTools Protocol

  • Browser Run now exposes CDP directly through a WebSocket endpoint.
  • Existing CDP-based frameworks, scripts, and agent tools can connect with minimal changes.
  • CDP provides capabilities beyond Puppeteer and Playwright, including JavaScript debugging.
  • Raw protocol messages can be sent directly to models, potentially reducing token usage.
  • Developers can connect from any language or environment without creating a Cloudflare Worker.
  • Self-hosted Chrome scripts can be migrated by changing the browser WebSocket URL and adding Cloudflare authentication headers.

MCP Client Support

  • MCP clients such as Claude Desktop, Cursor, Codex, and OpenCode can use Browser Run as a remote browser.
  • Cloudflare supports the chrome-devtools-mcp package, which provides browser automation, debugging, and performance-analysis capabilities.
  • Configuration requires pointing the MCP server to Browser Run’s CDP endpoint and supplying an API token.

WebMCP

  • WebMCP is intended to make websites more reliable for AI agents.
  • Websites can declare actions that agents can discover and call directly.
  • This addresses the limitations of a web originally designed primarily for human navigation.

Overall Direction

Cloudflare’s update combines hosted browser infrastructure, multiple automation interfaces, real-time visibility, replayable sessions, and human fallback. The goal is to make browser-based agents more dependable in production while avoiding the operational burden of managing Chrome infrastructure themselves.

For teams building web-using agents, Browser Run offers a practical path from self-hosted or local browser automation to scalable, observable remote sessions, especially when existing CDP, Puppeteer, Playwright, or MCP tooling is already in use.