The browser is the broadest compatibility layer for agents, but Chrome isn't it: why we need Kitesurf

浏览器是 Agent 覆盖面最广的兼容层，但 Chrome 不是：为什么我们需要 Kitesurf？

Cloudflare released Kitesurf, a headless browser infrastructure built for AI agents. It compiles a Rust-based rendering engine to WASM and runs it inside V8 Isolates on Workers, ditching Chromium's multi-process model. In Cloudflare's own benchmarks, HTML extraction used 39.4 MiB per page vs. 273.7 MiB for warm Chromium—about 7× lower memory. Screenshot memory was 57.8 MiB, 4.7× lower. The trade-off: end-to-end screenshot latency hit 1,148 ms vs. Chromium's 637 ms, roughly 1.8× slower, mainly from cold-start software rasterization and JPEG/PNG encoding. Kitesurf explicitly does not support video, WebGL 3D, or bot challenges requiring real TLS fingerprints, and isn't suited for long-lived authenticated sessions. The post also flags an unresolved tension: Cloudflare runs Bot Management to block automated traffic while also shipping agent browser infra, and there's no public answer yet on how Kitesurf traffic gets classified by anti-automation systems.

Why it matters: Cloudflare rebuilt a headless browser specifically for agents, with a sharp angle and hard numbers. Not scoring higher because we only have first-party benchmarks — no third-party stress tests or agent task success rates yet.