Kitesurf: Cloudflare's Chromium-free browser built for AI agents

Cloudflare has unveiled Kitesurf, a headless web browser built specifically to be operated by AI agents. The tool is available in beta, with an online playground for testing it directly. Internally, the question of whether to build an in-house browser had resurfaced every couple of years without ever moving forward. It finally did this time because two conditions lined up at once: WebAssembly execution on Workers had matured enough, and the surge of AI agents turned the need for a "non-human browser" into a concrete problem.

What agents want isn't what humans want

Cloudflare's starting point was to rethink the requirements from scratch. A browser built for humans needs tabs, bookmarks, extensions, password management, and cross-device sync. Fast theme rendering and smooth scrolling also matter to perceived interface quality. An AI agent needs none of that. What matters to an agent is token count, context window, the ability to scale, performance, and cost. Machine-readable structured content matters, but a slightly off CSS rendering or a pixel that lands in the wrong place causes almost no harm.

Conversely, an agent operates far faster than a human and runs many browsers in parallel. An agent browser therefore needs to be light enough to run at high density and high speed on its execution infrastructure, and it needs security protections different from those built for humans — defenses against prompt injection, for instance. Engines like Chromium were built for humans and carry overhead that models never use. Their memory and compute footprint is too large to give every agent its own instance without the bill exploding. The result: large parts of the web stayed accessible only to the most expensive, highest-performing models.

Rust, WebAssembly, and Workers underneath

Kitesurf is written mainly in Rust, compiled to WebAssembly, and runs on Cloudflare Workers. No Chromium, no Node.js dependency. According to the company, it uses 3 to 7 times less CPU and memory than Chromium, and it is designed to spin up per request. Access is free during the beta.

This architecture rests on several years of work on the developer platform side: dynamic Workers, SQLite-based Durable Objects, Worker-to-Worker RPC, service bindings, improved Node.js compatibility, and higher limits across the board — all building blocks that make applications of a previously unreachable scale possible on Workers. Another factor: Cloudflare's headless browser automation API was already growing fast on the back of AI adoption. Agents need a browser for many tasks, and some tasks simply cannot be done without one.

Existing tools plug in without changes

The most practical choice Cloudflare made was not introducing a proprietary protocol. Kitesurf can be reached over the Chrome DevTools Protocol (CDP) via WebSocket, or through an HTTP RESTful API. Because it speaks CDP, existing tools such as Puppeteer, Playwright, Chrome's remote interface, and the Chrome DevTools frontend itself connect to it directly and work without adaptation. This design, which keeps migration cost to a minimum, weighs heavily on the decision to adopt it.

• Implementation: mainly Rust, compiled to WebAssembly, running on Cloudflare Workers
• Efficiency: Cloudflare says 3 to 7 times less CPU and memory than Chromium
• Connectivity: CDP over WebSocket and a RESTful API; Puppeteer and Playwright work unmodified
• Validation: Web Platform Tests conformance, plus multi-step tests on real sites compared against Chromium

On validation, Cloudflare details its method: beyond Web Platform Tests conformance, the company runs Puppeteer-driven multi-step tests on real websites against both Kitesurf and reference Chromium, comparing results as development proceeds. And, unsurprisingly, it also passes the traditional "does it run Doom" test.

Lightness becomes a precondition of the agent era

Kitesurf is not simply the arrival of one more lightweight browser. Once agents are assumed to operate business systems, the browser stops being "the window a human looks through" and becomes "a component a machine executes." For a component, unit cost, startup time, and concurrency sit at the center of the design. The beta performance figures are self-reported by the company, and real-world compatibility will need to be verified in each organization's own workflow — but the direction is hard to ignore. For anyone planning to run dozens or hundreds of agents in parallel, a heavy browser eventually shows up on the bill.