Discuss your project
Web architecture

Test Kitesurf on the pages your agent needs to read

Your agent reads an order status from a dynamic page. Compare Kitesurf with your current browser on rendering, task isolation, and the network access the service actually needs.

Tester Kitesurf sur les pages qu’un agent doit vraiment lire

Your agent reads an order status from a dynamic page. The page opens, but the order number remains blank. Before adopting a lighter engine, verify the pages and actions your application actually uses.

The code opened on November 13

Cloudflare published Kitesurf under Apache 2.0. The agent browser runs on Cloudflare Workers, executes page JavaScript, and renders screenshots. It supports CDP, the control protocol used by tools such as Puppeteer. Cloudflare documents local development and deployment on a paid Workers account for the required service features. CDP helps with comparison. Page compatibility depends on the engine you use.

Compare rendering and task isolation

  1. Prepare a static page and a page that loads a fictional order status through JavaScript. Use identical test IDs and assertions with your existing browser and Kitesurf.
  2. Record status, time until the field appears, errors, and screenshots. Repeat with a slow page and a new task. Check that the previous task’s ID does not reappear.
  3. Restrict allowed hosts in your application. Verify expected denial on an unauthorized test host. Keep credentials synthetic and review traces before adding a service account.

An earlier Partitech article covered instructions injected into browser content. This one focuses on engine choice and compatibility and isolation tests for your own tasks.

Share this article