Cloudflare Built a Browser That Only Agents Will Ever Use
Day three of Cloudflare's Agents Week (August 6) was the densest yet. The headliner is Kitesurf, a web browser built from scratch for AI agents, running entirely in V8 isolates on Cloudflare Workers (blog.cloudflare.com/kitesurf). No Chromium anywhere in the stack: HTML parsing by Blitz, CSS by Firefox's Rust-based Stylo, JavaScript eval by the Boa engine, rasterization by blitz-paint. The pitch is that a browser for humans wastes everything agents pay for — tabs, themes, extensions — when what an agent cares about is token count, memory, and cost per page.
The numbers back it up: 57.8 MiB for a screenshot versus Chromium's 271 MiB, 3 to 4 times less CPU, over 215,000 web platform tests passing. It speaks Chrome DevTools Protocol, so existing Puppeteer and Playwright code works by adding a browser=kitesurf parameter. Free in beta through Browser Run. Browser automation at scale has always meant herding Chromium containers, the most resource-hungry way imaginable to fetch a page. If agents become the dominant consumers of the web — Cloudflare has better data on that than anyone — rebuilding the browser around them is the obvious move everyone else was too invested in Chromium to make.
Same day, two protocol plays. WebMCP (developer preview) gives any website an MCP interface without touching its backend: the site declares tools, browser agents call them, no API required. And Cloudflare shipped its implementation of the next-generation stateless MCP — the 2026-07-28 spec rewrite we covered in July — optimized for Workers, plus an AI Search product that indexes your own files and sites for agent consumption.
Step back and look at the week: an open-source workspace (Cloudflare OS), a computer (cloudflare/computer), a wallet, and now a browser, a search engine, and the protocol glue. Cloudflare is speedrunning the entire agent stack in public, and selling the same thing underneath all of it: Workers. The bet is that the agentic Internet needs an infrastructure company the way the human Internet needed a CDN, and they intend to be both.
← Back to all articles
The numbers back it up: 57.8 MiB for a screenshot versus Chromium's 271 MiB, 3 to 4 times less CPU, over 215,000 web platform tests passing. It speaks Chrome DevTools Protocol, so existing Puppeteer and Playwright code works by adding a browser=kitesurf parameter. Free in beta through Browser Run. Browser automation at scale has always meant herding Chromium containers, the most resource-hungry way imaginable to fetch a page. If agents become the dominant consumers of the web — Cloudflare has better data on that than anyone — rebuilding the browser around them is the obvious move everyone else was too invested in Chromium to make.
Same day, two protocol plays. WebMCP (developer preview) gives any website an MCP interface without touching its backend: the site declares tools, browser agents call them, no API required. And Cloudflare shipped its implementation of the next-generation stateless MCP — the 2026-07-28 spec rewrite we covered in July — optimized for Workers, plus an AI Search product that indexes your own files and sites for agent consumption.
Step back and look at the week: an open-source workspace (Cloudflare OS), a computer (cloudflare/computer), a wallet, and now a browser, a search engine, and the protocol glue. Cloudflare is speedrunning the entire agent stack in public, and selling the same thing underneath all of it: Workers. The bet is that the agentic Internet needs an infrastructure company the way the human Internet needed a CDN, and they intend to be both.
Comments