Cloudflare

Cloudflare has open-sourced Kitesurf, its stateless browser for AI agents, on GitHub under the Apache 2.0 license, so developers can read the code, run it locally, modify it, and deploy their own instance to their own Cloudflare Workers account. Kitesurf runs entirely on Workers, parsing HTML, applying CSS, executing page JavaScript and rendering screenshots without a browser container, and it supports the Chrome DevTools Protocol so clients such as Puppeteer can connect. Cloudflare says the goal is a lightweight browser for agents that uses less CPU and memory than a full browser like Chromium and scales on demand, while noting the project is under heavy development.

Cloudflare has open-sourced Kitesurf, its stateless browser for AI agents, on GitHub under the Apache 2.0 license, so developers can read the code, run it locally, modify it, and deploy their own instance to their own Cloudflare Workers account. Kitesurf runs entirely on Workers, parsing HTML, applying CSS, executing page JavaScript and rendering screenshots without a browser container, and it supports the Chrome DevTools Protocol so clients such as Puppeteer can connect. Cloudflare says the goal is a lightweight browser for agents that uses less CPU and memory than a full browser like Chromium and scales on demand, while noting the project is under heavy development.

Cloudflare released traffic analytics and finer-grained access policies for personal agents. Previously, sites saw these requests made on a person's behalf only as automated traffic, with little way to tell which agents were visiting or which pages they reached. Security Analytics now lists Personal Assistants as its own category and can filter by a single agent's paths, status codes and source networks; sites can also set Allow, Block on pages with ads, or Block for each supported personal agent.

Cloudflare released traffic analytics and finer-grained access policies for personal agents. Previously, sites saw these requests made on a person's behalf only as automated traffic, with little way to tell which agents were visiting or which pages they reached. Security Analytics now lists Personal Assistants as its own category and can filter by a single agent's paths, status codes and source networks; sites can also set Allow, Block on pages with ads, or Block for each supported personal agent.

Cloudflare has added Zero Wire, a public vulnerability intelligence feed in Cloudflare Radar's security section, that condenses critical CVEs in Internet-facing software into briefings for security leaders and engineers deciding whether they are affected. Each briefing carries a plain-language explanation, which deployments to investigate, recommended actions, and links to evidence and vendor guidance, plus a pre-compiled prompt for a read-only exposure assessment by an AI agent. Cloudflare positions it as a complement to vendor advisories and vulnerability databases, not a catalog of every CVE.

Cloudflare has added Zero Wire, a public vulnerability intelligence feed in Cloudflare Radar's security section, that condenses critical CVEs in Internet-facing software into briefings for security leaders and engineers deciding whether they are affected. Each briefing carries a plain-language explanation, which deployments to investigate, recommended actions, and links to evidence and vendor guidance, plus a pre-compiled prompt for a read-only exposure assessment by an AI agent. Cloudflare positions it as a complement to vendor advisories and vulnerability databases, not a catalog of every CVE.

Cloudflare's Agents SDK now treats Agent Skills as files in the agent's workspace: write a folder containing SKILL.md under /workspace/.agents/skills/ and the agent can use it on its next turn, with no build step or deploy, and the agent can write its own skills. Skills load from a workspace, an R2 bucket, or code, and Think lists every source again before each turn; each SKILL.md is checked against the Agent Skills specification, and a skill that breaks a rule still loads with a logged warning. This is a breaking change: direct agents/skills use, the Vite import, SkillRegistry, and Think's skillWorkspace are removed.

Cloudflare's Agents SDK now treats Agent Skills as files in the agent's workspace: write a folder containing SKILL.md under /workspace/.agents/skills/ and the agent can use it on its next turn, with no build step or deploy, and the agent can write its own skills. Skills load from a workspace, an R2 bucket, or code, and Think lists every source again before each turn; each SKILL.md is checked against the Agent Skills specification, and a skill that breaks a rule still loads with a logged warning. This is a breaking change: direct agents/skills use, the Vite import, SkillRegistry, and Think's skillWorkspace are removed.

Cloudflare has previewed Clairic on Workers AI, extending so-called System One models from decisions to extraction: given text and a map of typed fields, it returns extracted, computed, estimated or forecast values in a single parallel forward pass, each with confidence and an 80% interval. Structured-output calls previously went to frontier LLMs that generate tokens, requiring parsing, validation and retries. In one support-claim pipeline, Clairic plus the decision model Clef plus an LLM finished in 19.3 seconds, against 61.7 seconds when GLM-5.3 did every step.

Cloudflare has previewed Clairic on Workers AI, extending so-called System One models from decisions to extraction: given text and a map of typed fields, it returns extracted, computed, estimated or forecast values in a single parallel forward pass, each with confidence and an 80% interval. Structured-output calls previously went to frontier LLMs that generate tokens, requiring parsing, validation and retries. In one support-claim pipeline, Clairic plus the decision model Clef plus an LLM finished in 19.3 seconds, against 61.7 seconds when GLM-5.3 did every step.

Cloudflare added internal hostnames to the persistent browser in its Agents SDK: give the browser a name such as preview.internal and requests to it go to the agent itself rather than the internet. The agent can then check a dev server in its sandbox, a folder in its workspace, or another Worker in the same browser it uses for the web, with nothing exposed publicly. Each internal host has a fetch function running in the Durable Object, so it can use that object's bindings and state, and a host can carry a target schema so the model chooses which port or folder it serves.

Cloudflare added internal hostnames to the persistent browser in its Agents SDK: give the browser a name such as preview.internal and requests to it go to the agent itself rather than the internet. The agent can then check a dev server in its sandbox, a folder in its workspace, or another Worker in the same browser it uses for the web, with nothing exposed publicly. Each internal host has a fetch function running in the Durable Object, so it can use that object's bindings and state, and a host can carry a target schema so the model chooses which port or folder it serves.