---
title: Developer platform Changelog
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/) 

Developer platform

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

Sep 18, 2025
1. ### [Connect and secure any private or public app by hostname, not IP — with hostname routing for Cloudflare Tunnel](https://edgetunnel-b2h.pages.dev/changelog/post/2025-09-18-tunnel-hostname-routing/)  
[ Cloudflare Tunnel ](https://edgetunnel-b2h.pages.dev/tunnel/)[ Cloudflare Tunnel for SASE ](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/)  
You can now route private traffic to [Cloudflare Tunnel](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/) based on a hostname or domain, moving beyond the limitations of IP-based routing. This new capability is **free for all Cloudflare One customers**.  
Previously, Tunnel routes could only be defined by IP address or [CIDR range](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/). This created a challenge for modern applications with dynamic or ephemeral IP addresses, often forcing administrators to maintain complex and brittle IP lists.  
![Hostname-based routing in Cloudflare Tunnel](https://edgetunnel-b2h.pages.dev/_astro/tunnel-hostname-routing.DSi8MP_7_Z1E6Ym4.webp)  

**What’s new:**

  * **Hostname & Domain Routing**: Create routes for individual hostnames (e.g., `payroll.acme.local`) or entire domains (e.g., `*.acme.local`) and direct their traffic to a specific Tunnel.
  * **Simplified Zero Trust Policies**: Build resilient policies in Cloudflare Access and Gateway using stable hostnames, making it dramatically easier to apply per-resource authorization for your private applications.
  * **Precise Egress Control**: Route traffic for public hostnames (e.g., `bank.example.com`) through a specific Tunnel to enforce a dedicated source IP, solving the IP allowlist problem for third-party services.
  * **No More IP Lists**: This feature makes the workaround of maintaining dynamic IP Lists for Tunnel connections obsolete.  
Get started in the Tunnels section of the Zero Trust dashboard with your first [private hostname](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/) or [public hostname](https://edgetunnel-b2h.pages.dev/cloudflare-one/traffic-policies/egress-policies/egress-cloudflared/) route.  
Learn more in our [blog post ↗](https://blog.cloudflare.com/tunnel-hostname-routing/).

Sep 18, 2025
1. ### [Increased vCPU for Workers Builds on paid plans](https://edgetunnel-b2h.pages.dev/changelog/post/2025-09-07-builds-increased-cpu-paid/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
We recently [increased the available disk space](https://edgetunnel-b2h.pages.dev/changelog/2025-08-04-builds-increased-disk-size/) from 8 GB to 20 GB for **all** plans. Building on that improvement, we’re now doubling the CPU power available for paid plans — from 2 vCPU to **4 vCPU**.  
These changes continue our focus on making [Workers Builds](https://edgetunnel-b2h.pages.dev/workers/ci-cd/builds/) faster and more reliable.

| Metric | Free Plan | Paid Plans |
| ------ | --------- | ---------- |
| CPU    | 2 vCPU    | **4 vCPU** |  
#### Performance Improvements

  * **Fast build times**: Even single-threaded workloads benefit from having more vCPUs
  * **2x faster multi-threaded builds**: Tools like [esbuild ↗](https://esbuild.github.io/) and [webpack ↗](https://webpack.js.org/) can now utilize additional cores, delivering near-linear performance scaling  
All other [build limits](https://edgetunnel-b2h.pages.dev/workers/ci-cd/builds/limits-and-pricing/) — including memory, build minutes, and timeout remain unchanged.

Sep 17, 2025
1. ### [Preview URLs now default to opt-in](https://edgetunnel-b2h.pages.dev/changelog/post/2025-09-17-update-preview-url-setting/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
To prevent the accidental exposure of applications, we've updated how [Worker preview URLs](https://edgetunnel-b2h.pages.dev/workers/versions-and-deployments/preview-urls/) (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) are handled. We made this change to ensure preview URLs are only active when intentionally configured, improving the default security posture of your Workers.  
#### One-Time Update for Workers with workers.dev Disabled  
We performed a one-time update to disable preview URLs for existing Workers where the [workers.dev subdomain](https://edgetunnel-b2h.pages.dev/workers/configuration/routing/workers-dev/) was also disabled.  
Because preview URLs were historically enabled by default, users who had intentionally disabled their workers.dev route may not have realized their Worker was still accessible at a separate preview URL. This update was performed to ensure that using a preview URL is always an intentional, opt-in choice.  
If your Worker was affected, its preview URL (`<PREVIEW>-<WORKER_NAME>.<SUBDOMAIN>.workers.dev`) will now direct to an informational page explaining this change.

**How to Re-enable Your Preview URL**  
If your preview URL was disabled, you can re-enable it [via the Cloudflare dashboard](https://edgetunnel-b2h.pages.dev/workers/versions-and-deployments/preview-urls/#toggle-preview-urls-enable-or-disable) by navigating to your Worker's Settings page and toggling on the Preview URL.  
Alternatively, you can use Wrangler by adding the `preview_urls = true` setting to your Wrangler file and redeploying the Worker.

  * [  wrangler.jsonc ](#tab-panel-3545)
  * [  wrangler.toml ](#tab-panel-3546)

**JSONC**  
```jsonc  
{  
  "preview_urls": true  
}  
```

**TOML**  
```toml  
preview_urls = true  
```

**Note:** You can set `preview_urls = true` with any Wrangler version that supports the preview URL flag (v3.91.0+). However, we recommend updating to v4.34.0 or newer, as this version defaults `preview_urls` to false, ensuring preview URLs are always enabled by explicit choice.

Sep 16, 2025
1. ### [Remote bindings GA - Connect to remote resources (D1, KV, R2, etc.) during local development](https://edgetunnel-b2h.pages.dev/changelog/post/2025-09-16-remote-bindings-ga/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
Three months ago [we announced the public beta](https://edgetunnel-b2h.pages.dev/changelog/2025-06-18-remote-bindings-beta/) of [remote bindings](https://edgetunnel-b2h.pages.dev/workers/local-development/#remote-bindings) for local development. Now, we're excited to say that it's available for everyone in Wrangler, Vite, and Vitest without using an experimental flag!  
With remote bindings, you can now connect to deployed resources like [R2 buckets](https://edgetunnel-b2h.pages.dev/r2/) and [D1 databases](https://edgetunnel-b2h.pages.dev/d1/) while running Worker code on your local machine. This means you can test your local code changes against real data and services, without the overhead of deploying for each iteration.  
#### Example configuration  
To enable remote bindings, add `"remote" : true` to each binding that you want to rely on a remote resource running on Cloudflare:

  * [  wrangler.jsonc ](#tab-panel-3547)
  * [  wrangler.toml ](#tab-panel-3548)

**JSONC**  
```jsonc  
{  
  "name": "my-worker",  
  // Set this to today's date  
  "compatibility_date": "2026-07-20",  
  "r2_buckets": [  
    {  
      "bucket_name": "screenshots-bucket",  
      "binding": "screenshots_bucket",  
      "remote": true,  
    },  
  ],  
}  
```

**TOML**  
```toml  
name = "my-worker"  
# Set this to today's date  
compatibility_date = "2026-07-20"  
[[r2_buckets]]  
bucket_name = "screenshots-bucket"  
binding = "screenshots_bucket"  
remote = true  
```  
When remote bindings are configured, your Worker **still executes locally**, but all binding calls are proxied to the deployed resource that runs on Cloudflare's network.

**You can [try out remote bindings](https://edgetunnel-b2h.pages.dev/workers/local-development/#remote-bindings) for local development today with:**

  * [Wrangler v4.37.0](https://edgetunnel-b2h.pages.dev/workers/wrangler/)
  * The [Cloudflare Vite Plugin](https://edgetunnel-b2h.pages.dev/workers/vite-plugin/)
  * The [Cloudflare Vitest Plugin](https://edgetunnel-b2h.pages.dev/workers/testing/vitest-integration/)

Sep 11, 2025
1. ### [D1 automatically retries read-only queries](https://edgetunnel-b2h.pages.dev/changelog/post/2025-09-11-d1-automatic-read-retries/)  
[ D1 ](https://edgetunnel-b2h.pages.dev/d1/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
D1 now detects read-only queries and automatically attempts up to two retries to execute those queries in the event of failures with retryable errors. You can access the number of execution attempts in the returned [response metadata](https://edgetunnel-b2h.pages.dev/d1/worker-api/return-object/#d1result) property `total_attempts`.  
At the moment, only read-only queries are retried, that is, queries containing only the following SQLite keywords: `SELECT`, `EXPLAIN`, `WITH`. Queries containing any [SQLite keyword ↗](https://sqlite.org/lang%5Fkeywords.html) that leads to database writes are not retried.  
The retry success ratio among read-only retryable errors varies from 5% all the way up to 95%, depending on the underlying error and its duration (like network errors or other internal errors).  
The retry success ratio among all retryable errors is lower, indicating that there are write-queries that could be retried. Therefore, we recommend D1 users to continue applying [retries in their own code](https://edgetunnel-b2h.pages.dev/d1/best-practices/retry-queries/) for queries that are not read-only but are idempotent according to the business logic of the application.  
![D1 automatically query retries success ratio](https://edgetunnel-b2h.pages.dev/_astro/d1-auto-retry-success-ratio.yPw8B0tB_1c6euA.webp)  
D1 ensures that any retry attempt does not cause database writes, making the automatic retries safe from side-effects, even if a query causing changes slips through the read-only detection. D1 achieves this by checking for modifications after every query execution, and if any write occurred due to a retry attempt, the query is rolled back.  
The read-only query detection heuristics are simple for now, and there is room for improvement to capture more cases of queries that can be retried, so this is just the beginning.

Sep 11, 2025
1. ### [Worker version rollback limit increased from 10 to 100](https://edgetunnel-b2h.pages.dev/changelog/post/2025-09-11-increased-version-rollback-limit/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
The number of recent versions available for a Worker rollback has been increased from 10 to 100.  
This allows you to:

  * Promote any of the 100 most recent versions to be the active deployment.
  * Split traffic using [gradual deployments](https://edgetunnel-b2h.pages.dev/workers/versions-and-deployments/gradual-deployments/) between your latest code and any of the 100 most recent versions.  
You can do this through the Cloudflare dashboard or with [Wrangler's rollback command](https://edgetunnel-b2h.pages.dev/workers/wrangler/commands/general/#rollback)  
Learn more about [versioned deployments](https://edgetunnel-b2h.pages.dev/workers/versions-and-deployments/) and [rollbacks](https://edgetunnel-b2h.pages.dev/workers/versions-and-deployments/rollbacks/).

Sep 10, 2025
1. ### [Agents SDK v0.1.0 and workers-ai-provider v2.0.0 with AI SDK v5 support](https://edgetunnel-b2h.pages.dev/changelog/post/2025-09-03-agents-sdk-beta-v5/)  
[ Agents ](https://edgetunnel-b2h.pages.dev/agents/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
We've shipped a new release for the [Agents SDK ↗](https://github.com/cloudflare/agents) bringing full compatibility with [AI SDK v5 ↗](https://ai-sdk.dev/docs/introduction) and introducing automatic message migration that handles all legacy formats transparently.  
This release includes improved streaming and tool support, tool confirmation detection (for "human in the loop" systems), enhanced React hooks with automatic tool resolution, improved error handling for streaming responses, and seamless migration utilities that work behind the scenes.  
This makes it ideal for building production AI chat interfaces with Cloudflare Workers AI models, agent workflows, human-in-the-loop systems, or any application requiring reliable message handling across SDK versions — all while maintaining backward compatibility.  
Additionally, we've updated workers-ai-provider v2.0.0, the official provider for Cloudflare Workers AI models, to be compatible with AI SDK v5.  
#### useAgentChat(options)  
Creates a new chat interface with enhanced v5 capabilities.

**TypeScript**  
```ts  
// Basic chat setup  
const { messages, sendMessage, addToolResult } = useAgentChat({  
  agent,  
  experimental_automaticToolResolution: true,  
  tools,  
});  
// With custom tool confirmation  
const chat = useAgentChat({  
  agent,  
  experimental_automaticToolResolution: true,  
  toolsRequiringConfirmation: ["dangerousOperation"],  
});  
```  
#### Automatic Tool Resolution  
Tools are automatically categorized based on their configuration:

**TypeScript**  
```ts  
const tools = {  
  // Auto-executes (has execute function)  
  getLocalTime: {  
    description: "Get current local time",  
    inputSchema: z.object({}),  
    execute: async () => new Date().toLocaleString(),  
  },  
  // Requires confirmation (no execute function)  
  deleteFile: {  
    description: "Delete a file from the system",  
    inputSchema: z.object({  
      filename: z.string(),  
    }),  
  },  
  // Server-executed (no client confirmation)  
  analyzeData: {  
    description: "Analyze dataset on server",  
    inputSchema: z.object({ data: z.array(z.number()) }),  
    serverExecuted: true,  
  },  
} satisfies Record<string, AITool>;  
```  
#### Message Handling  
Send messages using the new v5 format with parts array:

**TypeScript**  
```ts  
// Text message  
sendMessage({  
  role: "user",  
  parts: [{ type: "text", text: "Hello, assistant!" }],  
});  
// Multi-part message with file  
sendMessage({  
  role: "user",  
  parts: [  
    { type: "text", text: "Analyze this image:" },  
    { type: "image", image: imageData },  
  ],  
});  
```  
#### Tool Confirmation Detection  
Simplified logic for detecting pending tool confirmations:

**TypeScript**  
```ts  
const pendingToolCallConfirmation = messages.some((m) =>  
  m.parts?.some(  
    (part) => isToolUIPart(part) && part.state === "input-available",  
  ),  
);  
// Handle tool confirmation  
if (pendingToolCallConfirmation) {  
  await addToolResult({  
    toolCallId: part.toolCallId,  
    tool: getToolName(part),  
    output: "User approved the action",  
  });  
}  
```  
#### Automatic Message Migration  
Seamlessly handle legacy message formats without code changes.

**TypeScript**  
```ts  
// All these formats are automatically converted:  
// Legacy v4 string content  
const legacyMessage = {  
  role: "user",  
  content: "Hello world",  
};  
// Legacy v4 with tool calls  
const legacyWithTools = {  
  role: "assistant",  
  content: "",  
  toolInvocations: [  
    {  
      toolCallId: "123",  
      toolName: "weather",  
      args: { city: "SF" },  
      state: "result",  
      result: "Sunny, 72°F",  
    },  
  ],  
};  
// Automatically becomes v5 format:  
// {  
//   role: "assistant",  
//   parts: [{  
//     type: "tool-call",  
//     toolCallId: "123",  
//     toolName: "weather",  
//     args: { city: "SF" },  
//     state: "result",  
//     result: "Sunny, 72°F"  
//   }]  
// }  
```  
#### Tool Definition Updates  
Migrate tool definitions to use the new `inputSchema` property.

**TypeScript**  
```ts  
// Before (AI SDK v4)  
const tools = {  
  weather: {  
    description: "Get weather information",  
    parameters: z.object({  
      city: z.string(),  
    }),  
    execute: async (args) => {  
      return await getWeather(args.city);  
    },  
  },  
};  
// After (AI SDK v5)  
const tools = {  
  weather: {  
    description: "Get weather information",  
    inputSchema: z.object({  
      city: z.string(),  
    }),  
    execute: async (args) => {  
      return await getWeather(args.city);  
    },  
  },  
};  
```  
#### Cloudflare Workers AI Integration  
Seamless integration with Cloudflare Workers AI models through the updated workers-ai-provider v2.0.0.  
#### Model Setup with Workers AI  
Use Cloudflare Workers AI models directly in your agent workflows:

**TypeScript**  
```ts  
import { createWorkersAI } from "workers-ai-provider";  
import { useAgentChat } from "agents/ai-react";  
// Create Workers AI model (v2.0.0 - same API, enhanced v5 internals)  
const model = createWorkersAI({  
  binding: env.AI,  
})("@cf/meta/llama-3.2-3b-instruct");  
```  
#### Enhanced File and Image Support  
Workers AI models now support v5 file handling with automatic conversion:

**TypeScript**  
```ts  
// Send images and files to Workers AI models  
sendMessage({  
  role: "user",  
  parts: [  
    { type: "text", text: "Analyze this image:" },  
    {  
      type: "file",  
      data: imageBuffer,  
      mediaType: "image/jpeg",  
    },  
  ],  
});  
// Workers AI provider automatically converts to proper format  
```  
#### Streaming with Workers AI  
Enhanced streaming support with automatic warning detection:

**TypeScript**  
```ts  
// Streaming with Workers AI models  
const result = await streamText({  
  model: createWorkersAI({ binding: env.AI })("@cf/meta/llama-3.2-3b-instruct"),  
  messages,  
  onChunk: (chunk) => {  
    // Enhanced streaming with warning handling  
    console.log(chunk);  
  },  
});  
```  
#### Import Updates  
Update your imports to use the new v5 types:

**TypeScript**  
```ts  
// Before (AI SDK v4)  
import type { Message } from "ai";  
import { useChat } from "ai/react";  
// After (AI SDK v5)  
import type { UIMessage } from "ai";  
// or alias for compatibility  
import type { UIMessage as Message } from "ai";  
import { useChat } from "@ai-sdk/react";  
```  
#### Resources

  * [Migration Guide ↗](https://github.com/cloudflare/agents/blob/main/docs/migration-to-ai-sdk-v5.md) \- Comprehensive migration documentation
  * [AI SDK v5 Documentation ↗](https://ai-sdk.dev/docs/migration-guides/migration-guide-5-0) \- Official AI SDK migration guide
  * [An Example PR showing the migration from AI SDK v4 to v5 ↗](https://github.com/cloudflare/agents-starter/pull/105)
  * [GitHub Issues ↗](https://github.com/cloudflare/agents/issues) \- Report bugs or request features  
#### Feedback Welcome  
We'd love your feedback! We're particularly interested in feedback on:

  * **Migration experience** \- How smooth was the upgrade process?
  * **Tool confirmation workflow** \- Does the new automatic detection work as expected?
  * **Message format handling** \- Any edge cases with legacy message conversion?

Sep 10, 2025
1. ### [Built with Cloudflare button](https://edgetunnel-b2h.pages.dev/changelog/post/2025-09-10-built-with-cloudflare-button/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
We've updated our "Built with Cloudflare" button to make it easier to share that you're building on Cloudflare with the world. Embed it in your project's README, blog post, or wherever you want to let people know.  
![Built with Cloudflare](https://workers.cloudflare.com/built-with-cloudflare.svg)  
Check out the [documentation](https://edgetunnel-b2h.pages.dev/workers/platform/built-with-cloudflare) for usage information.

Sep 09, 2025
1. ### [Deploy static sites to Workers without a configuration file](https://edgetunnel-b2h.pages.dev/changelog/post/2025-09-09-interactive-wrangler-assets/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
Deploying static site to Workers is now easier. When you run `wrangler deploy [directory]` or `wrangler deploy --assets [directory]` without an existing [configuration file](https://edgetunnel-b2h.pages.dev/workers/wrangler/configuration/), [Wrangler CLI](https://edgetunnel-b2h.pages.dev/workers/wrangler/) now guides you through the deployment process with interactive prompts.  
#### Before and after

**Before:** Required remembering multiple flags and parameters  
```bash  
wrangler deploy --assets ./dist --compatibility-date 2025-09-09 --name my-project  
```

**After:** Simple directory deployment with guided setup  
```bash  
wrangler deploy dist  
# Interactive prompts handle the rest as shown in the example flow below  
```  
#### What's new

**Interactive prompts for missing configuration:**

  * Wrangler detects when you're trying to deploy a directory of static assets
  * Prompts you to confirm the deployment type
  * Asks for a project name (with smart defaults)
  * Automatically sets the compatibility date to today

**Automatic configuration generation:**

  * Creates a `wrangler.jsonc` file with your deployment settings
  * Stores your choices for future deployments
  * Eliminates the need to remember complex command-line flags  
#### Example workflow  
```bash  
# Deploy your built static site  
wrangler deploy dist  
# Wrangler will prompt:  
✔ It looks like you are trying to deploy a directory of static assets only. Is this correct? … yes  
✔ What do you want to name your project? … my-astro-site  
# Automatically generates a wrangler.jsonc file and adds it to your project:  
{  
  "name": "my-astro-site",  
  "compatibility_date": "2025-09-09",  
  "assets": {  
    "directory": "dist"  
  }  
}  
# Next time you run wrangler deploy, this will use the configuration in your newly generated wrangler.jsonc file  
wrangler deploy  
```  
#### Requirements

  * You must use Wrangler version 4.24.4 or later in order to use this feature

Sep 05, 2025
1. ### [Introducing EmbeddingGemma from Google on Workers AI](https://edgetunnel-b2h.pages.dev/changelog/post/2025-09-05-embeddinggemma/)  
[ Workers AI ](https://edgetunnel-b2h.pages.dev/workers-ai/)  
We're excited to be a launch partner alongside [Google ↗](https://developers.googleblog.com/en/introducing-embeddinggemma/) to bring their newest embedding model, **EmbeddingGemma**, to Workers AI that delivers best-in-class performance for its size, enabling RAG and semantic search use cases.  
[@cf/google/embeddinggemma-300m](https://edgetunnel-b2h.pages.dev/workers-ai/models/embeddinggemma-300m/) is a 300M parameter embedding model from Google, built from Gemma 3 and the same research used to create Gemini models. This multilingual model supports 100+ languages, making it ideal for RAG systems, semantic search, content classification, and clustering tasks.

**Using EmbeddingGemma in AI Search:**Now you can leverage EmbeddingGemma directly through AI Search for your RAG pipelines. EmbeddingGemma's multilingual capabilities make it perfect for global applications that need to understand and retrieve content across different languages with exceptional accuracy.  
To use EmbeddingGemma for your AI Search projects:

  1. Go to **Create** in the [AI Search dashboard ↗](https://dash.cloudflare.com/?to=/:account/ai/ai-search)
  2. Follow the setup flow for your new RAG instance
  3. In the **Generate Index** step, open up **More embedding models** and select `@cf/google/embeddinggemma-300m` as your embedding model
  4. Complete the setup to create an AI Search  
Try it out and let us know what you think!

Sep 04, 2025
1. ### [Increased static asset limits for Workers](https://edgetunnel-b2h.pages.dev/changelog/post/2025-09-02-increased-static-asset-limits/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)[ Workers for Platforms ](https://edgetunnel-b2h.pages.dev/cloudflare-for-platforms/workers-for-platforms/)  
You can now upload up to **100,000 static assets** per Worker version

  * Paid and Workers for Platforms users can now upload up to **100,000 static assets** per Worker version, a 5x increase from the previous limit of 20,000.
  * Customers on the free plan still have the same limit as before — 20,000 static assets per version of your Worker
  * The individual file size limit of 25 MiB remains unchanged for all customers.  
This increase allows you to build larger applications with more static assets without hitting limits.  
#### Wrangler  
To take advantage of the increased limits, you must use **Wrangler version 4.34.0 or higher**. Earlier versions of Wrangler will continue to enforce the previous 20,000 file limit.  
#### Learn more  
For more information about Workers static assets, see the [Static Assets documentation](https://edgetunnel-b2h.pages.dev/workers/static-assets/) and [Platform Limits](https://edgetunnel-b2h.pages.dev/workers/platform/limits/#static-assets).

Sep 04, 2025
1. ### [A new, simpler REST API for Cloudflare Workers (Beta)](https://edgetunnel-b2h.pages.dev/changelog/post/2025-09-03-new-workers-api/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
You can now manage [**Workers**](https://edgetunnel-b2h.pages.dev/api/resources/workers/subresources/beta/subresources/workers/methods/create/), [**Versions**](https://edgetunnel-b2h.pages.dev/api/resources/workers/subresources/beta/subresources/workers/models/worker/#%28schema%29), and [**Deployments**](https://edgetunnel-b2h.pages.dev/api/resources/workers/subresources/scripts/subresources/content/methods/update/) as separate resources with a new, resource-oriented API (Beta).  
This new API is supported in the [Cloudflare Terraform provider ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) and the [Cloudflare Typescript SDK ↗](https://github.com/cloudflare/cloudflare-typescript), allowing platform teams to manage a Worker's infrastructure in Terraform, while development teams handle code deployments from a separate repository or workflow. We also designed this API with AI agents in mind, as a clear, predictable structure is essential for them to reliably build, test, and deploy applications.  
#### Try it out

  * [**New beta API endpoints**](https://edgetunnel-b2h.pages.dev/api/resources/workers/subresources/beta/)
  * [**Cloudflare TypeScript SDK v5.0.0** ↗](https://github.com/cloudflare/cloudflare-typescript)
  * [**Cloudflare Go SDK v6.0.0** ↗](https://github.com/cloudflare/cloudflare-go)
  * [**Terraform provider v5.9.0** ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs): [cloudflare\_worker ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker) , [cloudflare\_worker\_version ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/worker%5Fversion), and [cloudflare\_workers\_deployments ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/workers%5Fdeployment) resources.
  * See full examples in our [Infrastructure as Code (IaC) guide](https://edgetunnel-b2h.pages.dev/workers/platform/infrastructure-as-code)  
#### Before: Eight+ endpoints with mixed responsibilities  
![Before](https://edgetunnel-b2h.pages.dev/_astro/api-before.VkE1i-Rj_eezro.webp)  
The existing API was originally designed for simple, one-shot script uploads:  
```sh  
curl -X PUT "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/workers/scripts/$SCRIPT_NAME" \
    -H "X-Auth-Email: $CLOUDFLARE_EMAIL" \
    -H "X-Auth-Key: $CLOUDFLARE_API_KEY" \
    -H "Content-Type: multipart/form-data" \
    -F 'metadata={  
      "main_module": "worker.js",  
      "compatibility_date": "$today$"  
    }' \
    -F "worker.js=@worker.js;type=application/javascript+module"  
```  
This API worked for creating a basic Worker, uploading all of its code, and deploying it immediately — but came with challenges:

  * **A Worker couldn't exist without code**: To create a Worker, you had to upload its code in the same API request. This meant platform teams couldn't provision Workers with the proper settings, and then hand them off to development teams to deploy the actual code.
  * **Several endpoints implicitly created deployments**: Simple updates like adding a secret or changing a script's content would implicitly create a new version and immediately deploy it.
  * **Updating a setting was confusing**: Configuration was scattered across eight endpoints with overlapping responsibilities. This ambiguity made it difficult for human developers (and even more so for AI agents) to reliably update a Worker via API.
  * **Scripts used names as primary identifiers**: This meant simple renames could turn into a risky migration, requiring you to create a brand new Worker and update every reference. If you were using Terraform, this could inadvertently destroy your Worker altogether.  
#### After: Three resources with clear boundaries  
![After](https://edgetunnel-b2h.pages.dev/_astro/api-after.J8u2vIcT_ZesBmg.webp)  
All endpoints now use simple JSON payloads, with script content embedded as `base64`\-encoded strings -- a more consistent and reliable approach than the previous `multipart/form-data` format.

  * **Worker**: The parent resource representing your application. It has a stable UUID and holds persistent settings like `name`, `tags`, and `logpush`. You can now create a Worker to establish its identity and settings **before** any code is uploaded.
  * **Version**: An immutable snapshot of your code and its specific configuration, like bindings and `compatibility_date`. Creating a new version is a safe action that doesn't affect live traffic.
  * **Deployment**: An explicit action that directs traffic to a specific version.  
Note  
[Workers](https://edgetunnel-b2h.pages.dev/api/resources/workers/subresources/beta/subresources/workers/) and [Versions](https://edgetunnel-b2h.pages.dev/api/resources/workers/subresources/beta/subresources/workers/subresources/versions/) use the new `/workers/` beta endpoints, while [Deployments](https://edgetunnel-b2h.pages.dev/api/resources/workers/subresources/scripts/subresources/deployments/) remain on the existing `/scripts/` endpoint. Pair the new endpoints with the existing Deployment API for a complete workflow.  
#### Why this matters  
#### You can now create Workers before uploading code  
Workers are now standalone resources that can be created and configured without any code. Platform teams can provision Workers with the right settings, then hand them off to development teams for implementation.  
#### Example: Typescript SDK

**TypeScript**  
```ts  
// Step 1: Platform team creates the Worker resource (no code needed)  
const worker = await client.workers.beta.workers.create({  
  name: "payment-service",  
  account_id: "...",  
  observability: {  
    enabled: true,  
  },  
});  
// Step 2: Development team adds code and creates a version later  
const version = await client.workers.beta.workers.versions.create(worker.id, {  
  account_id: "...",  
  main_module: "worker.js",  
  compatibility_date: "$today",  
  bindings: [ /*...*/ ],  
  modules: [  
    {  
      name: "worker.js",  
      content_type: "application/javascript+module",  
      content_base64: Buffer.from(scriptContent).toString("base64"),  
    },  
  ],  
});  
// Step 3: Deploy explicitly when ready  
const deployment = await client.workers.scripts.deployments.create(worker.name, {  
  account_id: "...",  
  strategy: "percentage",  
  versions: [  
    {  
      percentage: 100,  
      version_id: version.id,  
    },  
  ],  
});  
```  
#### Example: Terraform  
If you use Terraform, you can now declare the Worker in your Terraform configuration and manage configuration outside of Terraform in your Worker's [wrangler.jsonc file](https://edgetunnel-b2h.pages.dev/workers/wrangler/configuration/) and deploy code changes using [Wrangler](https://edgetunnel-b2h.pages.dev/workers/wrangler/).  
```tf  
resource "cloudflare_worker" "my_worker" {  
  account_id = "..."  
  name = "my-important-service"  
}  
# Manage Versions and Deployments here or outside of Terraform  
# resource "cloudflare_worker_version" "my_worker_version" {}  
# resource "cloudflare_workers_deployment" "my_worker_deployment" {}  
```  
#### Deployments are always explicit, never implicit  
Creating a version and deploying it are now always explicit, separate actions - never implicit side effects. To update version-specific settings (like bindings), you create a new version with those changes. The existing deployed version remains unchanged until you explicitly deploy the new one.  
```sh  
# Step 1: Create a new version with updated settings (doesn't affect live traffic)  
POST /workers/workers/{id}/versions  
{  
  "compatibility_date": "$today",  
  "bindings": [  
    {  
      "name": "MY_NEW_ENV_VAR",  
      "text": "new_value",  
      "type": "plain_text"  
    }  
  ],  
  "modules": [...]  
}  
# Step 2: Explicitly deploy when ready (now affects live traffic)  
POST /workers/scripts/{script_name}/deployments  
{  
  "strategy": "percentage",  
  "versions": [  
    {  
      "percentage": 100,  
      "version_id": "new_version_id"  
    }  
  ]  
}  
```  
#### Settings are clearly organized by scope  
Configuration is now logically divided: [**Worker settings**](https://edgetunnel-b2h.pages.dev/api/resources/workers/subresources/beta/subresources/workers/) (like `name` and `tags`) persist across all versions, while [**Version settings**](https://edgetunnel-b2h.pages.dev/api/resources/workers/subresources/beta/subresources/workers/subresources/versions/) (like `bindings` and `compatibility_date`) are specific to each code snapshot.  
```sh  
# Worker settings (the parent resource)  
PUT /workers/workers/{id}  
{  
  "name": "payment-service",  
  "tags": ["production"],  
  "logpush": true,  
}  
```  
```sh  
# Version settings (the "code")  
POST /workers/workers/{id}/versions  
{  
  "compatibility_date": "$today",  
  "bindings": [...],  
  "modules": [...]  
}  
```  
#### `/workers` API endpoints now support UUIDs (in addition to names)  
The `/workers/workers/` path now supports addressing a Worker by both its immutable UUID and its mutable name.  
```sh  
# Both work for the same Worker  
GET /workers/workers/29494978e03748669e8effb243cf2515  # UUID (stable for automation)  
GET /workers/workers/payment-service                  # Name (convenient for humans)  
```  
This dual approach means:

  * Developers can use readable names for debugging.
  * Automation can rely on stable UUIDs to prevent errors when Workers are renamed.
  * Terraform can rename Workers without destroying and recreating them.  
#### Learn more

  * [Infrastructure as Code (IaC) guide](https://edgetunnel-b2h.pages.dev/workers/platform/infrastructure-as-code)
  * [API documentation](https://edgetunnel-b2h.pages.dev/api/resources/workers/subresources/beta/)
  * [Versions and Deployments overview](https://edgetunnel-b2h.pages.dev/workers/versions-and-deployments/)  
#### Technical notes

  * The pre-existing Workers REST API remains fully supported. Once the new API exits beta, we'll provide a migration timeline with ample notice and comprehensive migration guides.
  * Existing Terraform resources and SDK methods will continue to be fully supported through the current major version.
  * While the Deployments API currently remains on the `/scripts/` endpoint, we plan to introduce a new Deployments endpoint under `/workers/` to match the new API structure.

Sep 02, 2025
1. ### [Cloudflare Tunnel and Networks API will no longer return deleted resources by default starting December 1, 2025](https://edgetunnel-b2h.pages.dev/changelog/post/2025-09-02-tunnel-networks-list-endpoints-new-default/)  
[ Cloudflare Tunnel ](https://edgetunnel-b2h.pages.dev/tunnel/)[ Cloudflare Tunnel for SASE ](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/)  
Starting **December 1, 2025**, list endpoints for the [Cloudflare Tunnel API](https://edgetunnel-b2h.pages.dev/api/resources/zero%5Ftrust/subresources/tunnels/) and [Zero Trust Networks API](https://edgetunnel-b2h.pages.dev/api/resources/zero%5Ftrust/subresources/networks/) will no longer return deleted tunnels, routes, subnets and virtual networks by default. This change makes the API behavior more intuitive by only returning active resources unless otherwise specified.  
No action is required if you already explicitly set `is_deleted=false` or if you only need to list active resources.  
This change affects the following API endpoints:

  * List all tunnels: [GET /accounts/{account\_id}/tunnels](https://edgetunnel-b2h.pages.dev/api/resources/zero%5Ftrust/subresources/tunnels/methods/list/)
  * List [Cloudflare Tunnels](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/): [GET /accounts/{account\_id}/cfd\_tunnel](https://edgetunnel-b2h.pages.dev/api/resources/zero%5Ftrust/subresources/tunnels/subresources/cloudflared/methods/list/)
  * List [WARP Connector](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-mesh/) tunnels: [GET /accounts/{account\_id}/warp\_connector](https://edgetunnel-b2h.pages.dev/api/resources/zero%5Ftrust/subresources/tunnels/subresources/warp%5Fconnector/methods/list/)
  * List tunnel routes: [GET /accounts/{account\_id}/teamnet/routes](https://edgetunnel-b2h.pages.dev/api/resources/zero%5Ftrust/subresources/networks/subresources/routes/methods/list/)
  * List subnets: [GET /accounts/{account\_id}/zerotrust/subnets](https://edgetunnel-b2h.pages.dev/api/resources/zero%5Ftrust/subresources/networks/subresources/subnets/methods/list/)
  * List virtual networks: [GET /accounts/{account\_id}/teamnet/virtual\_networks](https://edgetunnel-b2h.pages.dev/api/resources/zero%5Ftrust/subresources/networks/subresources/virtual%5Fnetworks/methods/list/)  
#### What is changing?  
The default behavior of the `is_deleted` query parameter will be updated.

| Scenario                         | Previous behavior (before December 1, 2025)                                | New behavior (from December 1, 2025)                                  |
| -------------------------------- | -------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| is\_deleted parameter is omitted | Returns **active & deleted** tunnels, routes, subnets and virtual networks | Returns **only active** tunnels, routes, subnets and virtual networks |  
#### Action required  
If you need to retrieve deleted (or all) resources, please update your API calls to explicitly include the `is_deleted` parameter before **December 1, 2025**.  
To get a list of only deleted resources, you must now explicitly add the `is_deleted=true` query parameter to your request:  
```bash  
# Example: Get ONLY deleted Tunnels  
curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/tunnels?is_deleted=true" \
     -H "Authorization: Bearer $API_TOKEN"  
# Example: Get ONLY deleted Virtual Networks  
curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/teamnet/virtual_networks?is_deleted=true" \
     -H "Authorization: Bearer $API_TOKEN"  
```  
Following this change, retrieving a complete list of both active and deleted resources will require two separate API calls: one to get active items (by omitting the parameter or using `is_deleted=false`) and one to get deleted items (`is_deleted=true`).  
#### Why we’re making this change  
This update is based on user feedback and aims to:

  * **Create a more intuitive default:** Aligning with common API design principles where list operations return only active resources by default.
  * **Reduce unexpected results:** Prevents users from accidentally operating on deleted resources that were returned unexpectedly.
  * **Improve performance:** For most users, the default query result will now be smaller and more relevant.  
To learn more, please visit the [Cloudflare Tunnel API](https://edgetunnel-b2h.pages.dev/api/resources/zero%5Ftrust/subresources/tunnels/) and [Zero Trust Networks API](https://edgetunnel-b2h.pages.dev/api/resources/zero%5Ftrust/subresources/networks/) documentation.

Aug 29, 2025
1. ### [Terraform v5.9 now available](https://edgetunnel-b2h.pages.dev/changelog/post/2025-08-29-terrform-v59-provider/)  
[ Cloudflare Fundamentals ](https://edgetunnel-b2h.pages.dev/fundamentals/)[ Terraform ](https://edgetunnel-b2h.pages.dev/terraform/)  
Earlier this year, we announced the launch of the new [Terraform v5 Provider](https://edgetunnel-b2h.pages.dev/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues ↗](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a 2 week cadence to ensure its stability and reliability, including the v5.9 release. We have also pivoted from an issue-to-issue approach to a resource-per-resource approach - we will be focusing on specific resources for every release, stabilizing the release, and closing all associated bugs with that resource before moving onto resolving migration issues.  
Thank you for continuing to raise issues. We triage them weekly and they help make our products stronger.  
This release includes a new resource, `cloudflare_snippet`, which replaces `cloudflare_snippets`. `cloudflare_snippet` is now considered deprecated but can still be used. Please utilize `cloudflare_snippet` as soon as possible.  
#### Changes

  * Resources stabilized:  
    * `cloudflare_zone_setting`
    * `cloudflare_worker_script`
    * `cloudflare_worker_route`
    * `tiered_cache`
  * **NEW** resource `cloudflare_snippet` which should be used in place of `cloudflare_snippets`. `cloudflare_snippets` is now deprecated. This enables the management of Cloudflare's snippet functionality through Terraform.
  * DNS Record Improvements: Enhanced handling of DNS record drift detection
  * Load Balancer Fixes: Resolved `created_on` field inconsistencies and improved pool configuration handling
  * Bot Management: Enhanced auto-update model state consistency and fight mode configurations
  * Other bug fixes  
For a more detailed look at all of the changes, refer to the [changelog ↗](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.9.0) in GitHub.  
#### Issues Closed

  * [#5921: In cloudflare\_ruleset removing an existing rule causes recreation of later rules ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5921)
  * [#5904: cloudflare\_zero\_trust\_access\_application is not idempotent ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5904)
  * [#5898: (cloudflare\_workers\_script) Durable Object migrations not applied ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5898)
  * [#5892: cloudflare\_workers\_script secret\_text environment variable gets replaced on every deploy ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5892)
  * [#5891: cloudflare\_zone suddenly started showing drift ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5891)
  * [#5882: cloudflare\_zero\_trust\_list always marked for change due to read only attributes ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5882)
  * [#5879: cloudflare\_zero\_trust\_gateway\_certificate unable to manage resource (cant mark as active/inactive) ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5879)
  * [#5858: cloudflare\_dns\_records is always updated in-place ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5858)
  * [#5839: Recurring change on cloudflare\_zero\_trust\_gateway\_policy after upgrade to V5 provider & also setting expiration fails ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5839)
  * [#5811: Reusable policies are imported as inline type for cloudflare\_zero\_trust\_access\_application ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5811)
  * [#5795: cloudflare\_zone\_setting inconsistent value of "editable" upon apply ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5795)
  * [#5789: Pagination issue fetching all policies in "cloudflare\_zero\_trust\_access\_policies" data source ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5789)
  * [#5770: cloudflare\_zero\_trust\_access\_application type warp diff on every apply ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5770)
  * [#5765: V5 / cloudflare\_zone\_dnssec fails with HTTP/400 "Malformed request body" ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5765)
  * [#5755: Unable to manage Cloudflare managed WAF rules via Terraform ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5755)
  * [#5738: v4 to v5 upgrade failing Error: no schema available AND Unable to Read Previously Saved State for UpgradeResourceState ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5738)
  * [#5727: cloudflare\_ruleset http\_request\_cache\_settings bypass mismatch between dashboard and terraform ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5727)
  * [#5700: cloudflare\_account\_member invalid type 'string' for field 'roles' ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5700)  
If you have an unaddressed issue with the provider, we encourage you to check the [open issues ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues) and open a new issue if one does not already exist for what you are experiencing.  
#### Upgrading  
We suggest holding off on migration to v5 while we work on stabilization. This help will you avoid any blocking issues while the Terraform resources are actively being stabilized.  
If you'd like more information on migrating from v4 to v5, please make use of the [migration guide ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade). We have provided automated migration scripts using Grit which simplify the transition. These do not support implementations which use Terraform modules, so customers making use of modules need to migrate manually. Please make use of `terraform plan` to test your changes before applying, and let us know if you encounter any additional issues by reporting to our [GitHub repository ↗](https://github.com/cloudflare/terraform-provider-cloudflare).  
#### For more info

  * [Terraform provider ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
  * [Documentation on using Terraform with Cloudflare](https://edgetunnel-b2h.pages.dev/terraform/)
  * [GitHub Repository ↗](https://github.com/cloudflare/terraform-provider-cloudflare)

Aug 27, 2025
1. ### [Deepgram and Leonardo partner models now available on Workers AI](https://edgetunnel-b2h.pages.dev/changelog/post/2025-08-27-partner-models/)  
[ Workers AI ](https://edgetunnel-b2h.pages.dev/workers-ai/)  
New state-of-the-art models have landed on Workers AI! This time, we're introducing new **partner models** trained by our friends at [Deepgram ↗](https://deepgram.com) and [Leonardo ↗](https://leonardo.ai), hosted on Workers AI infrastructure.  
As well, we're introuding a new turn detection model that enables you to detect when someone is done speaking — useful for building voice agents!  
Read the [blog ↗](https://blog.cloudflare.com/workers-ai-partner-models) for more details and check out some of the new models on our platform:

  * [@cf/deepgram/aura-1](https://edgetunnel-b2h.pages.dev/workers-ai/models/aura-1) is a text-to-speech model that allows you to input text and have it come to life in a customizable voice
  * [@cf/deepgram/nova-3](https://edgetunnel-b2h.pages.dev/workers-ai/models/nova-3) is speech-to-text model that transcribes multilingual audio at a blazingly fast speed
  * [@cf/pipecat-ai/smart-turn-v2](https://edgetunnel-b2h.pages.dev/workers-ai/models/smart-turn-v2) helps you detect when someone is done speaking
  * [@cf/leonardo/lucid-origin](https://edgetunnel-b2h.pages.dev/workers-ai/models/lucid-origin) is a text-to-image model that generates images with sharp graphic design, stunning full-HD renders, or highly specific creative direction
  * [@cf/leonardo/phoenix-1.0](https://edgetunnel-b2h.pages.dev/workers-ai/models/phoenix-1.0) is a text-to-image model with exceptional prompt adherence and coherent text  
You can filter out new partner models with the `Partner` capability on our [Models](https://edgetunnel-b2h.pages.dev/workers-ai/models) page.  
As well, we're introducing WebSocket support for some of our audio models, which you can filter though the `Realtime` capability on our [Models](https://edgetunnel-b2h.pages.dev/workers-ai/models) page. WebSockets allows you to create a bi-directional connection to our inference server with low latency — perfect for those that are building voice agents.  
An example python snippet on how to use WebSockets with our new Aura model:  
```plaintext  
import json  
import os  
import asyncio  
import websockets  
uri = f"wss://api.cloudflare.com/client/v4/accounts/{ACCOUNT_ID}/ai/run/@cf/deepgram/aura-1"  
input = [  
    "Line one, out of three lines that will be provided to the aura model.",  
    "Line two, out of three lines that will be provided to the aura model.",  
    "Line three, out of three lines that will be provided to the aura model. This is a last line.",  
]  
async def text_to_speech():  
    async with websockets.connect(uri, additional_headers={"Authorization": os.getenv("CF_TOKEN")}) as websocket:  
        print("connection established")  
        for line in input:  
            print(f"sending `{line}`")  
            await websocket.send(json.dumps({"type": "Speak", "text": line}))  
            print("line was sent, flushing")  
            await websocket.send(json.dumps({"type": "Flush"}))  
            print("flushed, recving")  
            resp = await websocket.recv()  
            print(f"response received {resp}")  
if __name__ == "__main__":  
    asyncio.run(text_to_speech())  
```

Aug 26, 2025
1. ### [List all vectors in a Vectorize index with the new list-vectors operation](https://edgetunnel-b2h.pages.dev/changelog/post/2025-08-26-vectorize-list-vectors/)  
[ Vectorize ](https://edgetunnel-b2h.pages.dev/vectorize/)  
You can now list all vector identifiers in a Vectorize index using the new `list-vectors` operation. This enables bulk operations, auditing, and data migration workflows through paginated requests that maintain snapshot consistency.  
The operation is available via Wrangler CLI and REST API. Refer to the [list-vectors best practices guide](https://edgetunnel-b2h.pages.dev/vectorize/best-practices/list-vectors/) for detailed usage guidance.

Aug 25, 2025
1. ### [Manage and deploy your AI provider keys through Bring Your Own Key (BYOK) with AI Gateway, now powered by Cloudflare Secrets Store](https://edgetunnel-b2h.pages.dev/changelog/post/2025-08-25-secrets-store-ai-gateway/)  
[ Secrets Store ](https://edgetunnel-b2h.pages.dev/secrets-store/)[ AI Gateway ](https://edgetunnel-b2h.pages.dev/ai-gateway/)[ SSL/TLS ](https://edgetunnel-b2h.pages.dev/ssl/)  
Cloudflare Secrets Store is now integrated with AI Gateway, allowing you to store, manage, and deploy your AI provider keys in a secure and seamless configuration through [Bring Your Own Key ↗](https://edgetunnel-b2h.pages.dev/ai-gateway/configuration/bring-your-own-keys/). Instead of passing your AI provider keys directly in every request header, you can centrally manage each key with Secrets Store and deploy in your gateway configuration using only a reference, rather than passing the value in plain text.  
You can now create a secret directly from your AI Gateway [in the dashboard ↗](http://dash.cloudflare.com/?to=/:account/ai-gateway) by navigating into your gateway -> **Provider Keys** \-> **Add**.  
![Import repo or choose template](https://edgetunnel-b2h.pages.dev/_astro/add-secret-ai-gateway.B-SIPr6s_jJjDD.webp)  
You can also create your secret with the newly available **ai\_gateway** scope via [wrangler ↗](https://edgetunnel-b2h.pages.dev/workers/wrangler/commands/), the [Secrets Store dashboard ↗](http://dash.cloudflare.com/?to=/:account/secrets-store), or the [API ↗](https://edgetunnel-b2h.pages.dev/api/resources/secrets%5Fstore/).  
Then, pass the key in the request header using its Secrets Store reference:  
```bash  
curl -X POST https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthropic/v1/messages \
 --header 'cf-aig-authorization: ANTHROPIC_KEY_1 \
 --header 'anthropic-version: 2023-06-01' \
 --header 'Content-Type: application/json' \
 --data  '{"model": "claude-3-opus-20240229", "messages": [{"role": "user", "content": "What is Cloudflare?"}]}'  
```  
Or, using Javascript:  
```plaintext  
import Anthropic from '@anthropic-ai/sdk';  
const anthropic = new Anthropic({  
 apiKey: "ANTHROPIC_KEY_1",  
 baseURL: "https://gateway.ai.cloudflare.com/v1/<ACCOUNT_ID>/my-gateway/anthropic",  
});  
const message = await anthropic.messages.create({  
 model: 'claude-3-opus-20240229',  
 messages: [{role: "user", content: "What is Cloudflare?"}],  
 max_tokens: 1024  
});  
```  
For more information, check out the [blog ↗](https://blog.cloudflare.com/ai-gateway-aug-2025-refresh)!

Aug 25, 2025
1. ### [Content type returned in Workers Assets for Javascript files is now \`text/javascript\`](https://edgetunnel-b2h.pages.dev/changelog/post/2025-08-25-workers-assets-javascript-content-type/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
JavaScript asset responses have been updated to use the `text/javascript` Content-Type header instead of `application/javascript`. While both MIME types are widely supported by browsers, the HTML Living Standard explicitly recommends `text/javascript` as the preferred type going forward.  
This change improves:

  * Standards alignment: Ensures consistency with the HTML spec and modern web platform guidance.
  * Interoperability: Some developer tools, validators, and proxies expect text/javascript and may warn or behave inconsistently with application/javascript.
  * Future-proofing: By following the spec-preferred MIME type, we reduce the risk of deprecation warnings or unexpected behavior in evolving browser environments.
  * Consistency: Most frameworks, CDNs, and hosting providers now default to text/javascript, so this change matches common ecosystem practice.  
Because all major browsers accept both MIME types, this update is backwards compatible and should not cause breakage.  
Users will see this change on the next deployment of their assets.

Aug 22, 2025
1. ### [Workers KV completes hybrid storage provider rollout for improved performance, fault-tolerance](https://edgetunnel-b2h.pages.dev/changelog/post/2025-08-22-kv-performance-improvements/)  
[ KV ](https://edgetunnel-b2h.pages.dev/kv/)  
Workers KV has completed rolling out performance improvements across all KV namespaces, providing a significant latency reduction on read operations for all KV users. This is due to architectural changes to KV's underlying storage infrastructure, which introduces a new metadata later and substantially improves redundancy.  
![Workers KV latency improvements showing P95 and P99 performance gains in Europe, Asia, Africa and Middle East regions as measured within KV's internal storage gateway worker.](https://edgetunnel-b2h.pages.dev/_astro/kv-hybrid-providers-performance-improvements.D6MBO22S_2ok8qE.webp)  
#### Performance improvements  
The new hybrid architecture delivers substantial latency reductions throughout Europe, Asia, Middle East, Africa regions. Over the past 2 weeks, we have observed the following:

  * **p95 latency**: Reduced from \~150ms to \~50ms (67% decrease)
  * **p99 latency**: Reduced from \~350ms to \~250ms (29% decrease)

Aug 22, 2025
1. ### [Build durable multi-step applications in Python with Workflows (now in beta)](https://edgetunnel-b2h.pages.dev/changelog/post/2025-08-22-workflows-python-beta/)  
[ Workflows ](https://edgetunnel-b2h.pages.dev/workflows/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
You can now build [Workflows](https://edgetunnel-b2h.pages.dev/workflows/) using Python. With Python Workflows, you get automatic retries, state persistence, and the ability to run multi-step operations that can span minutes, hours, or weeks using Python’s familiar syntax and the [Python Workers](https://edgetunnel-b2h.pages.dev/workers/languages/python/) runtime.  
Python Workflows use the same step-based execution model as JavaScript Workflows, but with Python syntax and access to Python’s ecosystem. Python Workflows also enable [DAG (Directed Acyclic Graph) workflows](https://edgetunnel-b2h.pages.dev/workflows/python/dag/), where you can define complex dependencies between steps using the depends parameter.  
Here’s a simple example:

**Python**  
```python  
from workers import Response, WorkflowEntrypoint  
class PythonWorkflowStarter(WorkflowEntrypoint):  
    async def run(self, event, step):  
        @step.do("my first step")  
        async def my_first_step():  
            # do some work  
            return "Hello Python!"  
        await my_first_step()  
        await step.sleep("my-sleep-step", "10 seconds")  
        @step.do("my second step")  
        async def my_second_step():  
            # do some more work  
            return "Hello again!"  
        await my_second_step()  
class Default(WorkerEntrypoint):  
    async def fetch(self, request):  
        await self.env.MY_WORKFLOW.create()  
        return Response("Hello Workflow creation!")  
```  
Note  
Python Workflows requires a `compatibility_date = "2025-08-01"`, or lower, in your wrangler toml file.  
Python Workflows support the same core capabilities as JavaScript Workflows, including sleep scheduling, event-driven workflows, and built-in error handling with configurable retry policies.  
To learn more and get started, refer to [Python Workflows documentation](https://edgetunnel-b2h.pages.dev/workflows/python/).

Aug 21, 2025
1. ### [New getByName() API to access Durable Objects](https://edgetunnel-b2h.pages.dev/changelog/post/2025-08-21-durable-objects-get-by-name/)  
[ Durable Objects ](https://edgetunnel-b2h.pages.dev/durable-objects/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
You can now create a client (a [Durable Object stub](https://edgetunnel-b2h.pages.dev/durable-objects/api/stub/)) to a Durable Object with the new `getByName` method, removing the need to convert Durable Object names to IDs and then create a stub.

**JavaScript**  
```js  
// Before: (1) translate name to ID then (2) get a client  
const objectId = env.MY_DURABLE_OBJECT.idFromName("foo"); // or .newUniqueId()  
const stub = env.MY_DURABLE_OBJECT.get(objectId);  
// Now: retrieve client to Durable Object directly via its name  
const stub = env.MY_DURABLE_OBJECT.getByName("foo");  
// Use client to send request to the remote Durable Object  
const rpcResponse = await stub.sayHello();  
```  
Each Durable Object has a globally-unique name, which allows you to send requests to a specific object from anywhere in the world. Thus, a Durable Object can be used to coordinate between multiple clients who need to work together. You can have billions of Durable Objects, providing isolation between application tenants.  
To learn more, visit the Durable Objects [API Documentation](https://edgetunnel-b2h.pages.dev/durable-objects/api/namespace/#getbyname) or the [getting started guide](https://edgetunnel-b2h.pages.dev/durable-objects/get-started/).

Aug 19, 2025
1. ### [Subscribe to events from Cloudflare services with Queues](https://edgetunnel-b2h.pages.dev/changelog/post/2025-08-19-event-subscriptions/)  
[ Queues ](https://edgetunnel-b2h.pages.dev/queues/)  
You can now subscribe to events from other Cloudflare services (for example, [Workers KV](https://edgetunnel-b2h.pages.dev/kv/), [Workers AI](https://edgetunnel-b2h.pages.dev/workers-ai), [Workers](https://edgetunnel-b2h.pages.dev/workers)) and consume those events via [Queues](https://edgetunnel-b2h.pages.dev/queues/), allowing you to build custom workflows, integrations, and logic in response to account activity.  
![Event subscriptions architecture](https://edgetunnel-b2h.pages.dev/_astro/queues-event-subscriptions.3aVidnXJ_Z2p3fRA.webp)  
Event subscriptions allow you to receive messages when events occur across your Cloudflare account. Cloudflare products can publish structured events to a queue, which you can then consume with [Workers](https://edgetunnel-b2h.pages.dev/workers/) or [pull via HTTP from anywhere](https://edgetunnel-b2h.pages.dev/queues/configuration/pull-consumers/).  
To create a subscription, use the dashboard or [Wrangler](https://edgetunnel-b2h.pages.dev/workers/wrangler/commands/queues/#queues-subscription-create):  
```bash  
npx wrangler queues subscription create my-queue --source r2 --events bucket.created  
```  
An event is a structured record of something happening in your Cloudflare account – like a Workers AI batch request being queued, a Worker build completing, or an R2 bucket being created. Events follow a consistent structure:

**Example R2 bucket created event**  
```json  
{  
  "type": "cf.r2.bucket.created",  
  "source": {  
    "type": "r2"  
  },  
  "payload": {  
    "name": "my-bucket",  
    "location": "WNAM"  
  },  
  "metadata": {  
    "accountId": "f9f79265f388666de8122cfb508d7776",  
    "eventTimestamp": "2025-07-28T10:30:00Z"  
  }  
}  
```  
Current [event sources](https://edgetunnel-b2h.pages.dev/queues/event-subscriptions/events-schemas/) include [R2](https://edgetunnel-b2h.pages.dev/r2/), [Workers KV](https://edgetunnel-b2h.pages.dev/kv/), [Workers AI](https://edgetunnel-b2h.pages.dev/workers-ai/), [Workers Builds](https://edgetunnel-b2h.pages.dev/workers/ci-cd/builds/), [Vectorize](https://edgetunnel-b2h.pages.dev/vectorize/), [Super Slurper](https://edgetunnel-b2h.pages.dev/r2/data-migration/super-slurper/), and [Workflows](https://edgetunnel-b2h.pages.dev/workflows/). More sources and events are on the way.  
For more information on event subscriptions, available events, and how to get started, refer to our [documentation](https://edgetunnel-b2h.pages.dev/queues/event-subscriptions/).

Aug 19, 2025
1. ### [Easier debugging in Workers with improved Wrangler error screen](https://edgetunnel-b2h.pages.dev/changelog/post/2025-08-19-improved-wrangler-error-screen/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
Wrangler's error screen has received several improvements to enhance your debugging experience!  
The error screen now features a refreshed design thanks to [youch ↗](https://www.npmjs.com/package/youch), with support for both light and dark themes, improved source map resolution logic that handles missing source files more reliably, and better error cause display.

| Before                                                                                               | After (Light)                                                                                                         | After (Dark)                                                                                                       |
| ---------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| ![Old error screen](https://edgetunnel-b2h.pages.dev/_astro/old-error-screen.yurLWiKb_Z1vn3jq.webp) | ![New light theme error screen](https://edgetunnel-b2h.pages.dev/_astro/new-error-screen-light.CcroERTP_2f4pOC.webp) | ![New dark theme error screen](https://edgetunnel-b2h.pages.dev/_astro/new-error-screen-dark.BIDA2RGg_Q0JqP.webp) |  
Try it out now with `npx wrangler@latest dev` in your Workers project.

Aug 15, 2025
1. ### [Terraform v5.8.4 now available](https://edgetunnel-b2h.pages.dev/changelog/post/2025-08-15-terraform-v584-provider/)  
[ Cloudflare Fundamentals ](https://edgetunnel-b2h.pages.dev/fundamentals/)[ Terraform ](https://edgetunnel-b2h.pages.dev/terraform/)  
Earlier this year, we announced the launch of the new [Terraform v5 Provider](https://edgetunnel-b2h.pages.dev/changelog/2025-02-03-terraform-v5-provider/). We are aware of the high number of [issues ↗](https://github.com/cloudflare/terraform-provider-cloudflare) reported by the Cloudflare Community related to the v5 release. We have committed to releasing improvements on a two week cadence to ensure stability and reliability.  
One key change we adopted in recent weeks is a pivot to more comprehensive, test-driven development. We are still evaluating individual issues, but are also investing in much deeper testing to drive our stabilization efforts. We will subsequently be investing in comprehensive migration scripts. As a result, you will see several of the highest traffic APIs have been stabilized in the most recent release, and are supported by comprehensive acceptance tests.  
Thank you for continuing to raise issues. We triage them weekly and they help make our products stronger.  
#### Changes

  * Resources stabilized:  
    * `cloudflare_argo_smart_routing`
    * `cloudflare_bot_management`
    * `cloudflare_list`
    * `cloudflare_list_item`
    * `cloudflare_load_balancer`
    * `cloudflare_load_balancer_monitor`
    * `cloudflare_load_balancer_pool`
    * `cloudflare_spectrum_application`
    * `cloudflare_managed_transforms`
    * `cloudflare_url_normalization_settings`
    * `cloudflare_snippet`
    * `cloudflare_snippet_rules`
    * `cloudflare_zero_trust_access_application`
    * `cloudflare_zero_trust_access_group`
    * `cloudflare_zero_trust_access_identity_provider`
    * `cloudflare_zero_trust_access_mtls_certificate`
    * `cloudflare_zero_trust_access_mtls_hostname_settings`
    * `cloudflare_zero_trust_access_policy`
    * `cloudflare_zone`
  * Multipart handling restored for `cloudflare_snippet`
  * `cloudflare_bot_management` diff issues resolves when running `terraform plan` and `terraform apply`
  * Other bug fixes  
For a more detailed look at all of the changes, refer to the [changelog ↗](https://github.com/cloudflare/terraform-provider-cloudflare/releases/tag/v5.8.4) in GitHub.  
#### Issues Closed

  * [#5017: 'Uncaught Error: No such module' using cloudflare\_snippets ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5017)
  * [#5701: cloudflare\_workers\_script migrations for Durable Objects not recorded in tfstate; cannot be upgraded between versions ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5701)
  * [#5640: cloudflare\_argo\_smart\_routing importing doesn't read the actual value ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5640)  
If you have an unaddressed issue with the provider, we encourage you to check the [open issues ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues) and open a new one if one does not already exist for what you are experiencing.  
#### Upgrading  
We suggest holding off on migration to v5 while we work on stabilization. This will help you avoid any blocking issues while the Terraform resources are actively being stabilized.  
If you'd like more information on migrating to v5, please make use of the [migration guide ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/guides/version-5-upgrade). We have provided automated migration scripts using Grit which simplify the transition. These migration scripts do not support implementations which use Terraform modules, so customers making use of modules need to migrate manually. Please make use of `terraform plan` to test your changes before applying, and let us know if you encounter any additional issues by reporting to our [GitHub repository ↗](https://github.com/cloudflare/terraform-provider-cloudflare).  
#### For more info

  * [Terraform provider ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
  * [Documentation on using Terraform with Cloudflare](https://edgetunnel-b2h.pages.dev/terraform/)

Aug 15, 2025
1. ### [The Node.js and Web File System APIs in Workers](https://edgetunnel-b2h.pages.dev/changelog/post/2025-08-15-nodejs-fs/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
Implementations of the [node:fs module ↗](https://nodejs.org/docs/latest/api/fs.html) and the [Web File System API ↗](https://developer.mozilla.org/en-US/docs/Web/API/File%5FSystem%5FAccess%5FAPI) are now available in Workers.  
#### Using the `node:fs` module  
The `node:fs` module provides access to a virtual file system in Workers. You can use it to read and write files, create directories, and perform other file system operations.  
The virtual file system is ephemeral with each individual request havig its own isolated temporary file space. Files written to the file system will not persist across requests and will not be shared across requests or across different Workers.  
Workers running with the `nodejs_compat` compatibility flag will have access to the `node:fs` module by default when the compatibility date is set to `2025-09-01` or later. Support for the API can also be enabled using the `enable_nodejs_fs_module` compatibility flag together with the `nodejs_compat` flag. The `node:fs` module can be disabled using the `disable_nodejs_fs_module` compatibility flag.

**JavaScript**  
```js  
import fs from "node:fs";  
const config = JSON.parse(fs.readFileSync("/bundle/config.json", "utf-8"));  
export default {  
  async fetch(request) {  
    return new Response(`Config value: ${config.value}`);  
  },  
};  
```  
There are a number of initial limitations to the `node:fs` implementation:

  * The glob APIs (e.g. `fs.globSync(...)`) are not implemented.
  * The file watching APIs (e.g. `fs.watch(...)`) are not implemented.
  * The file timestamps (modified time, access time, etc) are only partially supported. For now, these will always return the Unix epoch.  
Refer to the [Node.js documentation ↗](https://nodejs.org/docs/latest/api/fs.html) for more information on the `node:fs` module and its APIs.  
#### The Web File System API  
The Web File System API provides access to the same virtual file system as the `node:fs` module, but with a different API surface. The Web File System API is only available in Workers running with the `enable_web_file_system` compatibility flag. The `nodejs_compat` compatibility flag is not required to use the Web File System API.

**JavaScript**  
```js  
const root = navigator.storage.getDirectory();  
export default {  
  async fetch(request) {  
    const tmp = await root.getDirectoryHandle("/tmp");  
    const file = await tmp.getFileHandle("data.txt", { create: true });  
    const writable = await file.createWritable();  
    const writer = writable.getWriter();  
    await writer.write("Hello, World!");  
    await writer.close();  
    return new Response("File written successfully!");  
  },  
};  
```  
As there are still some parts of the Web File System API that are not fully standardized, there may be some differences between the Workers implementation and the implementations in browsers.

```json
{"@context":"https://schema.org","@type":"BlogPosting","@id":"https://edgetunnel-b2h.pages.dev/changelog/product-group/developer-platform/13/#page","headline":"Developer platform Changelog | Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/changelog/product-group/developer-platform/13/","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/"}}
```