Kitesurf: Agent-first browser that runs in V8 isolates

That shifted attention from the agent marketing to the browser stack itself. Several people zeroed in on how unusual the architecture is. Blitz is decoupled at nearly every layer, including parsing, networking, rendering, windowing, and the JavaScript engine, which makes this kind of custom deployment inside Workers more plausible than trying to carve pieces out of WebKit or Chromium. Others noted that Web Platform Tests were a big reason Cloudflare could get to useful compatibility quickly. On control protocols, people broadly want WebDriver BiDi to win, but the practical reality today is that CDP still covers more of the browser inspection and automation use cases serious tooling needs. The other strong theme was trust and incentives. Multiple commenters asked the obvious question: if Cloudflare sells both anti-bot protection and agent browsers, does its own browser traffic get special treatment? Cloudflare’s replies were explicit that Browser Run traffic is marked as bot traffic, uses documented headers, and does not try to hide. That calmed the narrow technical question, but not the broader unease. The sharper read is that Kitesurf is less about pretending agents are human and more about formalizing bot traffic into something Cloudflare can host, identify, and eventually monetize. On actual use cases, the thread cut through the hype. People are not mostly delegating life decisions to shopping agents. They are using browser agents for tedious admin panels, filling carts on sites with bad APIs, finding information buried in hostile UIs, and generating quick page-specific automations. In other words, this looks much closer to cloud-native RPA than a mainstream autonomous consumer agent breakthrough.