Cloudflare has launched Kitesurf, a browser runtime built from scratch for AI agents instead of humans. Unlike nearly every browser automation tool of the past decade, it doesn’t run on Chromium at all: it’s a Rust-based engine that runs entirely inside V8 isolates on Cloudflare Workers, and Cloudflare says it uses 3 to 7 times less CPU and memory than Chromium for common agent tasks like taking screenshots or pulling structured data out of a page.
It’s currently in beta, free to use, and available now through Cloudflare’s Browser Run product.
Why Chromium is the wrong tool for AI agents
Most “AI browses the web” products today are really just an AI model driving a real Chrome instance through Puppeteer or Playwright, screenshot by screenshot. That works, but Chromium was built to paint pixels for a human, not to hand structured information to a model. Every agent task ends up paying for a full rendering pipeline it never actually needs, which gets expensive and slow fast when you’re spinning up hundreds or thousands of browser sessions for bursty, automated workloads.
Kitesurf skips that pipeline entirely. There’s no rendering layer optimized for what a screen looks like, just a machine-readable DOM flowing in and structured data flowing back out to the agent. Cloudflare says the engine still passes more than 235,000 web platform tests, so it’s not a stripped-down toy version of a browser, it’s a real one that simply never bothers rendering anything for a human to look at.
Built for how agents actually get abused, too
Running agents loose on the open web comes with its own failure modes that a normal browser was never designed to guard against, like a malicious page trying to hijack an agent through prompt injection, or a task quietly blowing through its context window and token budget. Kitesurf is designed with those agent-specific problems in mind from the ground up, rather than bolting protections onto a browser that was built for something else.
Drop-in for existing tools
Cloudflare isn’t asking developers to rip out their existing stack to try it. Kitesurf plugs into the same Browser Run CDP and Quick Action endpoints developers already use, and works with Puppeteer, Playwright, and MCP clients out of the box, so switching over is mostly a matter of adding a `browser=kitesurf` parameter to requests that already exist. There’s also a no-code playground at kitesurf.cloudflare.app for anyone who wants to try it before touching any code.
Why this matters
This is a bet from Cloudflare that the next wave of internet infrastructure isn’t built around browsers that render pages for people, it’s built around runtimes that feed the web to agents. If that’s right, whoever owns the layer agents use to actually browse the internet ends up owning a pretty significant chokepoint in how AI systems get things done online, and Cloudflare wants that layer to run on its own network.
Bottom line
For developers already running agent workloads through Puppeteer, Playwright, or MCP, Kitesurf is a low-effort way to cut compute costs significantly, and it’s free to test during the beta. For everyone else, it’s an early signal that browser infrastructure is starting to split into two separate tracks: one for humans, and one for the AI agents increasingly browsing on our behalf.