---
title: Changelogs
image: https://edgetunnel-b2h.pages.dev/cf-twitter-card.png
---

> Documentation Index  
> Fetch the complete documentation index at: https://edgetunnel-b2h.pages.dev/changelog/llms.txt  
> Use this file to discover all available pages before exploring further. 

[Skip to content](#%5Ftop) 

# Changelog

New updates and improvements at Cloudflare.

[ Subscribe to RSS ](https://edgetunnel-b2h.pages.dev/changelog/rss/index.xml) [ View RSS feeds ](https://edgetunnel-b2h.pages.dev/fundamentals/new-features/available-rss-feeds/) 

All products

![hero image](https://edgetunnel-b2h.pages.dev/_astro/hero.CVYJHPAd_26AMqX.svg) 

Jun 22, 2026
1. ### [R2 SQL now supports window functions, DISTINCT, and set operations](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-21-window-functions-distinct-set-operations/)  
[ R2 SQL ](https://edgetunnel-b2h.pages.dev/r2-sql/)  
R2 SQL now supports window functions, `SELECT DISTINCT`, set operations, and additional aggregates, making it easier to write analytical queries without preprocessing your data elsewhere.  
[R2 SQL](https://edgetunnel-b2h.pages.dev/r2-sql/) is Cloudflare's serverless, distributed SQL engine for querying [Apache Iceberg ↗](https://iceberg.apache.org/) tables stored in [R2 Data Catalog](https://edgetunnel-b2h.pages.dev/r2/data-catalog/).  
#### New capabilities

  * **Window functions** — `ROW_NUMBER`, `RANK`, `DENSE_RANK`, `PERCENT_RANK`, `CUME_DIST`, `NTILE`, `LAG`, `LEAD`, `FIRST_VALUE`, `LAST_VALUE`, `NTH_VALUE`, and aggregates with an `OVER (...)` clause, including `PARTITION BY` and explicit frames
  * **QUALIFY** — filter rows based on a window function result
  * **DISTINCT** — `SELECT DISTINCT`, `DISTINCT ON (...)`, and the `DISTINCT` modifier on aggregates such as `COUNT(DISTINCT ...)`
  * **Set operations** — `UNION`, `UNION ALL`, `INTERSECT`, and `EXCEPT`
  * **Grouping extensions** — `GROUPING SETS`, `ROLLUP`, and `CUBE`
  * **Exact aggregates** — `MEDIAN`, `PERCENTILE_CONT`, `ARRAY_AGG`, and `STRING_AGG`  
#### Examples  
#### Rank rows with a window function  
```sql  
SELECT customer_id, region,  
       ROW_NUMBER() OVER (PARTITION BY region ORDER BY total_amount DESC) AS rank_in_region  
FROM my_namespace.sales_data  
```  
#### Filter with QUALIFY  
```sql  
SELECT customer_id, region, total_amount  
FROM my_namespace.sales_data  
QUALIFY ROW_NUMBER() OVER (PARTITION BY region ORDER BY total_amount DESC) <= 3  
```  
#### Combine tables with a set operation  
```sql  
SELECT customer_id FROM my_namespace.sales_data  
EXCEPT  
SELECT customer_id FROM my_namespace.archived_sales  
```  
The named `WINDOW` clause is not supported — inline the `OVER (...)` specification at each call site. For the full syntax reference, refer to the [SQL reference](https://edgetunnel-b2h.pages.dev/r2-sql/sql-reference/). For supported features and performance guidance, refer to [Limitations and best practices](https://edgetunnel-b2h.pages.dev/r2-sql/reference/limitations-best-practices/).

Jun 19, 2026
1. ### [Manage all your routes from one page in the dashboard](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-19-unified-routes-page/)  
[ Cloudflare Mesh ](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-mesh/)[ Cloudflare Tunnel ](https://edgetunnel-b2h.pages.dev/tunnel/)[ Cloudflare WAN ](https://edgetunnel-b2h.pages.dev/cloudflare-wan/)[ Cloudflare One ](https://edgetunnel-b2h.pages.dev/cloudflare-one/)  
The **Routes** page in the Cloudflare dashboard now shows the routes across all of your connectors — [Cloudflare Mesh](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-mesh/) and [Cloudflare Tunnel](https://edgetunnel-b2h.pages.dev/tunnel/) routes alongside [Cloudflare WAN](https://edgetunnel-b2h.pages.dev/cloudflare-wan/) and [Magic Transit](https://edgetunnel-b2h.pages.dev/magic-transit/) static routes — in a single table, instead of a separate routes view per product.  
![The unified Routes page in the Cloudflare dashboard, showing routes across connectors in a single table](https://edgetunnel-b2h.pages.dev/_astro/2026-06-19-unified-routes.B3igBY20_Z1awHp.webp)  
From the unified Routes page you can:

  * **Visualize your network with an interactive map** that shows how your destinations flow through to your connectors — including equal-cost multi-path (ECMP) routes where the same prefix is served by several connectors. Select a node to filter the table down to the routes behind it.
  * **See every route in one table**, with its destination, type, connector, priority, and source, and filter or sort to find what you need.
  * **Create, edit, and delete routes** of any supported type without leaving the page. When adding a Cloudflare WAN or Magic Transit static route, you now pick the next hop by **connector name** instead of typing its IP.
  * **Manage [virtual networks](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/virtual-networks/)** from a dedicated tab.
  * **Test a route** to see which connector and next hop a destination resolves to before you commit a change.  
To find it, go to **Networking** \> **Routes** in the dashboard sidebar.  
[ Go to **Routes** ](https://dash.cloudflare.com/?to=/:account/magic-networks/routes)  
Your existing routes, APIs, and configurations are unchanged — this is a dashboard experience that brings them together in one place. Learn how to [add routes](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/routes/add-routes/) and [manage virtual networks](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/virtual-networks/).

Jun 19, 2026
1. ### [New Asia-Pacific location hints: apac-ne and apac-se](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-19-apac-ne-apac-se-location-hints/)  
[ Durable Objects ](https://edgetunnel-b2h.pages.dev/durable-objects/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
Durable Objects now supports two new location hints for Asia-Pacific: `apac-ne` (Northeast Asia-Pacific) and `apac-se` (Southeast Asia-Pacific). Use `apac-ne` or `apac-se` when you want finer-grained placement within Asia-Pacific rather than the broader `apac` hint.  
Use the new hints the same way as any other `locationHint`:

**JavaScript**  
```js  
// Northeast Asia-Pacific (Japan, Korea, etc.)  
const stubNE = env.MY_DURABLE_OBJECT.get(id, { locationHint: "apac-ne" });  
// Southeast Asia-Pacific (Singapore, Indonesia, etc.)  
const stubSE = env.MY_DURABLE_OBJECT.get(id, { locationHint: "apac-se" });  
```  
If your users are spread across all of Asia-Pacific, the existing `apac` hint remains the right choice. Only reach for `apac-ne` or `apac-se` when your traffic is clearly concentrated in one sub-region and you want to minimize round-trip time to that audience. The default behavior and what we generally recommended is not adding a location hint unless absolutely needed, this will create the Durable Object as close to the initializing request as possible to reduce latency.  
As with all location hints, these are best-effort suggestions. Cloudflare will place the Durable Object in a nearby data center, not necessarily the exact hinted location.  
For the full list of supported hints, refer to [Data location — Provide a location hint](https://edgetunnel-b2h.pages.dev/durable-objects/reference/data-location/#provide-a-location-hint).

Jun 19, 2026
1. ### [Outbound connections keep Durable Objects alive](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-19-outbound-connections-keep-dos-alive/)  
[ Durable Objects ](https://edgetunnel-b2h.pages.dev/durable-objects/)  
Durable Objects now remain alive for the duration of active outbound connections created via [connect()](https://edgetunnel-b2h.pages.dev/workers/runtime-apis/tcp-sockets/) or an outbound WebSocket. Previously, a Durable Object would be evicted after 70-140 seconds of no incoming traffic, even if the object had an open outbound connection, which is a common pattern when streaming responses from a large language model (LLM) over TCP or an outbound WebSocket.  
With this change, each active outbound connection prevents eviction. Once all outbound connections close, the standard 70-140 second inactivity window applies before the Durable Object is evicted.  
#### Before: streaming connections were cut off by eviction  
![Timeline showing a Durable Object evicted 70-140 seconds after the last incoming request, cutting off an in-flight LLM stream while the outbound connection is still open](https://edgetunnel-b2h.pages.dev/_astro/outbound-connection-before.DpePflZI_1djzQi.svg)  
#### After: active outbound connections keep the Durable Object alive  
![Timeline showing the same outbound stream completing because the active connection keeps the Durable Object alive, with the inactivity window starting only after the connection closes](https://edgetunnel-b2h.pages.dev/_astro/outbound-connection-after.Bn9BVcYz_1djzQi.svg)  
If you are [building agents on Cloudflare](https://edgetunnel-b2h.pages.dev/agents/), this is especially relevant. An agent that streams tokens from an LLM while [calling models](https://edgetunnel-b2h.pages.dev/agents/concepts/calling-llms/), or that performs [long-running tasks](https://edgetunnel-b2h.pages.dev/agents/concepts/agentic-patterns/long-running-agents/) over an outbound connection, now stays alive for the duration of that connection instead of being evicted mid-stream.

**Limits:**

  * Each outbound connection keeps the Durable Object alive for a maximum of **15 minutes**. After 15 minutes, the connection stops preventing eviction (the connection itself continues operating), and the [standard eviction rules](https://edgetunnel-b2h.pages.dev/durable-objects/concepts/durable-object-lifecycle/) resume.
  * The Durable Object's existing [per-account instance limits](https://edgetunnel-b2h.pages.dev/durable-objects/platform/limits/) still apply.  
For more information, refer to [Lifecycle of a Durable Object](https://edgetunnel-b2h.pages.dev/durable-objects/concepts/durable-object-lifecycle/).

Jun 19, 2026
1. ### [Temporary accounts for AI agent deployments](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-19-temporary-accounts-for-agents/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
AI agents can now deploy Workers to Cloudflare without first requiring a user to sign up, open a browser-based OAuth flow, click through the dashboard, or create an API token. When an agent tries to deploy without Cloudflare credentials, Wrangler can tell it to rerun with `--temporary`, then deploy the Worker to a temporary preview account.  
To try this with your agent, update to Wrangler 4.102.0 or later, make sure you are logged out (`wrangler logout`), and then ask your agent to build something and deploy it to Cloudflare. The agent should follow Wrangler's output and deploy using the `--temporary` flag.  
![Diagram showing an AI agent deploying, verifying, and redeploying a Worker to a temporary account, then claiming it after authentication and moving it to a permanent account](https://edgetunnel-b2h.pages.dev/_astro/claim-deployments-flow.Co0tUHG4_g1dGj.webp)  
```sh  
wrangler deploy --temporary  
```  
The temporary deployment stays live for 60 minutes. During that window, the agent can verify the Worker, redeploy changes, and return both the live Worker URL and claim URL. Opening the claim URL lets you sign in to or create a Cloudflare account and make the temporary account permanent.  
Temporary preview accounts currently support a limited set of products, including Workers, Workers Static Assets, Workers KV, D1, Durable Objects, Hyperdrive, Queues, and SSL/TLS certificates. For supported products, limits, and claim behavior, refer to [Claim deployments (temporary accounts)](https://edgetunnel-b2h.pages.dev/workers/platform/claim-deployments/).  
For more context, refer to [Temporary Cloudflare Accounts for Agents ↗](https://blog.cloudflare.com/temporary-accounts/).

Jun 18, 2026
1. ### [Cloudflare identity provider is now the default for new accounts](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-18-cloudflare-idp-default/)  
[ Cloudflare One ](https://edgetunnel-b2h.pages.dev/cloudflare-one/)[ Access ](https://edgetunnel-b2h.pages.dev/cloudflare-one/access-controls/policies/)  
When you create a new Zero Trust organization, Cloudflare now adds the [Cloudflare identity provider](https://edgetunnel-b2h.pages.dev/cloudflare-one/integrations/identity-providers/cloudflare/) as your default login method. Previously, new organizations started with [one-time PIN (OTP)](https://edgetunnel-b2h.pages.dev/cloudflare-one/integrations/identity-providers/one-time-pin/).  
With the Cloudflare identity provider, your users authenticate using their existing Cloudflare account credentials, and authentication is restricted to members of your account. You can still add OTP or connect any [third-party identity provider](https://edgetunnel-b2h.pages.dev/cloudflare-one/integrations/identity-providers/) whenever you need to.  
This change only applies to newly created accounts. Existing organizations keep the login methods they already have configured. If you would like to use the Cloudflare Identity Provider in an existing account, you must enable it.

Jun 18, 2026
1. ### [exec() is now available for Containers](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-18-container-exec/)  
[ Containers ](https://edgetunnel-b2h.pages.dev/containers/)  
`exec()` is now available for [Containers](https://edgetunnel-b2h.pages.dev/containers/). Use `this.ctx.container.exec()` to start processes inside a running Container, stream standard input and output, inspect exit codes, and signal each process.  
Call `exec()` from a class extending `Container`, or from another Durable Object through `this.ctx.container`. The associated Container must already be running.  
This example starts the Container when needed, then reads its Node.js version:

  * [  JavaScript ](#tab-panel-4969)
  * [  TypeScript ](#tab-panel-4970)

**src/index.js**  
```js  
import { Container } from "@cloudflare/containers";  
export class MyContainer extends Container {  
  async readVersion() {  
    if (!this.ctx.container.running) {  
      await this.start();  
    }  
    const process = await this.ctx.container.exec(["node", "--version"]);  
    const output = await process.output();  
    const decoder = new TextDecoder();  
    return {  
      exitCode: output.exitCode,  
      stdout: decoder.decode(output.stdout),  
      stderr: decoder.decode(output.stderr),  
    };  
  }  
}  
```

**src/index.ts**  
```ts  
import { Container } from "@cloudflare/containers";  
export class MyContainer extends Container {  
  async readVersion() {  
    if (!this.ctx.container.running) {  
      await this.start();  
    }  
    const process = await this.ctx.container.exec(["node", "--version"]);  
    const output = await process.output();  
    const decoder = new TextDecoder();  
    return {  
      exitCode: output.exitCode,  
      stdout: decoder.decode(output.stdout),  
      stderr: decoder.decode(output.stderr),  
    };  
  }  
}  
```  
The command array starts an executable directly, without an implicit shell. Invoke a shell explicitly for pipes, redirects, or variable expansion.  
One RPC method can coordinate multiple `exec()` calls in one caller-to-Durable Object round trip. It can also pass byte-oriented `ReadableStream` input or return streamed output with flow control.  
For options and streaming examples, refer to [Execute commands](https://edgetunnel-b2h.pages.dev/containers/execute-commands/).

Jun 18, 2026
1. ### [Create PlanetScale Postgres and MySQL databases, billed to your Cloudflare account](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-18-planetscale-databases-cloudflare-billing/)  
[ Hyperdrive ](https://edgetunnel-b2h.pages.dev/hyperdrive/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
You can create PlanetScale Postgres and MySQL databases from Cloudflare and bill PlanetScale database usage through your Cloudflare account as a pay-as-you-go customer. Cloudflare contract customers will be able to add PlanetScale usage to their contract in July so reach out to your Cloudflare account team if interested.  
Create a PlanetScale database from the Cloudflare dashboard to check out globally distributed Workers optimized for regional data access.  
[ Go to **Create a PlanetScale database** ](https://dash.cloudflare.com/?to=/:account/workers/hyperdrive?modal=1&type=planetscale&step=1) ![Request flow from a user to Workers, Hyperdrive caches, connection pools, and PlanetScale.](https://edgetunnel-b2h.pages.dev/_astro/planetscale-request-flow.CchJ2m4p_1fTg6l.svg)  
PlanetScale databases created from Cloudflare work with [Workers](https://edgetunnel-b2h.pages.dev/workers/) through [Hyperdrive](https://edgetunnel-b2h.pages.dev/hyperdrive/). Hyperdrive manages database connection pools and query caching, so you can use PlanetScale as a centralized relational database for Workers applications without changing your database drivers, object-relational mapping (ORM) libraries, or SQL tooling.  
PlanetScale usage appears on your Cloudflare invoice each billing period as a dollar total at PlanetScale's standard [pricing ↗](https://planetscale.com/pricing). You can introspect per-database billing usage via PlanetScale's [dashboard ↗](https://planetscale.com/docs/billing#organization-usage-and-billing-page).  
When you create a PlanetScale database from the Cloudflare dashboard, you receive the same PlanetScale developer experience, including development branches, query insights, and Model Context Protocol (MCP) server support for agents.  
To get started, refer to [PlanetScale Postgres and MySQL with Hyperdrive](https://edgetunnel-b2h.pages.dev/hyperdrive/planetscale/).

Jun 18, 2026
1. ### [Updated Workers AI popularity metric in Cloudflare Radar](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-18-radar-workers-ai-inference-metric/)  
[ Radar ](https://edgetunnel-b2h.pages.dev/radar/)  
[**Radar**](https://edgetunnel-b2h.pages.dev/radar/) has changed how it measures [Workers AI](https://edgetunnel-b2h.pages.dev/workers-ai/) model and task popularity.  
Previously, popularity was based on the number of unique accounts running inferences against each model or task. It is now based on the **number of inferences**, giving a more representative view of actual usage volume. This change will affect all new measurements as well as historical data. As a result, the model and task distributions shown on Radar may differ from what you saw previously, and historical trends may shift accordingly.  
The [Workers AI model popularity ↗](https://radar.cloudflare.com/ai-insights#workers-ai-model-popularity) chart shows the distribution of inferences across models.  
![Screenshot of the Workers AI model popularity chart on the AI Insights page](https://edgetunnel-b2h.pages.dev/_astro/workers-ai-model-popularity.CMw_WVXg_Tjg4b.webp)  
The [Workers AI task popularity ↗](https://radar.cloudflare.com/ai-insights#workers-ai-task-popularity) chart shows the distribution of inferences across tasks.  
![Screenshot of the Workers AI task popularity chart on the AI Insights page](https://edgetunnel-b2h.pages.dev/_astro/workers-ai-task-popularity.ZoA-NO8k_ZVCPD5.webp)  
The same data is available via the following API endpoints:

  * [/ai/inference/summary/{dimension}](https://edgetunnel-b2h.pages.dev/api/resources/radar/subresources/ai/subresources/inference/methods/summary%5Fv2/)
  * [/ai/inference/timeseries\_groups/{dimension}](https://edgetunnel-b2h.pages.dev/api/resources/radar/subresources/ai/subresources/inference/methods/timeseries%5Fgroups%5Fv2/)  
Explore the data on the [AI Insights page ↗](https://radar.cloudflare.com/ai-insights).

Jun 18, 2026
1. ### [Cloudflare Fonts error handling and security improvements](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-18-cloudflare-fonts-error-handling-security/)  
[ Speed ](https://edgetunnel-b2h.pages.dev/speed/)  
Cloudflare Fonts now forwards `/cf-fonts` requests to your origin server when it encounters invalid paths or unexpected runtime errors, instead of returning 4xx or 5xx responses directly. This update also adds additional input validation to enhance security.

Jun 17, 2026
1. ### [Manage Artifacts from the Cloudflare dashboard](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-17-dashboard-management/)  
[ Artifacts ](https://edgetunnel-b2h.pages.dev/artifacts/)  
You can now configure [Artifacts](https://edgetunnel-b2h.pages.dev/artifacts/concepts/how-artifacts-works/) namespaces, repos, and tokens directly from the Cloudflare dashboard.  
Artifacts is Git-compatible storage that lets you store repos on Cloudflare and interact with them using standard Git workflows.  
You can view and create [namespaces](https://edgetunnel-b2h.pages.dev/artifacts/concepts/namespaces/#use-namespaces-as-containers), which are top-level containers for repos:  
![Artifacts namespaces dashboard showing namespace search and create namespace controls](https://edgetunnel-b2h.pages.dev/_astro/dashboard-namespaces.0BJelWZh_Z1uJ1iD.webp)  
You can view, create, fork, and search repos within a namespace:  
![Artifacts repositories dashboard showing repo source, access, and created columns](https://edgetunnel-b2h.pages.dev/_astro/dashboard-repositories.M9P9JUL__Agf9h.webp)  
You can open a repo to view its files and copy its Git remote URL.  
![Artifacts repository overview showing files, commits, token management, and quick actions](https://edgetunnel-b2h.pages.dev/_astro/dashboard-repo-overview.CSHxrCW2_81obq.webp)  
You can also provision tokens directly from the dashboard to scope Git access to a single repo, with read tokens for clone, fetch, and pull workflows, or write tokens when a client needs to push changes.  
To get started, go to the [Cloudflare dashboard ↗](https://dash.cloudflare.com/) and select **Storage & databases** \> **Artifacts**.  
If you are enrolled in the Artifacts beta, you can use the dashboard to set up Artifacts. If you would like to join the beta, complete the [request form ↗](https://forms.gle/DwBoPRa3CWQ8ajFp7).

Jun 17, 2026
1. ### [Post-quantum ML-DSA certificates for Authenticated Origin Pulls and Custom Origin Trust Store](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-17-pqc-mldsa-aop-cots/)  
[ SSL/TLS ](https://edgetunnel-b2h.pages.dev/ssl/)  
Cloudflare now accepts [ML-DSA ↗](https://csrc.nist.gov/pubs/fips/204/final) (FIPS 204) post-quantum certificates on the connection between Cloudflare's edge and your origin server. Combined with our existing [X25519MLKEM768](https://edgetunnel-b2h.pages.dev/ssl/post-quantum-cryptography/#hybrid-key-agreement) key agreement, this lets you establish end-to-end post-quantum authentication on the Cloudflare-to-origin connection.  
ML-DSA is supported in two origin-facing features:

  * [Authenticated Origin Pulls](https://edgetunnel-b2h.pages.dev/ssl/origin-configuration/authenticated-origin-pull/) (AOP) — upload an ML-DSA client certificate that Cloudflare will present during the mTLS handshake to your origin. Available at both zone-level and per-hostname scopes.
  * [Custom Origin Trust Store](https://edgetunnel-b2h.pages.dev/ssl/origin-configuration/custom-origin-trust-store/) (COTS) — upload an ML-DSA certificate authority that Cloudflare will trust when validating your origin server certificate under [Full (strict) encryption mode](https://edgetunnel-b2h.pages.dev/ssl/origin-configuration/ssl-modes/full-strict/).  
Refer to [Post-quantum signatures](https://edgetunnel-b2h.pages.dev/ssl/post-quantum-cryptography/pqc-to-origin/#post-quantum-signatures) for certificate generation and setup guidance, and to [PQC in Cloudflare products](https://edgetunnel-b2h.pages.dev/ssl/post-quantum-cryptography/pqc-cloudflare-products/) for the current post-quantum deployment status across Cloudflare.

Jun 16, 2026
1. ### [Agents SDK improves browser automation, code execution, and recovery](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-16-agents-sdk-v0161/)  
[ Agents ](https://edgetunnel-b2h.pages.dev/agents/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
The latest release of the [Agents SDK ↗](https://github.com/cloudflare/agents) makes it easier to build agents that can safely interact with real systems and keep working through interruptions.  
Agents can now browse websites through Browser Run, write code against external tools through Code Mode, use client-provided tools when delegating to Think sub-agents, and recover more reliably from deploys, Durable Object evictions, and connection churn.  
#### Safer browser automation  
Agents can now use [Browser Run](https://edgetunnel-b2h.pages.dev/browser-run/) through a single durable `browser_execute` tool. Instead of choosing from a fixed list of actions, the model writes code against the Chrome DevTools Protocol (CDP) and can inspect pages, capture screenshots, read rendered content, debug frontend behavior, and interact with live browser sessions.

  * [  JavaScript ](#tab-panel-4963)
  * [  TypeScript ](#tab-panel-4964)

**JavaScript**  
```js  
const browserTools = createBrowserTools({  
  ctx: this.ctx,  
  browser: this.env.BROWSER,  
  loader: this.env.LOADER,  
  session: { mode: "dynamic" },  
});  
```

**TypeScript**  
```ts  
const browserTools = createBrowserTools({  
  ctx: this.ctx,  
  browser: this.env.BROWSER,  
  loader: this.env.LOADER,  
  session: { mode: "dynamic" },  
});  
```  
Browser sessions can be one-time, reused, or promoted from one-time to persistent during a run. This is useful when an agent needs a human to log in, complete MFA, or approve a sensitive action. The run can pause, keep the same tabs and cookies, and resume after approval.  
The browser tools also add Live View URLs, optional session recording, and quick actions such as `browser_markdown`, `browser_extract`, `browser_links`, and `browser_scrape` for one-shot browsing tasks.  
#### Resumable code execution with approvals  
Code Mode now uses `createCodemodeRuntime`, connectors, and a durable execution log. This lets you give a model one `codemode` tool instead of a large prompt full of tool definitions. The model can discover the capabilities it needs, write code against typed globals, and reuse saved snippets.

  * [  JavaScript ](#tab-panel-4967)
  * [  TypeScript ](#tab-panel-4968)

**JavaScript**  
```js  
const runtime = createCodemodeRuntime({  
  ctx: this.ctx,  
  executor: new DynamicWorkerExecutor({ loader: this.env.LOADER }),  
  connectors: [new GithubConnector(this.ctx, this.env, connection)],  
});  
const result = streamText({  
  model,  
  messages,  
  tools: { codemode: runtime.tool() },  
});  
```

**TypeScript**  
```ts  
const runtime = createCodemodeRuntime({  
  ctx: this.ctx,  
  executor: new DynamicWorkerExecutor({ loader: this.env.LOADER }),  
  connectors: [new GithubConnector(this.ctx, this.env, connection)],  
});  
const result = streamText({  
  model,  
  messages,  
  tools: { codemode: runtime.tool() },  
});  
```  
When the code reaches an approval-gated action, the runtime pauses execution and returns a pending approval. After approval, completed calls replay from the durable log, the approved action runs, and the same code continues. This makes it practical to build agents that create issues, update external systems, or perform other side effects without custom pause-and-resume logic for every tool.  
#### Better Think delegation  
Think sub-agents can now use client-defined tools over the RPC `chat()` path. A parent agent can pass tool schemas with `clientTools` and resolve tool calls through `onClientToolCall`. This lets delegated agents use caller-provided capabilities without requiring a browser WebSocket.

  * [  JavaScript ](#tab-panel-4971)
  * [  TypeScript ](#tab-panel-4972)

**JavaScript**  
```js  
await child.chat(message, callback, {  
  signal,  
  clientTools: [  
    {  
      name: "get_user_timezone",  
      description: "Get the caller's timezone",  
      parameters: { type: "object" },  
    },  
  ],  
  onClientToolCall: async ({ toolName, input }) => {  
    return runClientTool(toolName, input);  
  },  
});  
```

**TypeScript**  
```ts  
await child.chat(message, callback, {  
  signal,  
  clientTools: [  
    {  
      name: "get_user_timezone",  
      description: "Get the caller's timezone",  
      parameters: { type: "object" },  
    },  
  ],  
  onClientToolCall: async ({ toolName, input }) => {  
    return runClientTool(toolName, input);  
  },  
});  
```  
Think Workflows also improve `step.prompt()`. A prompt step now runs a full agentic turn before returning structured output, so the agent can call tools before producing the typed result. This makes Workflow steps more useful for durable triage, research, and approval flows.  
The unified Think execute tool can also include `cdp.*` browser capabilities alongside `state.*` and `tools.*` when Browser Run is bound.  
#### Voice output device selection  
Voice clients can route assistant audio to a specific output device. Use `outputDeviceId` with `useVoiceAgent`, or call `client.setOutputDevice()` from the framework-agnostic client.

  * [  JavaScript ](#tab-panel-4965)
  * [  TypeScript ](#tab-panel-4966)

**JavaScript**  
```js  
const voice = useVoiceAgent({  
  agent: "MyVoiceAgent",  
  outputDeviceId: selectedSpeakerId,  
});  
```

**TypeScript**  
```ts  
const voice = useVoiceAgent({  
  agent: "MyVoiceAgent",  
  outputDeviceId: selectedSpeakerId,  
});  
```  
Browsers without speaker-selection support continue playing through the default output device and report a non-fatal `outputDeviceError`.  
#### Reliability fixes  
This release includes several fixes for production agents:

  * `useAgent` and `AgentClient` handle WebSocket replacement more reliably during reconnects and configuration changes.
  * Chat stream replay is more reliable after reconnects, deploys, and provider errors.
  * Fiber recovery continues across multi-pass scans and backs off when recovery hooks keep failing.
  * Agent teardown continues even when the request that started teardown is canceled.
  * Large session histories use byte-budgeted reads to reduce memory pressure during startup.  
#### Upgrade  
To update to the latest version:  
 npm  yarn  pnpm  bun  
```  
npm i agents@latest @cloudflare/think@latest @cloudflare/codemode@latest @cloudflare/ai-chat@latest @cloudflare/voice@latest  
```  
```  
yarn add agents@latest @cloudflare/think@latest @cloudflare/codemode@latest @cloudflare/ai-chat@latest @cloudflare/voice@latest  
```  
```  
pnpm add agents@latest @cloudflare/think@latest @cloudflare/codemode@latest @cloudflare/ai-chat@latest @cloudflare/voice@latest  
```  
```  
bun add agents@latest @cloudflare/think@latest @cloudflare/codemode@latest @cloudflare/ai-chat@latest @cloudflare/voice@latest  
```  
Refer to the [Code Mode documentation](https://edgetunnel-b2h.pages.dev/agents/tools/codemode/), [Browser tools documentation](https://edgetunnel-b2h.pages.dev/agents/tools/browser/), [Think tools documentation](https://edgetunnel-b2h.pages.dev/agents/harnesses/think/tools/), and [Voice documentation](https://edgetunnel-b2h.pages.dev/agents/communication-channels/voice/) for more information.

Jun 16, 2026
1. ### [New optimization features in Images](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-16-new-optimization-features/)  
[ Cloudflare Images ](https://edgetunnel-b2h.pages.dev/images/)  
These updates introduce new features for optimizing and manipulating with Images:

  * **New `composite` option:** Control how [overlays are blended](https://edgetunnel-b2h.pages.dev/images/optimization/draw-overlays/#composite) with the base image.
  * **Percentage widths:** Set the dimensions of an overlay as [a fraction of the dimensions](https://edgetunnel-b2h.pages.dev/images/optimization/draw-overlays/#width-and-height) of the base image.
  * **New `fit` modes:** Use [aspect-crop](https://edgetunnel-b2h.pages.dev/images/optimization/features/#aspect-crop) to always preserve the target aspect ratio or [scale-up](https://edgetunnel-b2h.pages.dev/images/optimization/features/#scale-up) to always enlarge images.
  * **New `upscale` parameter:** Apply [AI upscaling](https://edgetunnel-b2h.pages.dev/images/optimization/features/#upscale) to produce sharper, more detailed results when enlarging images.

Jun 16, 2026
1. ### [Introducing GLM-5.2 on Workers AI](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-16-glm-52-workers-ai/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)[ Agents ](https://edgetunnel-b2h.pages.dev/agents/)[ Workers AI ](https://edgetunnel-b2h.pages.dev/workers-ai/)  
We are excited to announce **GLM-5.2** on Workers AI, Z.ai's flagship agentic coding model.  
[@cf/zai-org/glm-5.2](https://edgetunnel-b2h.pages.dev/workers-ai/models/glm-5.2/) is a text generation model built for agentic coding workflows. With function calling and reasoning support, it can handle long codebases, multi-step planning, and tool-augmented agents.

**Key features and use cases:**

  * **Agentic coding**: Designed for autonomous coding tasks, long-horizon planning, and complex software engineering workflows
  * **Large context window**: GLM-5.2 supports up to a 1,048,576 token context window. Workers AI is launching the model with a 262,144 token context window and plans to increase this in the future
  * **Function calling**: Build agents that invoke tools and APIs across multiple conversation turns
  * **Reasoning**: Tackles complex problem-solving and step-by-step reasoning tasks  
Use GLM-5.2 through the [Workers AI binding](https://edgetunnel-b2h.pages.dev/workers-ai/configuration/bindings/) (`env.AI.run()`), the REST API at `/run` or `/v1/chat/completions`, or [AI Gateway](https://edgetunnel-b2h.pages.dev/ai-gateway/).  
Pricing is available on the [model page](https://edgetunnel-b2h.pages.dev/workers-ai/models/glm-5.2/) or [pricing page](https://edgetunnel-b2h.pages.dev/workers-ai/platform/pricing/).

Jun 16, 2026
1. ### [TCP connections via connect() over VPC Networks](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-16-tcp-connect-vpc-networks/)  
[ Workers VPC ](https://edgetunnel-b2h.pages.dev/workers-vpc/)  
[VPC Network](https://edgetunnel-b2h.pages.dev/workers-vpc/configuration/vpc-networks/) bindings now support the [connect()](https://edgetunnel-b2h.pages.dev/workers/runtime-apis/tcp-sockets/) Socket API for raw TCP connections to private destinations, in addition to HTTP traffic via `fetch()`.  
This means Workers can now open TCP sockets to any private service reachable through the bound Cloudflare Tunnel, Cloudflare Mesh, or Cloudflare WAN on-ramp — Redis, Memcached, MQTT, custom binary protocols, or any other TCP-based service.

  * [  wrangler.jsonc ](#tab-panel-4961)
  * [  wrangler.toml ](#tab-panel-4962)

**JSONC**  
```jsonc  
{  
  "$schema": "./node_modules/wrangler/config-schema.json",  
  "vpc_networks": [  
    {  
      "binding": "PRIVATE_NETWORK",  
      "network_id": "cf1:network",  
      "remote": true  
    }  
  ]  
}  
```

**TOML**  
```toml  
[[vpc_networks]]  
binding = "PRIVATE_NETWORK"  
network_id = "cf1:network"  
remote = true  
```  
At runtime, use `connect()` on the binding to open a TCP socket to a private destination:

**TypeScript**  
```ts  
export default {  
  async fetch(request: Request, env: Env) {  
    // Open a TCP connection to a private Redis instance  
    const socket = await env.PRIVATE_NETWORK.connect("10.0.1.50:6379");  
    // Write a Redis PING command  
    const writer = socket.writable.getWriter();  
    await writer.write(new TextEncoder().encode("PING\r\n"));  
    await writer.close();  
    return new Response(socket.readable);  
  },  
};  
```  
Note  
`connect()` over VPC Networks currently supports plaintext TCP only.  
For more details, refer to [VPC Networks](https://edgetunnel-b2h.pages.dev/workers-vpc/configuration/vpc-networks/) and the [Workers Binding API](https://edgetunnel-b2h.pages.dev/workers-vpc/api/).

Jun 16, 2026
1. ### [Workers tracing now supports custom spans](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-16-custom-spans/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
You can now create custom trace spans in your Workers code using `tracing.enterSpan()`. Custom spans appear alongside the automatic platform instrumentation (fetch calls, KV reads, D1 queries, and other platform operations) in your traces and OpenTelemetry exports, with correct parent-child nesting.  
The API is available via `import { tracing } from "cloudflare:workers"` or through the handler context as `ctx.tracing`:

**TypeScript**  
```ts  
import { tracing } from "cloudflare:workers";  
export default {  
  async fetch(request, env, ctx) {  
    return tracing.enterSpan("handleRequest", async (span) => {  
      span.setAttribute("url.path", new URL(request.url).pathname);  
      const data = await env.MY_KV.get("key");  
      return new Response(data);  
    });  
  },  
};  
```  
Spans nest automatically based on the JavaScript async context, and are auto-ended when the callback returns or its returned promise settles. The `Span` object provides `setAttribute(key, value)` for attaching metadata and an `isTraced` property to check whether the current request is being sampled.  
![Trace waterfall showing custom spans nested alongside automatic KV and fetch instrumentation](https://edgetunnel-b2h.pages.dev/_astro/wobs_custom_spans_screenshot.B-hsHjyv_ZGVlIY.webp)  
[Tracing must be enabled](https://edgetunnel-b2h.pages.dev/workers/observability/traces/#how-to-enable-tracing) in your Wrangler configuration for spans to be recorded.  
For full API details and examples, refer to [Custom spans](https://edgetunnel-b2h.pages.dev/workers/observability/traces/custom-spans/).

Jun 15, 2026
1. ### [Use Cloudforce One threat intelligence in WAF rules](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-15-threat-intelligence-fields/)  
[ WAF ](https://edgetunnel-b2h.pages.dev/waf/)  
You can now match incoming requests against Cloudforce One threat intelligence in your WAF rules. A new detection looks up the client IP address of each request against the threat intelligence database. If the IP was involved in threat activity in the past seven days, Cloudflare populates `cf.intel.ip.*` fields that you can use in [custom rules](https://edgetunnel-b2h.pages.dev/waf/custom-rules/) and [rate limiting rules](https://edgetunnel-b2h.pages.dev/waf/rate-limiting-rules/).  
The detection populates the following fields. Use the [any()](https://edgetunnel-b2h.pages.dev/ruleset-engine/rules-language/functions/#any) function with the `[*]` wildcard to match array values:

  * `cf.intel.ip.datasets` — the dataset that flagged the IP address (`ddos` or `waf`).
  * `cf.intel.ip.target_industries` — industries the IP address has targeted.
  * `cf.intel.ip.attacker_names` — known threat actors associated with the IP address.
  * `cf.intel.ip.attacker_countries` — source countries of the threat activity.
  * `cf.intel.ip.target_countries` — countries the IP address has targeted.  
For example, the following custom rule expression blocks requests from IP addresses associated with DDoS activity that have targeted France:  
```txt  
any(cf.intel.ip.target_countries[*] == "FR") and any(cf.intel.ip.datasets[*] == "ddos")  
```  
These fields work with the Cloudflare API and Terraform. Matches are logged in [Security Analytics](https://edgetunnel-b2h.pages.dev/waf/analytics/security-analytics/).  
The threat intelligence detection is available to customers with an active [Cloudforce One](https://edgetunnel-b2h.pages.dev/security-center/cloudforce-one/) subscription. For more information, refer to [Threat intelligence](https://edgetunnel-b2h.pages.dev/waf/detections/threat-intelligence/).

Jun 15, 2026
1. ### [WAF Release - 2026-06-15](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-15-waf-release/)  
[ WAF ](https://edgetunnel-b2h.pages.dev/waf/)  
This week's release introduces new managed protection to address a critical SQL injection vulnerability in Ghost CMS (CVE-2026-26980) and a new generic rule designed to identify and block sophisticated SQL Injection (SQLi) bypass attempts leveraging obfuscated boolean logic. These rules protect affected installations from unauthorized data exfiltration at the network edge.

**Key Findings**

  * CVE-2026-26980: A blind SQL injection vulnerability in the Ghost CMS Content API (versions 3.24.0 to 6.19.0) allows unauthenticated remote attackers to inject malicious SQL commands via query parameters due to improper input validation.

| Ruleset                    | Rule ID     | Legacy Rule ID | Description                           | Previous Action | New Action | Comments                 |
| -------------------------- | ----------- | -------------- | ------------------------------------- | --------------- | ---------- | ------------------------ |
| Cloudflare Managed Ruleset | ...b4c29bc6 | N/A            | Ghost CMS - SQLi - CVE:CVE-2026-26980 | Log             | Block      | This is a new detection. |
| Cloudflare Managed Ruleset | ...b56f403f | N/A            | SQLi - Obfuscated Boolean - URI       | Log             | Disabled   | This is a new detection. |

Jun 12, 2026
1. ### [View the user agent of requests in AI Gateway logs](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-12-user-agent-logging/)  
[ AI Gateway ](https://edgetunnel-b2h.pages.dev/ai-gateway/)  
AI Gateway logs now capture the user agent of the client that made each request, making it easier to identify which SDK, library, or application sent the traffic flowing through your gateway. For example, you can tell apart requests coming from `openai-python` versus a custom application or a Cloudflare Worker.  
The user agent appears alongside the other details in each log entry, and you can filter logs by user agent (equals, does not equal, or contains) in the dashboard.  
For more information, refer to [Logging](https://edgetunnel-b2h.pages.dev/ai-gateway/observability/logging/).

Jun 12, 2026
1. ### [Filter Durable Objects metrics by object ID or name](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-12-durable-objects-metrics-filter-by-id-name/)  
[ Durable Objects ](https://edgetunnel-b2h.pages.dev/durable-objects/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
You can now filter the **Metrics** tab for a Durable Objects namespace by an individual Durable Object's [ID](https://edgetunnel-b2h.pages.dev/durable-objects/api/id/) or [name](https://edgetunnel-b2h.pages.dev/durable-objects/api/id/#name) in the Cloudflare dashboard. Previously, metrics charts only showed aggregate, namespace-level data, making it difficult to isolate the behavior of a specific object.  
[ Go to **Durable Objects** ](https://dash.cloudflare.com/?to=/:account/workers/durable-objects) ![The Durable Objects Metrics tab filtered to a single object by ID, showing per-object requests and errors by invocation status.](https://edgetunnel-b2h.pages.dev/_astro/durable-objects-metrics-dashboard.BFZTyhWU_Z2e46Sb.webp)  
Start typing an ID or name into the filter and select a match from the autocomplete dropdown. The autocomplete only shows objects with invocations during the selected time range, so an object that does not appear has not been invoked in that window. This does not necessarily mean the object has been deleted. Every chart on the page updates to reflect only the selected object. This makes it easier to identify and investigate a single Durable Object when debugging a high-traffic object, an error spike, or unexpected storage usage. Clear the filter to return to namespace-level metrics.  
Metrics are powered by the [GraphQL Analytics API](https://edgetunnel-b2h.pages.dev/analytics/graphql-api/), so standard analytics behavior such as ingestion delay and [sampling](https://edgetunnel-b2h.pages.dev/analytics/faq/graphql-api-inconsistent-results/) applies.  
For more information, refer to [Metrics and analytics](https://edgetunnel-b2h.pages.dev/durable-objects/observability/metrics-and-analytics/).

Jun 12, 2026
1. ### [Terraform v5.20.0 now available](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-12-terraform-v5200-provider/)  
[ Terraform ](https://edgetunnel-b2h.pages.dev/terraform/)  
Cloudflare's Terraform v5 Provider makes it easy for developers to manage their Cloudflare infrastructure using a configuration as code approach. It releases every [2-3 weeks ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure that you can always manage the latest features in the platform. This week, we launched Terraform v5.20.0, which adds 24 new resources, bumps the underlying Go SDK to cloudflare-go v7, and includes a range of bug fixes and state upgraders based on community feedback.  
#### New resources

  * **cloudflare\_ai\_search\_namespace:** Manage AI Search namespaces
  * **cloudflare\_custom\_csr:** Manage custom certificate signing requests
  * **cloudflare\_dls\_prefix\_binding:** Manage DLS regional service prefix bindings
  * **cloudflare\_flagship\_app:** Manage Flagship feature flag apps
  * **cloudflare\_flagship\_flag:** Manage Flagship feature flags
  * **cloudflare\_google\_tag\_gateway:** Manage Google Tag Gateway
  * **cloudflare\_load\_balancer\_monitor\_group:** Manage load balancer monitor groups
  * **cloudflare\_oauth\_client:** Manage IAM OAuth clients
  * **cloudflare\_origin\_cloud\_region:** Manage origin cloud regions (v2 endpoints)
  * **cloudflare\_secrets\_store:** Manage Secrets Store instances
  * **cloudflare\_secrets\_store\_secret:** Manage Secrets Store secrets
  * **cloudflare\_share:** Manage resource shares
  * **cloudflare\_share\_recipient:** Manage share recipients
  * **cloudflare\_share\_resource:** Manage shared resources
  * **cloudflare\_zero\_trust\_device\_deployment\_groups:** Manage Zero Trust device deployment groups
  * **cloudflare\_zero\_trust\_dlp\_data\_class:** Manage DLP data classes
  * **cloudflare\_zero\_trust\_dlp\_data\_tag:** Manage DLP data tags
  * **cloudflare\_zero\_trust\_dlp\_data\_tag\_category:** Manage DLP data tag categories
  * **cloudflare\_zero\_trust\_dlp\_sensitivity\_group:** Manage DLP sensitivity groups
  * **cloudflare\_zero\_trust\_dlp\_sensitivity\_level:** Manage DLP sensitivity levels
  * **cloudflare\_zero\_trust\_dlp\_sensitivity\_level\_order:** Manage DLP sensitivity level ordering
  * **cloudflare\_zero\_trust\_resource\_library\_application:** Manage Zero Trust resource library applications
  * **cloudflare\_zero\_trust\_resource\_library\_category:** Manage Zero Trust resource library categories
  * **cloudflare\_zero\_trust\_tunnel\_warp\_connector\_config:** Manage WARP connector tunnel configurations  
#### Features

  * **cache:** add create (POST) method for smart\_tiered\_cache
  * **cache:** update OPCR config to v2 endpoints
  * **dlp:** promote classification Stainless config to main
  * **dlp:** add custom prompt topics endpoint
  * **email\_security\_block\_sender:** state upgrader for v4 to v5 migration
  * **email\_security\_impersonation\_registry:** state upgrader for v4 to v5 migration
  * **email\_security\_trusted\_domains:** state upgrader for v4 to v5 migration
  * **snippets:** add Terraform `id_property` annotations for snippet and snippet\_rules
  * bump Go SDK to cloudflare-go v7  
#### Bug fixes

  * **account\_member:** missing upgrade path from v5.0–v5.15
  * **authenticated\_origin\_pulls\_settings:** nil pointer panic
  * **bot\_management:** restore `content_bots_protection` handling in model.go
  * **dns\_record:** prevent FQDN normalization from swallowing name shortening changes
  * **list:** nullify empty nested objects to prevent inconsistent result after apply
  * **load\_balancer\_pool:** accept early-v5 object-shape state at schema\_version=0
  * **load\_balancer\_pool:** add `UseStateForUnknown` for `load_shedding` attribute to prevent drift
  * **r2\_custom\_domain:** restore degraded-response handling in resource.go
  * **regional\_hostname:** update cloudflare-go imports from v6 to v7
  * **secrets\_store:** fix model/schema parity and guard acceptance tests
  * **spectrum\_application:** accept early-v5 object-shape state at schema\_version=0
  * **worker:** preserve `observability.traces.propagation_policy` across reads
  * **worker:** add `propagation_policy` to observability defaults
  * **worker\_version:** restore handwritten D1 `database_id` handling
  * **workers\_custom\_domain:** missing `CertId` field in state migration
  * **workers\_script:** restore annotations Read workaround stripped by codegen
  * **zero\_trust\_access\_identity\_provider:** change `read_only` from computed to optional
  * **zero\_trust\_access\_identity\_provider:** add `UseStateForUnknown` to SAML-only config fields
  * **zero\_trust\_access\_identity\_provider:** use `UseNonNullStateForUnknown` on scim\_config fields
  * **zero\_trust\_access\_policy:** populate `account_id` when migrating zone-scoped v4 state
  * **zero\_trust\_access\_policy:** missing `common_names` transform in migration
  * gracefully handle nil pointer dereference when config has `attributes_flat` during migration
  * set initial schema version to 500 for all new resources  
#### Refactors  
Extracted `MoveState` nil guard into shared helper  
#### For more information

  * [Terraform Provider ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
  * [Version 5 Migration Guide ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-migration)
  * [Documentation on using Terraform with Cloudflare](https://edgetunnel-b2h.pages.dev/terraform/)
  * [List of stabilized resources ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237)

Jun 12, 2026
1. ### [Moonshot AI Kimi K2.7 Code now available on Workers AI](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-12-kimi-k2-7-code-workers-ai/)  
[ Workers AI ](https://edgetunnel-b2h.pages.dev/workers-ai/)  
[@cf/moonshotai/kimi-k2.7-code](https://edgetunnel-b2h.pages.dev/workers-ai/models/kimi-k2.7-code/) is now available on Workers AI. Kimi K2.7 Code is a code-optimized variant of the Kimi K2 family, built on a Mixture-of-Experts architecture with 1T total parameters and 32B active per token.  
#### Improved coding and agent performance  
K2.7 Code delivers meaningful gains over K2.6 on coding and agentic benchmarks:

  * **+21.8%** on Kimi Code Bench v2
  * **+11.0%** on Program Bench
  * **+31.5%** on MLS Bench Lite  
#### Reasoning efficiency  
K2.7 Code uses 30% fewer reasoning tokens compared to K2.6, reducing overthinking and lowering inference cost for reasoning-heavy workloads.  
#### Key capabilities

  * **262.1k token context window** for retaining full conversation history, tool definitions, and codebases across long-running agent sessions
  * **Long-horizon coding** with improved instruction following and higher end-to-end coding task success rates
  * **Vision inputs** for processing images alongside text
  * **Thinking mode** with configurable reasoning depth via `chat_template_kwargs.thinking`
  * **Multi-turn tool calling** for building agents that invoke tools across multiple conversation turns
  * **Structured outputs** with JSON schema support  
#### Differences from Kimi K2.6  
If you are migrating from Kimi K2.6, note the following:

  * K2.7 Code is optimized for coding tasks with improved benchmark performance and reasoning efficiency
  * Cached input token pricing is $0.19 per M tokens (vs $0.16 for K2.6)
  * API usage is identical — no parameter changes required  
#### Get started  
Use Kimi K2.7 Code through the [Workers AI binding](https://edgetunnel-b2h.pages.dev/workers-ai/configuration/bindings/) (`env.AI.run()`), the REST API at `/ai/run`, or the OpenAI-compatible endpoint at `/v1/chat/completions`. You can also use [AI Gateway](https://edgetunnel-b2h.pages.dev/ai-gateway/) with any of these endpoints.  
For more information, refer to the [Kimi K2.7 Code model page](https://edgetunnel-b2h.pages.dev/workers-ai/models/kimi-k2.7-code/) and [pricing](https://edgetunnel-b2h.pages.dev/workers-ai/platform/pricing/).

Jun 11, 2026
1. ### [New formats parameter for the Browser Run /snapshot endpoint](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-11-browser-run-snapshot-formats/)  
[ Browser Run ](https://edgetunnel-b2h.pages.dev/browser-run/)  
[Browser Run](https://edgetunnel-b2h.pages.dev/browser-run/)'s [/snapshot endpoint](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/snapshot/) now supports a `formats` parameter that lets you return multiple page formats in a single API call. Previously, `/snapshot` returned only HTML content and a screenshot. You can now also include Markdown and the accessibility tree in the same response.  
These formats are particularly useful for AI agent workflows:

  * Markdown provides a token-efficient representation of page content that LLMs can process directly, without parsing HTML markup.
  * The accessibility tree provides a structured representation of a page's elements, including roles, labels, and hierarchy, helping LLMs understand page structure and navigate its contents.  
The following example returns a screenshot, Markdown, and the accessibility tree in one call:

  * [ curl ](#tab-panel-4958)
  * [ TypeScript SDK ](#tab-panel-4959)
  * [ Workers Bindings ](#tab-panel-4960)  
```bash  
curl -X POST 'https://api.cloudflare.com/client/v4/accounts/<accountId>/browser-rendering/snapshot' \
  -H 'Authorization: Bearer <apiToken>' \
  -H 'Content-Type: application/json' \
  -d '{  
    "url": "https://example.com/",  
    "formats": ["screenshot", "markdown", "accessibilityTree"]  
  }'  
```

**TypeScript**  
```typescript  
import Cloudflare from "cloudflare";  
const client = new Cloudflare({  
  apiToken: process.env["CLOUDFLARE_API_TOKEN"],  
});  
const snapshot = await client.browserRendering.snapshot.create({  
  account_id: process.env["CLOUDFLARE_ACCOUNT_ID"],  
  url: "https://example.com/",  
  formats: ["screenshot", "markdown", "accessibilityTree"],  
});  
console.log(snapshot.markdown);  
console.log(snapshot.accessibilityTree);  
```

**TypeScript**  
```typescript  
interface Env {  
  BROWSER: BrowserRun;  
}  
export default {  
  async fetch(request, env): Promise<Response> {  
    return await env.BROWSER.quickAction("snapshot", {  
      url: "https://example.com/",  
      formats: ["screenshot", "markdown", "accessibilityTree"],  
    });  
  },  
} satisfies ExportedHandler<Env>;  
```  
You must request at least two formats. If you only need one, use the respective single-format endpoint such as [/screenshot](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/screenshot-endpoint/) or [/markdown](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/markdown-endpoint/).  
Refer to the [/snapshot documentation](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/snapshot/) for the full list of accepted values.

Jun 11, 2026
1. ### [Define custom topics for AI prompt protection](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-11-custom-ai-prompt-topics/)  
[ Data Loss Prevention ](https://edgetunnel-b2h.pages.dev/cloudflare-one/data-loss-prevention/)  
You can now define custom topics for AI prompt protection. Predefined [AI prompt topics](https://edgetunnel-b2h.pages.dev/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics) cover common content and intent categories such as PII, source code, and jailbreak attempts. Custom topics let you detect unique or proprietary concepts that are not included in predefined categories.  
You describe a custom topic in natural language, and Cloudflare DLP detects whether a prompt matches that topic based on context rather than specific keywords. For example, a topic that describes confidential merger discussions matches a prompt that paraphrases the deal, even when the prompt never uses the word merger or names the companies involved. To detect literal values such as internal codenames or product identifiers, use a [custom wordlist or pattern entry](https://edgetunnel-b2h.pages.dev/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#custom-wordlist-datasets) instead.  
Custom topics run through the same [application granular controls](https://edgetunnel-b2h.pages.dev/cloudflare-one/traffic-policies/http-policies/#granular-controls) path as predefined AI prompt topics. Custom topics are available for ChatGPT, Google Gemini, Perplexity, and Claude.  
#### Create a custom AI prompt topic

  1. In the [Cloudflare dashboard ↗](https://dash.cloudflare.com/), go to **Zero Trust** \> **Data loss prevention** \> **Detection entries**.
  2. Select **AI prompt topics**, then select **Custom Prompt Topic**.
  3. Describe the topic in natural language. Be specific about the concept you want to detect. For example, describe unreleased product roadmap details or confidential customer contract terms.
  4. Add this detection entry to an existing DLP profile, or [create a new DLP profile](https://edgetunnel-b2h.pages.dev/cloudflare-one/data-loss-prevention/dlp-profiles/#build-a-custom-profile).
  5. Use the profile in a Gateway HTTP policy to log or block prompts that match the topic.  
Note  
Write the description as a concept to classify, not a list of keywords. For example, describe "internal financial forecasts and unreleased revenue figures" rather than listing specific document names.  
For more information, refer to [AI prompt topics](https://edgetunnel-b2h.pages.dev/cloudflare-one/data-loss-prevention/detection-entries/configure-detection-entries/#ai-prompt-topics).

```json
{"@context":"https://schema.org","@type":"BlogPosting","@id":"https://edgetunnel-b2h.pages.dev/changelog/4/#page","headline":"Changelogs | Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/changelog/4/","inLanguage":"en","image":"https://edgetunnel-b2h.pages.dev/cf-twitter-card.png","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://edgetunnel-b2h.pages.dev/#website","name":"Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/"}}
```