Quick answer
Cloudflare announced Kitesurf on August 6, 2026 as a beta browser for AI agents, available through Browser Run. It runs on Workers and targets stateless, isolated, bursty jobs such as compatible screenshots and HTML extraction. It is not a drop-in guarantee of full Chromium behavior.
Choose Kitesurf only after testing the actual target sites and actions. Use the Kitesurf readiness checker to classify a workload, and review browser-agent authority boundaries before connecting an agent.
Good-fit workloads
Cloudflare positions Kitesurf for agents that can accept non-pixel-perfect rendering, one-shot Quick Actions, and ephemeral tasks. Opt in by adding browser=kitesurf to a supported Quick Action or Browser Run CDP endpoint.
Existing CDP-compatible clients may connect, including Puppeteer, Playwright, chrome-remote-interface, and MCP clients. Compatibility at the protocol level does not prove that every command, page, or workflow behaves like Chromium.
Use Chromium for the documented exclusions
Cloudflare’s current documentation says Kitesurf is not yet the right choice for video, WebGL, bot-challenge handshakes requiring real TLS fingerprints, or long authenticated sessions that need persistent state. Use Browser Run’s default Chromium engine for these cases.
Also test CSS, fonts, SVG, JavaScript APIs, downloads, popups, iframes, authentication, and accessibility on representative pages. A large Web Platform Test count is engineering evidence, not proof for one production site.
Run a bounded acceptance test
Create a corpus of allowed pages and tasks. For each engine, capture navigation success, extracted fields, screenshots, console and network errors, action completion, CPU and wall time, browser usage, and retries. Review visual and structured outputs against explicit acceptance criteria.
Cloudflare’s published benchmark used five Quick Action runs across 14 URLs. Treat those results as provider evidence for that corpus, not as a cost or performance guarantee for your workload. Read the live Browser Run pricing and limits before estimating production cost.
Preserve security and operating boundaries
Kitesurf’s isolation and stateless design do not authorize access to a target or neutralize prompt injection. Keep credentials out of page content, allowlist domains and actions, cap navigation and spend, validate tool arguments, and require approval for messages, purchases, account changes, or data exports.
Log the engine, endpoint, client, target, policy decision, tool calls, outputs, failures, and reviewer. The Cloudflare agent tracing guide covers additional observability design.
Frequently asked questions
What is Cloudflare Kitesurf?
Kitesurf is Cloudflare’s beta, agent-focused browser that runs on Workers and is available through Browser Run. It prioritizes stateless, bursty automation over full Chromium compatibility and pixel-perfect rendering.
When should I use Chromium instead of Kitesurf?
Cloudflare recommends Browser Run’s default Chromium browser for video, WebGL, bot-challenge handshakes needing real TLS fingerprints, and long authenticated sessions that require persistent state.
Does Kitesurf make an agent safe or authorized?
No. The operator still needs target authorization, least-privilege credentials, robots and site-policy checks, prompt-injection defenses, action approvals, logging, and human review for consequential work.
Bottom line
Kitesurf is a promising beta for compatible stateless agent jobs. Adopt it per workload, retain a Chromium fallback, and promote only after representative compatibility, security, reliability, and cost tests pass.
Official sources
- Cloudflare: Introducing Kitesurf
- Cloudflare Kitesurf documentation
- Browser Run pricing
- Browser Run limits
Source check: August 11, 2026. Recheck beta status, compatibility, pricing, limits, and endpoint syntax before deployment.