Cloudflare Launches Kitesurf Browser Built for AI Agents
Cloudflare has launched Kitesurf, a lightweight browser running on V8 isolates that reduces memory and CPU usage for AI agents navigating the web.

Cloudflare has launched Kitesurf, an "agent-first" browser designed specifically to run on Cloudflare Workers using V8 isolates. Available for free in beta through Cloudflare's Browser Run API, the browser is built to handle automated web tasks for AI models rather than human users. Developed in just 12 weeks since its first commit in May, Kitesurf strips away human-centric features like tabs, themes, and smooth scrolling to focus entirely on scalability, token count, and cost efficiency.
Under the hood, Kitesurf relies heavily on WebAssembly and native Rust. It utilizes components of the Blitz modular rendering engine and Firefox's Stylo CSS parser. To execute JavaScript and WebAssembly within isolated environments, it uses a PageScript worker, employing the Boa JS ECMAScript engine to handle eval statements. Rendering is managed by the PageRenderer worker using blitz-paint and Parley for text shaping, returning stateless, disposable image buffers to the main engine via Cloudflare's built-in remote procedure call system.
In terms of performance, Kitesurf presents a distinct trade-off compared to traditional engines. While Chromium outperforms Kitesurf by 1.7x in raw speed due to its just-in-time compiler, Kitesurf reduces memory and CPU consumption by 3x to 7x. The browser already passes more than 215,000 Web Platform Tests and can successfully render complex sites like Wikipedia, TodoMVC, and even the classic game Doom. It supports the Chrome DevTools Protocol, making it compatible with existing automation tools like Puppeteer, Playwright, and Model Context Protocol clients.
For developers and AI practitioners, Kitesurf offers a highly scalable, stateless solution for bursty workloads like HTML extraction and screenshot generation. However, Cloudflare notes that Kitesurf is not yet suitable for tasks requiring WebGL, video playback, persistent ten-minute sessions, or bypassing bot-detection handshakes. Developers can test the browser in a public playground or integrate it into their workflows by appending a browser parameter to their Browser Run endpoints, with plans for an open-source release in the near future.
This is our own summary of reporting by Hacker News



