AboutAI ToolsCursorClaude CodeLovableBolt.newAI tool reviewsTutorialsVibe codingAI agentsMobile apps with AIAll tutorialsBlogSponsorWork With MeJoin 285K+ Subscribers

15 November 2026 · 3 min read

Cloudflare open-sources Kitesurf browser engine for AI agents

Cloudflare has released Kitesurf under Apache 2.0, letting developers inspect, run locally, and deploy their own instance of the experimental AI-agent browser engine on Cloudflare Workers.

Cloudflare announced on 13 November 2026 that Kitesurf, its experimental browser engine for AI agents, is now open source under the Apache 2.0 licence [1][2]. The code is available on GitHub, and developers can inspect it, run it locally, modify it, and deploy their own instance to Cloudflare Workers [2]. The open-source entry was recorded in the Browser Run changelog on 12 November, while the managed Kitesurf offering remains labelled beta [1].

What was released

The public repository includes the engine, core libraries, DOM shims, a renderer, and a command-line client [1][2]. Kitesurf runs entirely on Cloudflare Workers and processes HTML, CSS, and page JavaScript, producing screenshots without a browser container [1][2]. It exposes a Chrome DevTools Protocol (CDP) endpoint, so automation clients such as Puppeteer can connect directly [1][2].

Internally, the engine is built from Rust projects compiled to WebAssembly. Blitz provides HTML parsing, the DOM, layout, and painting; Stylo handles CSS parsing and computed styles; Linebender libraries cover text layout and 2D graphics; Krilla generates PDF output; and Boa acts as a fallback JavaScript runtime inside WebAssembly when page code cannot run in Dynamic Workers [2][3]. These dependencies retain their own licences, and the repository’s NOTICE file documents third-party notices [1][2].

Kitesurf is organised into three main parts: the Engine manages browser sessions and client connections, PageScript runs the page and its JavaScript, and PageRenderer draws the visual result [2][3].

Running your own instance

Local development requires Bazelisk, Node.js 22 or newer, and pnpm 9.15.4 [3]. After cloning the repository and installing dependencies, pnpm run dev starts a local engine at http://127.0.0.1:8787 [2]. The initial build compiles the Rust core and vendored dependencies; subsequent builds reuse the cache [2][3]. Developers can then inspect pages through Chrome DevTools or attach Puppeteer and other CDP clients [2].

Deploying to a Cloudflare account requires a Workers Paid plan because Kitesurf uses Dynamic Workers to create isolated workers for pages and renderers [2][3]. The deployment command is pnpm run deploy from the repository root [2].

Self-hosting transfers an important security responsibility. The engine ships without built-in authentication, and its workers.dev address is public by default [1][3]. Without an authentication layer such as Cloudflare Access, anyone with the URL could browse through the engine, connect CDP clients, issue outbound requests from the operator’s Cloudflare account, and consume paid CPU time and Dynamic Workers [1][3]. The repository instructs operators to protect the URL immediately and explains how to enable Access before deployment [3].

Note that the managed Browser Run Quick Actions binding does not run Kitesurf locally under Wrangler; that binding requires remote mode during development [1].

Limitations and experimental status

Kitesurf remains experimental and under heavy development. The repository describes it as a CDP endpoint rather than a complete Chrome implementation, and some Chrome DevTools features are still unsupported [3]. Cloudflare is prioritising compatibility, reliability, and efficiency [2][3].

At the August launch, the company stated that Kitesurf was not yet suitable for video, WebGL, bot-challenge handshakes that require real TLS fingerprints, or long authenticated sessions that depend on persistent state [1][3]. Passing Web Platform Tests does not guarantee compatibility with every website, and CDP support alone cannot confirm that a specific institutional portal or data-extraction task will work as expected [1].

What it means for developers

For developers building AI agents, the open-source release provides direct access to the browser stack. They can inspect and modify the engine, integrate it with Puppeteer or AI harnesses via CDP, and run it on their own infrastructure [1][2][3]. The trade-off is that self-hosted deployments must be secured by the operator, and the engine’s Chrome and web-platform compatibility is still incomplete [3].

Cloudflare welcomes contributions. Prospective contributors should open an issue with a minimal reproduction or proposed approach and obtain maintainer vouching before submitting a pull request. Focused fixes with tests and a defined scope are preferred, but reproducible rendering bugs, failing automation workflows, and documentation corrections are also welcome [2][3].

Sources

  1. Cloudflare open-sources Kitesurf agent browser — CASRAI
  2. Kitesurf is now open source
  3. Cloudflare Open-Sources Kitesurf Browser Engine for AI Agents
  4. Cloudflare Open Sources Kitesurf: Their Web Browser For AI Agents - Phoronix
  • cloudflare
  • kitesurf
  • ai agents
  • open source
  • browser engine
  • webassembly

Researched and drafted with AI from the sources above.

Learn to build with AI

Hands-on tutorials on Cursor, Claude Code, AI agents and more.