Introducing Kitesurf: The agent-first browser that runs in V8 isolates on Cloudflare Workers

Cloudflare spent years debating whether to build a browser, and kept talking itself out of it. The technical lift was huge, and nobody could point to a problem only a new browser could solve. That changed once Workers matured enough — dynamic workers, SQLite-backed Durable Objects, worker-to-worker RPC — and once AI agents started hammering Cloudflare's headless browser API, Browser Run, hard enough to expose a real gap.

The gap is simple: Chromium was built for humans. It manages tabs, extensions, sync, and pixel-perfect 60fps rendering, none of which an AI agent cares about. Agents care about token counts, context windows, and cost. Giving every agent a full Chromium instance is expensive and memory-hungry, which effectively rations agentic browsing to whoever can afford the compute. So twelve weeks ago Cloudflare's team decided to build something leaner: Kitesurf, a browser engine that runs entirely inside V8 isolates on Workers, free during beta through Browser Run.

The origin story is almost casual. Someone stumbled on obscura, a dependency-free Rust engine for headless automation, and the team used an AI coding agent to try porting it to Workers. It barely worked at first. Once they gave the agent a strict spec and clear pass/fail criteria drawn from the Web Platform Tests suite, though, it actually ran — and that rough prototype convinced Cloudflare to commit real engineering time. The build leans on Rust compiled directly to WebAssembly rather than Emscripten's heavier emulation layers, uses Blitz and Stylo (Firefox's CSS engine) for parsing, and even runs a JavaScript-in-JavaScript engine called Boa to handle eval() until native eval support lands in Workers.

Architecturally, Kitesurf splits into three isolated pieces — an Engine that speaks the Chrome DevTools Protocol so Puppeteer and Playwright work unmodified, a PageScript worker that parses HTML/CSS and runs page JavaScript inside a fresh isolate per session, and a PageRenderer that rasterizes the final scene into JPEG, PNG, or PDF. Every network fetch runs through a single sandboxed worker, isolation is enforced at the application level on top of Cloudflare's isolate boundaries, and components are kept stateless so a stuck render can just be killed and retried.

The numbers back up the pitch. Kitesurf currently passes over 215,000 Web Platform Tests and is gaining hundreds weekly. Against Chromium on common agent tasks, it uses roughly 3 to 4 times less CPU and up to 7 times less memory, though it's still about 1.7 times slower in wall-clock time because Chromium's warmed-up JIT beats a cold Rust renderer on raw speed. Cloudflare says most of that lag comes from rasterization and image encoding, which is exactly where it's focusing optimization next.