Cloudflare's Kitesurf: A Browser Built for AI Agents, Not Humans

Cloudflare has finally answered a question it has been asking itself for years: should we build our own browser? The answer, this time, is a resounding yes. The result is Kitesurf, a browser designed specifically for AI agents, running entirely on Cloudflare Workers. It's now available for free in beta through Browser Run.

The core insight behind Kitesurf is that traditional browsers like Chromium are built for humans, not machines. They carry overhead—tabs, themes, extensions, pixel-perfect rendering—that AI models simply don't need. What agents care about is token count, context windows, scalability, and cost. Kitesurf strips away the human-centric features and focuses on what matters for AI: efficient HTML extraction, structured content, and low resource consumption.

The technical foundation is a series of advancements in Cloudflare's developer platform: mature WebAssembly support, dynamic workers, SQLite-based Durable Objects, and worker-to-worker RPC. These primitives made it possible to build a browser that runs entirely on the edge, with no traditional browser engine involved.

Design decisions

Building a browser is a monumental task, so the team leaned heavily on AI-assisted development. They used the Web Platform Tests (WPT) suite as a benchmark for feature conformance, letting AI agents iterate against clear goalposts. To ensure real-world compatibility, they also implemented integration and visual regression tests that run Puppeteer scripts against both Chromium and Kitesurf, comparing outputs at every step.

The team chose Rust for performance-critical components, compiling to WebAssembly via wasm-bindgen to avoid emulation layers. Exception handling is designed so that any failure degrades to a blank frame or missing element, never a dead session. Isolation is paramount: every page load is treated as untrusted input, and each component has access only to the resources it strictly needs.

Statelessness is a guiding principle. Wherever possible, components are stateless, making them disposable and parallel by nature. This fits automation perfectly, where load arrives in bursts and the cheapest thing is to spin up work that costs only what it uses and vanishes when done.

Architecture

Kitesurf's architecture is built around three main components: the Engine, PageScript, and PageRenderer. The Engine is the only public-facing component, handling CDP WebSocket and HTTP REST APIs, and storing session state. All other components are stateless.

Network access is funneled through a single component, the SandboxOutbound worker, which enforces CORS, injects browser-shaped headers, filters responses, and keeps each page's cookies in their own jar. Nothing else can touch the network directly, enforced by Dynamic Workers.

The result is a browser that is significantly more efficient in CPU and memory consumption than Chromium for common agentic tasks like screenshots and HTML extraction. It's a bold bet that the future of browsing is not for humans, but for the agents that will increasingly act on our behalf.