Cloudflare's Kitesurf drops Chromium for agent browsing
The agent-first browser runs in V8 isolates on Workers with no Chromium underneath, claiming 3–7x lower CPU and memory on common agent tasks at 1.7–1.8x the wall-clock time.
Cloudflare introduced Kitesurf on Thursday, a web browser built for AI agents that runs entirely inside V8 isolates on Cloudflare Workers with no Chromium engine beneath it. It is free during beta through Browser Run, with per-account limits.
The architecture
Kitesurf discards the parts of a browser that exist for humans — tabs, extensions, pixel-perfect 60fps compositing — and keeps what an agent consumes: machine-readable page content, low token overhead, cheap parallelism and isolation. The system splits into an Engine that manages sessions over the Chrome DevTools Protocol and HTTP REST; PageScript, which handles DOM and layout using the Rust rendering engine Blitz and Firefox's Stylo CSS parser; a PageRenderer that emits JPEG, PNG or PDF; and SandboxOutbound, which enforces network policy, CORS and cookie handling.
Cloudflare reports 3.1–3.8x less CPU and 4.7–7.0x less memory than Chromium on typical agent workloads such as screenshots and HTML extraction, at roughly 1.7–1.8x slower wall-clock time. The company says the engine passes more than 215,000 Web Platform Tests. Existing Puppeteer, Playwright and MCP clients can switch by adding a single browser=kitesurf parameter, and Cloudflare says it plans to open-source Kitesurf for self-hosting.
Why it matters
Browser use has become a default agent capability, and the standard implementation — one headless Chromium per session — was never designed for it. Chromium's cost is dominated by rendering fidelity an agent never looks at, which makes per-agent browsing expensive enough to cap how many concurrent sessions a product can afford. Kitesurf's trade is explicit and unusual: accept nearly double the latency to cut resource consumption several-fold, which is the right direction when agents run unattended and cost, not responsiveness, is the binding constraint.
The strategic reading is that Cloudflare is positioning the browser as infrastructure it sells rather than a component each agent vendor rebuilds — the same move it made with Workers for compute. If the promised open-sourcing arrives, the more consequential outcome may be that a credible non-Chromium engine enters production use at scale for the first time in years.