---
title: Changelogs
image: https://developers.cloudflare.com/cf-twitter-card.png
---

> Documentation Index  
> Fetch the complete documentation index at: https://developers.cloudflare.com/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://developers.cloudflare.com/changelog/rss/index.xml) [ View RSS feeds ](https://developers.cloudflare.com/fundamentals/new-features/available-rss-feeds/) 

All products

![hero image](https://developers.cloudflare.com/_astro/hero.CVYJHPAd_26AMqX.svg) 

Jan 12, 2026
1. ### [Metro code field now available in Rules](https://developers.cloudflare.com/changelog/post/2026-01-12-dma-metro-code-field/)  
[ Rules ](https://developers.cloudflare.com/rules/)  
The `ip.src.metro_code` field in the Ruleset Engine is now populated with DMA (Designated Market Area) data.  
You can use this field to build rules that target traffic based on geographic market areas, enabling more granular location-based policies for your applications.  
#### Field details

| Field              | Type           | Description                                                                                                                   |
| ------------------ | -------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| ip.src.metro\_code | String \| null | The metro code (DMA) of the incoming request's IP address. Returns the designated market area code for the client's location. |  
Example filter expression:  
```plaintext  
ip.src.metro_code eq "501"  
```  
For more information, refer to the [Fields reference](https://developers.cloudflare.com/ruleset-engine/rules-language/fields/reference/ip.src.metro%5Fcode/).

Jan 12, 2026
1. ### [Cloudflare Threat Events now support STIX2 format](https://developers.cloudflare.com/changelog/post/2026-01-12-stix2-available-for-threat-events-api/)  
[ Security Center ](https://developers.cloudflare.com/security-center/)  
We are excited to announce that **Cloudflare Threat Events** now supports the **STIX2 (Structured Threat Information Expression)** format. This was a highly requested feature designed to streamline how security teams consume and act upon our threat intelligence.  
By adopting this industry-standard format, you can now integrate Cloudflare's threat events data more effectively into your existing security ecosystem.  
#### Key benefits

  * Eliminate the need for custom parsers, as STIX2 allows for "out of the box" ingestion into major **Threat Intel Platforms (TIPs)**, **SIEMs**, and **SOAR** tools.
  * STIX2 provides a standardized way to represent relationships between indicators, sightings, and threat actors, giving your analysts a clearer picture of the threat landscape.  
For technical details on how to query events using this format, please refer to our [Threat Events API Documentation ↗](https://developers.cloudflare.com/api/resources/cloudforce%5Fone/subresources/threat%5Fevents/methods/list/).

---

Jan 12, 2026
1. ### [WAF Release - 2026-01-12](https://developers.cloudflare.com/changelog/post/2026-01-12-waf-release/)  
[ WAF ](https://developers.cloudflare.com/waf/)  
This week's release focuses on improvements to existing detections to enhance coverage.

**Key Findings**

  * Existing rule enhancements have been deployed to improve detection resilience against SQL Injection.
  
| Ruleset                    | Rule ID     | Legacy Rule ID | Description                        | Previous Action | New Action | Comments                                                                                     |
| -------------------------- | ----------- | -------------- | ---------------------------------- | --------------- | ---------- | -------------------------------------------------------------------------------------------- |
| Cloudflare Managed Ruleset | ...48a1841a | N/A            | SQLi - AND/OR MAKE\_SET/ELT - Beta | Log             | Block      | This rule is merged into the original rule "SQLi - AND/OR MAKE\_SET/ELT" (ID: ...252d3934  ) |
| Cloudflare Managed Ruleset | ...9e553ad3 | N/A            | SQLi - Benchmark Function - Beta   | Log             | Block      | This rule is merged into the original rule "SQLi - Benchmark Function" (ID: ...2ebc44ad  )   |

Jan 12, 2026
1. ### [Validate your generated types with \`wrangler types --check\`](https://developers.cloudflare.com/changelog/post/2026-01-11-wrangler-types-check/)  
[ Workers ](https://developers.cloudflare.com/workers/)  
Wrangler now supports a `--check` flag for the `wrangler types` command. This flag validates that your generated types are up to date without writing any changes to disk.  
This is useful in CI/CD pipelines where you want to ensure that developers have regenerated their types after making changes to their Wrangler configuration. If the types are out of date, the command will exit with a non-zero status code.  
```sh  
npx wrangler types --check  
```  
If your types are up to date, the command will succeed silently. If they are out of date, you'll see an error message indicating which files need to be regenerated.  
For more information, see the [Wrangler types documentation](https://developers.cloudflare.com/workers/wrangler/commands/general/#types).

Jan 09, 2026
1. ### [Get notified when your Workers builds succeed or fail](https://developers.cloudflare.com/changelog/post/2025-12-11-builds-event-subscriptions/)  
[ Workers ](https://developers.cloudflare.com/workers/)[ Queues ](https://developers.cloudflare.com/queues/)  
You can now receive notifications when your Workers' builds start, succeed, fail, or get cancelled using [Event Subscriptions](https://developers.cloudflare.com/queues/event-subscriptions/).  
[Workers Builds](https://developers.cloudflare.com/workers/ci-cd/builds/) publishes events to a [Queue](https://developers.cloudflare.com/queues/) that your Worker can read messages from, and then send notifications wherever you need — Slack, Discord, email, or any webhook endpoint.  
You can deploy [this Worker ↗](https://github.com/cloudflare/templates/tree/main/workers-builds-notifications-template) to your own Cloudflare account to send build notifications to Slack:  
[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/templates/tree/main/workers-builds-notifications-template)  
The template includes:

  * Build status with Preview/Live URLs for successful deployments
  * Inline error messages for failed builds
  * Branch, commit hash, and author name  
![Slack notifications showing build events](https://developers.cloudflare.com/_astro/builds-notifications-slack.rcRiU95L_169ufw.webp)  
For setup instructions, refer to the [template README ↗](https://github.com/cloudflare/templates/tree/main/workers-builds-notifications-template#readme) or the [Event Subscriptions documentation](https://developers.cloudflare.com/queues/event-subscriptions/manage-event-subscriptions/).

Jan 09, 2026
1. ### [Shell tab completions for Wrangler CLI](https://developers.cloudflare.com/changelog/post/2026-01-09-wrangler-tab-completion/)  
[ Workers ](https://developers.cloudflare.com/workers/)  
Wrangler now includes built-in shell tab completion support, making it faster and easier to navigate commands without memorizing every option. Press Tab as you type to autocomplete commands, subcommands, flags, and even option values like log levels.  
Tab completions are supported for Bash, Zsh, Fish, and PowerShell.  
#### Setup  
Generate the completion script for your shell and add it to your configuration file:  
```sh  
# Bash  
wrangler complete bash >> ~/.bashrc  
# Zsh  
wrangler complete zsh >> ~/.zshrc  
# Fish  
wrangler complete fish >> ~/.config/fish/config.fish  
# PowerShell  
wrangler complete powershell >> $PROFILE  
```  
After adding the script, restart your terminal or source your configuration file for the changes to take effect. Then you can simply press Tab to see available completions:  
```sh  
wrangler d<TAB>          # completes to 'deploy', 'dev', 'd1', etc.  
wrangler kv <TAB>        # shows subcommands: namespace, key, bulk  
```  
Tab completions are dynamically generated from Wrangler's command registry, so they stay up-to-date as new commands and options are added. This feature is powered by [@bomb.sh/tab ↗](https://github.com/bombshell-dev/tab/).  
See the [wrangler complete documentation](https://developers.cloudflare.com/workers/wrangler/commands/general/#complete) for more details.

Jan 08, 2026
1. ### [Cloudflare admin activity logs capture creation of DNS over HTTP (DoH) users](https://developers.cloudflare.com/changelog/post/2026-01-08-access-audit-log-for-doh-users/)  
[ Access ](https://developers.cloudflare.com/cloudflare-one/access-controls/policies/)  
Cloudflare [admin activity logs](https://developers.cloudflare.com/cloudflare-one/insights/logs/) now capture each time a [DNS over HTTP (DoH) user](https://developers.cloudflare.com/cloudflare-one/networks/resolvers-and-proxies/dns/dns-over-https/) is created.  
These logs can be viewed from the [Cloudflare One dashboard ↗](https://one.dash.cloudflare.com/), pulled via the [Cloudflare API](https://developers.cloudflare.com/api/), and exported through [Logpush](https://developers.cloudflare.com/cloudflare-one/insights/logs/logpush/).

Jan 07, 2026
1. ### [Workers Analytics Engine SQL now supports filtering using HAVING and LIKE](https://developers.cloudflare.com/changelog/post/2026-01-07-analytics-engine-support-for-like-and-having/)  
[ Workers Analytics Engine ](https://developers.cloudflare.com/analytics/analytics-engine/)[ Workers ](https://developers.cloudflare.com/workers/)  
You can now use the `HAVING` clause and `LIKE` pattern matching operators in [Workers Analytics Engine ↗](https://developers.cloudflare.com/analytics/analytics-engine/).  
Workers Analytics Engine allows you to ingest and store high-cardinality data at scale and query your data through a simple SQL API.  
#### Filtering using `HAVING`  
The `HAVING` clause complements the `WHERE` clause by enabling you to filter groups based on aggregate values. While `WHERE` filters rows before aggregation, `HAVING` filters groups after aggregation is complete.  
You can use `HAVING` to filter groups where the average exceeds a threshold:  
```sql  
SELECT  
    blob1 AS probe_name,  
    avg(double1) AS average_temp  
FROM temperature_readings  
GROUP BY probe_name  
HAVING average_temp > 10  
```  
You can also filter groups based on aggregates such as the number of items in the group:  
```sql  
SELECT  
    blob1 AS probe_name,  
    count() AS num_readings  
FROM temperature_readings  
GROUP BY probe_name  
HAVING num_readings > 100  
```  
#### Pattern matching using `LIKE`  
The new pattern matching operators enable you to search for strings that match specific patterns using wildcard characters:

  * `LIKE` \- case-sensitive pattern matching
  * `NOT LIKE` \- case-sensitive pattern exclusion
  * `ILIKE` \- case-insensitive pattern matching
  * `NOT ILIKE` \- case-insensitive pattern exclusion  
Pattern matching supports two wildcard characters: `%` (matches zero or more characters) and `_` (matches exactly one character).  
You can match strings starting with a prefix:  
```sql  
SELECT *  
FROM logs  
WHERE blob1 LIKE 'error%'  
```  
You can also match file extensions (case-insensitive):  
```sql  
SELECT *  
FROM requests  
WHERE blob2 ILIKE '%.jpg'  
```  
Another example is excluding strings containing specific text:  
```sql  
SELECT *  
FROM events  
WHERE blob3 NOT ILIKE '%debug%'  
```  
#### Ready to get started?  
Learn more about the [HAVING clause](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/statements/#having-clause) or [pattern matching operators](https://developers.cloudflare.com/analytics/analytics-engine/sql-reference/operators/#pattern-matching-operators) in the Workers Analytics Engine SQL reference documentation.

Jan 05, 2026
1. ### [Custom container instance types now available for all users](https://developers.cloudflare.com/changelog/post/2026-01-05-custom-instance-types/)  
[ Containers ](https://developers.cloudflare.com/containers/)  
Custom instance types are now enabled for all [Cloudflare Containers](https://developers.cloudflare.com/containers) users. You can now specify specific vCPU, memory, and disk amounts, rather than being limited to pre-defined [instance types](https://developers.cloudflare.com/containers/platform-details/limits/#instance-types). Previously, only select Enterprise customers were able to customize their instance type.  
To use a custom instance type, specify the `instance_type` property as an object with `vcpu`, `memory_mib`, and `disk_mb` fields in your Wrangler configuration:

**TOML**  
```toml  
[[containers]]  
image = "./Dockerfile"  
instance_type = { vcpu = 2, memory_mib = 6144, disk_mb = 12000 }  
```  
Individual limits for custom instance types are based on the `standard-4` instance type (4 vCPU, 12 GiB memory, 20 GB disk). You must allocate at least 1 vCPU for custom instance types. For workloads requiring less than 1 vCPU, use the predefined instance types like `lite` or `basic`.  
See the [limits documentation](https://developers.cloudflare.com/containers/platform-details/limits/#custom-instance-types) for the full list of constraints on custom instance types. See the [getting started guide](https://developers.cloudflare.com/containers/get-started/) to deploy your first Container,

Jan 01, 2026
1. ### [Build microfrontend applications on Workers](https://developers.cloudflare.com/changelog/post/2026-01-01-microfrontends/)  
[ Workers ](https://developers.cloudflare.com/workers/)  
You can now deploy microfrontends to Cloudflare, splitting a single application into smaller, independently deployable units that render as one cohesive application. This lets different teams using different frameworks develop, test, and deploy each microfrontend without coordinating releases.  
Microfrontends solve several challenges for large-scale applications:

  * **Independent deployments**: Teams deploy updates on their own schedule without redeploying the entire application
  * **Framework flexibility**: Build multi-framework applications (for example, Astro, Remix, and Next.js in one app)
  * **Gradual migration**: Migrate from a monolith to a distributed architecture incrementally  
Create a microfrontend project:  
[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create?type=vmfe)  
This template automatically creates a router worker with pre-configured routing logic, and lets you configure [Service bindings](https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/) to Workers you have already deployed to your Cloudflare account. The router Worker analyzes incoming requests, matches them against configured routes, and forwards requests to the appropriate microfrontend via service bindings. The router automatically rewrites HTML, CSS, and headers to ensure assets load correctly from each microfrontend's mount path. The router includes advanced features like preloading for faster navigation between microfrontends, smooth page transitions using the View Transitions API, and automatic path rewriting for assets, redirects, and cookies.  
Each microfrontend can be a full-framework application, a static site with Workers Static Assets, or any other Worker-based application.  
Get started with the [microfrontends template ↗](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create?type=vmfe), or read the [microfrontends documentation](https://developers.cloudflare.com/workers/framework-guides/web-apps/microfrontends/) for implementation details.

Dec 31, 2025
1. ### [Breakout traffic visibility via NetFlow](https://developers.cloudflare.com/changelog/post/2025-12-31-connector-breakout-traffic-netflow/)  
[ Cloudflare One Appliance ](https://developers.cloudflare.com/cloudflare-wan/configuration/appliance/)[ Cloudflare One ](https://developers.cloudflare.com/cloudflare-one/)[ Cloudflare WAN ](https://developers.cloudflare.com/cloudflare-wan/)  
Magic WAN Connector now exports NetFlow data for breakout traffic to Magic Network Monitoring (MNM), providing visibility into traffic that bypasses Cloudflare's security filtering.  
This feature allows you to:

  * Monitor breakout traffic statistics in the Cloudflare dashboard.
  * View traffic patterns for applications configured to bypass Cloudflare.
  * Maintain visibility across all traffic passing through your Magic WAN Connector.  
For more information, refer to [NetFlow statistics](https://developers.cloudflare.com/cloudflare-wan/analytics/netflow-analytics/).

Dec 22, 2025
1. ### [Agents SDK v0.3.0, workers-ai-provider v3.0.0, and ai-gateway-provider v3.0.0 with AI SDK v6 support](https://developers.cloudflare.com/changelog/post/2025-12-22-agents-sdk-ai-sdk-v6/)  
[ Agents ](https://developers.cloudflare.com/agents/)[ Workers ](https://developers.cloudflare.com/workers/)  
We've shipped a new release for the [Agents SDK ↗](https://github.com/cloudflare/agents) v0.3.0 bringing full compatibility with [AI SDK v6 ↗](https://ai-sdk.dev/docs/introduction) and introducing the unified tool pattern, dynamic tool approval, and enhanced React hooks with improved tool handling.  
This release includes improved streaming and tool support, dynamic tool approval (for "human in the loop" systems), enhanced React hooks with `onToolCall` callback, improved error handling for streaming responses, and seamless migration from v5 patterns.  
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 tool execution and approval workflows.  
Additionally, we've updated **workers-ai-provider v3.0.0**, the official provider for Cloudflare Workers AI models, and **ai-gateway-provider v3.0.0**, the provider for Cloudflare AI Gateway, to be compatible with AI SDK v6.  
#### Agents SDK v0.3.0  
#### Unified Tool Pattern  
AI SDK v6 introduces a unified tool pattern where all tools are defined on the server using the `tool()` function. This replaces the previous client-side `AITool` pattern.  
#### Server-Side Tool Definition

**TypeScript**  
```ts  
import { tool } from "ai";  
import { z } from "zod";  
// Server: Define ALL tools on the server  
const tools = {  
  // Server-executed tool  
  getWeather: tool({  
    description: "Get weather for a city",  
    inputSchema: z.object({ city: z.string() }),  
    execute: async ({ city }) => fetchWeather(city)  
  }),  
  // Client-executed tool (no execute = client handles via onToolCall)  
  getLocation: tool({  
    description: "Get user location from browser",  
    inputSchema: z.object({})  
    // No execute function  
  }),  
  // Tool requiring approval (dynamic based on input)  
  processPayment: tool({  
    description: "Process a payment",  
    inputSchema: z.object({ amount: z.number() }),  
    needsApproval: async ({ amount }) => amount > 100,  
    execute: async ({ amount }) => charge(amount)  
  })  
};  
```  
#### Client-Side Tool Handling

**TypeScript**  
```ts  
// Client: Handle client-side tools via onToolCall callback  
import { useAgentChat } from "agents/ai-react";  
const { messages, sendMessage, addToolOutput } = useAgentChat({  
  agent,  
  onToolCall: async ({ toolCall, addToolOutput }) => {  
    if (toolCall.toolName === "getLocation") {  
      const position = await new Promise((resolve, reject) => {  
        navigator.geolocation.getCurrentPosition(resolve, reject);  
      });  
      addToolOutput({  
        toolCallId: toolCall.toolCallId,  
        output: {  
          lat: position.coords.latitude,  
          lng: position.coords.longitude  
        }  
      });  
    }  
  }  
});  
```

**Key benefits of the unified tool pattern:**

  * **Server-defined tools**: All tools are defined in one place on the server
  * **Dynamic approval**: Use `needsApproval` to conditionally require user confirmation
  * **Cleaner client code**: Use `onToolCall` callback instead of managing tool configs
  * **Type safety**: Full TypeScript support with proper tool typing  
#### useAgentChat(options)  
Creates a new chat interface with enhanced v6 capabilities.

**TypeScript**  
```ts  
// Basic chat setup with onToolCall  
const { messages, sendMessage, addToolOutput } = useAgentChat({  
  agent,  
  onToolCall: async ({ toolCall, addToolOutput }) => {  
    // Handle client-side tool execution  
    await addToolOutput({  
      toolCallId: toolCall.toolCallId,  
      output: { result: "success" }  
    });  
  }  
});  
```  
#### Dynamic Tool Approval  
Use `needsApproval` on server tools to conditionally require user confirmation:

**TypeScript**  
```ts  
const paymentTool = tool({  
  description: "Process a payment",  
  inputSchema: z.object({  
    amount: z.number(),  
    recipient: z.string()  
  }),  
  needsApproval: async ({ amount }) => amount > 1000,  
  execute: async ({ amount, recipient }) => {  
    return await processPayment(amount, recipient);  
  }  
});  
```  
#### Tool Confirmation Detection  
The `isToolUIPart` and `getToolName` functions now check both static and dynamic tool parts:

**TypeScript**  
```ts  
import { isToolUIPart, getToolName } from "ai";  
const pendingToolCallConfirmation = messages.some((m) =>  
  m.parts?.some(  
    (part) => isToolUIPart(part) && part.state === "input-available",  
  ),  
);  
// Handle tool confirmation  
if (pendingToolCallConfirmation) {  
  await addToolOutput({  
    toolCallId: part.toolCallId,  
    output: "User approved the action"  
  });  
}  
```  
If you need the v5 behavior (static-only checks), use the new functions:

**TypeScript**  
```ts  
import { isStaticToolUIPart, getStaticToolName } from "ai";  
```  
#### convertToModelMessages() is now async  
The `convertToModelMessages()` function is now asynchronous. Update all calls to await the result:

**TypeScript**  
```ts  
import { convertToModelMessages } from "ai";  
const result = streamText({  
  messages: await convertToModelMessages(this.messages),  
  model: openai("gpt-4o")  
});  
```  
#### ModelMessage type  
The `CoreMessage` type has been removed. Use `ModelMessage` instead:

**TypeScript**  
```ts  
import { convertToModelMessages, type ModelMessage } from "ai";  
const modelMessages: ModelMessage[] = await convertToModelMessages(messages);  
```  
#### generateObject mode option removed  
The `mode` option for `generateObject` has been removed:

**TypeScript**  
```ts  
// Before (v5)  
const result = await generateObject({  
  mode: "json",  
  model,  
  schema,  
  prompt  
});  
// After (v6)  
const result = await generateObject({  
  model,  
  schema,  
  prompt  
});  
```  
#### Structured Output with generateText  
While `generateObject` and `streamObject` are still functional, the recommended approach is to use `generateText`/`streamText` with the `Output.object()` helper:

**TypeScript**  
```ts  
import { generateText, Output, stepCountIs } from "ai";  
const { output } = await generateText({  
  model: openai("gpt-4"),  
  output: Output.object({  
    schema: z.object({ name: z.string() })  
  }),  
  stopWhen: stepCountIs(2),  
  prompt: "Generate a name"  
});  
```  
> **Note**: When using structured output with `generateText`, you must configure multiple steps with `stopWhen` because generating the structured output is itself a step.  
#### workers-ai-provider v3.0.0  
Seamless integration with Cloudflare Workers AI models through the updated workers-ai-provider v3.0.0 with AI SDK v6 support.  
#### 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 (v3.0.0 - enhanced v6 internals)  
const model = createWorkersAI({  
  binding: env.AI,  
})("@cf/meta/llama-3.2-3b-instruct");  
```  
#### Enhanced File and Image Support  
Workers AI models now support v6 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: await convertToModelMessages(messages),  
  onChunk: (chunk) => {  
    // Enhanced streaming with warning handling  
    console.log(chunk);  
  },  
});  
```  
#### ai-gateway-provider v3.0.0  
The ai-gateway-provider v3.0.0 now supports AI SDK v6, enabling you to use Cloudflare AI Gateway with multiple AI providers including Anthropic, Azure, AWS Bedrock, Google Vertex, and Perplexity.  
#### AI Gateway Setup  
Use Cloudflare AI Gateway to add analytics, caching, and rate limiting to your AI applications:

**TypeScript**  
```ts  
import { createAIGateway } from "ai-gateway-provider";  
// Create AI Gateway provider (v3.0.0 - enhanced v6 internals)  
const model = createAIGateway({  
  gatewayUrl: "https://gateway.ai.cloudflare.com/v1/your-account-id/gateway",  
  headers: {  
    "Authorization": `Bearer ${env.AI_GATEWAY_TOKEN}`  
  }  
})({  
  provider: "openai",  
  model: "gpt-4o"  
});  
```  
#### Migration from v5  
#### Deprecated APIs  
The following APIs are deprecated in favor of the unified tool pattern:

| Deprecated                            | Replacement                                      |
| ------------------------------------- | ------------------------------------------------ |
| AITool type                           | Use AI SDK's tool() function on server           |
| extractClientToolSchemas()            | Define tools on server, no client schemas needed |
| createToolsFromClientSchemas()        | Define tools on server with tool()               |
| toolsRequiringConfirmation option     | Use needsApproval on server tools                |
| experimental\_automaticToolResolution | Use onToolCall callback                          |
| tools option in useAgentChat          | Use onToolCall for client-side execution         |
| addToolResult()                       | Use addToolOutput()                              |  
#### Breaking Changes Summary

  1. **Unified Tool Pattern**: All tools must be defined on the server using `tool()`
  2. **`convertToModelMessages()` is async**: Add `await` to all calls
  3. **`CoreMessage` removed**: Use `ModelMessage` instead
  4. **`generateObject` mode removed**: Remove `mode` option
  5. **`isToolUIPart` behavior changed**: Now checks both static and dynamic tool parts  
#### Installation  
Update your dependencies to use the latest versions:  
```bash  
npm install agents@^0.3.0 workers-ai-provider@^3.0.0 ai-gateway-provider@^3.0.0 ai@^6.0.0 @ai-sdk/react@^3.0.0 @ai-sdk/openai@^3.0.0  
```  
#### Resources

  * [Migration Guide ↗](https://github.com/cloudflare/agents/blob/main/docs/migration-to-ai-sdk-v6.md) \- Comprehensive migration documentation from v5 to v6
  * [AI SDK v6 Documentation ↗](https://ai-sdk.dev/docs/migration-guides/migration-guide-6-0) \- Official AI SDK migration guide
  * [AI SDK v6 Announcement ↗](https://vercel.com/blog/ai-sdk-6) \- Learn about new features in v6
  * [AI SDK Documentation ↗](https://sdk.vercel.ai/docs) \- Complete AI SDK reference
  * [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 from v5 to v6?
  * **Unified tool pattern** \- How does the new server-defined tool pattern work for you?
  * **Dynamic tool approval** \- Does the `needsApproval` feature meet your needs?
  * **AI Gateway integration** \- How well does the new provider work with your setup?

Dec 19, 2025
1. ### [Terraform v5.15.0 now available](https://developers.cloudflare.com/changelog/post/2025-12-19-terraform-v5150-provider/)  
[ Cloudflare Fundamentals ](https://developers.cloudflare.com/fundamentals/)[ Terraform ](https://developers.cloudflare.com/terraform/)  
Earlier this year, we announced the launch of the new Terraform v5 Provider. We are aware of the high number of issues reported by the Cloudflare community related to the v5 release. We have committed to releasing improvements on a [2-3 week cadence ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/5774) to ensure its stability and reliability, including the v5.15 release. We have also pivoted from an [issue-to-issue approach to a resource-per-resource approach ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237) \- we will be focusing on specific resources to not only stabilize the resource but also ensure it is migration-friendly for those migrating from v4 to v5.  
Thank you for continuing to raise issues. They make our provider stronger and help us build products that reflect your needs.  
This release includes bug fixes, the stabilization of even more popular resources, and more.  
#### Features

  * **ai\_search:** Add AI Search endpoints ([6f02adb ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6f02adb420e872457f71f95b49cb527663388915))
  * **certificate\_pack:** Ensure proper Terraform resource ID handling for path parameters in API calls ([081f32a ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/081f32acab4ce9a194a7ff51c8e9fcabd349895a))
  * **worker\_version:** Support `startup_time_ms` ([286ab55 ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/286ab55bea8d5be0faa5a2b5b8b157e4a2214eba))
  * **zero\_trust\_dlp\_custom\_entry:** Support `upload_status` ([7dc0fe3 ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
  * **zero\_trust\_dlp\_entry:** Support `upload_status` ([7dc0fe3 ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
  * **zero\_trust\_dlp\_integration\_entry:** Support `upload_status` ([7dc0fe3 ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
  * **zero\_trust\_dlp\_predefined\_entry:** Support `upload_status` ([7dc0fe3 ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/7dc0fe3b23726ead8dc075f86728a0540846d90c))
  * **zero\_trust\_gateway\_policy:** Support `forensic_copy` ([5741fd0 ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))
  * **zero\_trust\_list:** Support additional types (category, location, device) ([5741fd0 ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5741fd0ed9f7270d20731cc47ec45eb0403a628b))  
#### Bug fixes

  * **access\_rules:** Add validation to prevent state drift. Ideally, we'd use Semantic Equality but since that isn't an option, this will remove a foot-gun. ([4457791 ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/44577911b3cbe45de6279aefa657bdee73c0794d))
  * **cloudflare\_pages\_project:** Addressing drift issues ([6edffcf ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/6edffcfcf187fdc9b10b624b9a9b90aed2fb2b2e)) ([3db318e ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3db318e747423bf10ce587d9149e90edcd8a77b0))
  * **cloudflare\_worker:** Can be cleanly imported ([4859b52 ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/4859b52968bb25570b680df9813f8e07fd50728f))
  * **cloudflare\_worker:** Ensure clean imports ([5b525bc ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/5b525bc478a4e2c9c0d4fd659b92cc7f7c18016a))
  * **list\_items:** Add validation for IP List items to avoid inconsistent state ([b6733dc ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/b6733dc4be909a5ab35895a88e519fc2582ccada))
  * **zero\_trust\_access\_application:** Remove all conditions from sweeper ([3197f1a ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/3197f1aed61be326d507d9e9e3b795b9f1d18fd7))
  * **spectrum\_application:** Map missing fields during spectrum resource import ([#6495 ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6495)) ([ddb4e72 ↗](https://github.com/cloudflare/terraform-provider-cloudflare/commit/ddb4e722b82c735825a549d651a9da219c142efa))  
#### Upgrade to newer version  
We suggest waiting to migrate to v5 while we work on stabilization. This helps with avoiding any blocking issues while the Terraform resources are actively being [stabilized ↗](https://github.com/cloudflare/terraform-provider-cloudflare/issues/6237). We will be releasing a new migration tool in March 2026 to help support v4 to v5 transitions for our most popular resources.  
#### For more information

  * [Terraform Provider ↗](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs)
  * [Documentation on using Terraform with Cloudflare](https://developers.cloudflare.com/terraform/)

Dec 19, 2025
1. ### [Static prerendering support for TanStack Start](https://developers.cloudflare.com/changelog/post/2025-12-19-tanstack-start-prerendering/)  
[ Workers ](https://developers.cloudflare.com/workers/)  
[TanStack Start ↗](https://tanstack.com/start/) apps can now prerender routes to static HTML at build time with access to build time environment variables and bindings, and serve them as [static assets](https://developers.cloudflare.com/workers/static-assets/). To enable prerendering, configure the `prerender` option of the TanStack Start plugin in your Vite config:

**vite.config.ts**  
```ts  
import { defineConfig } from "vite";  
import { cloudflare } from "@cloudflare/vite-plugin";  
import { tanstackStart } from "@tanstack/react-start/plugin/vite";  
export default defineConfig({  
  plugins: [  
    cloudflare({ viteEnvironment: { name: "ssr" } }),  
    tanstackStart({  
      prerender: {  
        enabled: true,  
      },  
    }),  
  ],  
});  
```  
This feature requires `@tanstack/react-start` v1.138.0 or later. See the [TanStack Start framework guide](https://developers.cloudflare.com/workers/framework-guides/web-apps/tanstack-start/#static-prerendering) for more details.

Dec 18, 2025
1. ### [New AI Crawl Control Overview tab](https://developers.cloudflare.com/changelog/post/2025-12-18-overview-tab/)  
[ AI Crawl Control ](https://developers.cloudflare.com/ai-crawl-control/)  
The **Overview** tab is now the default view in AI Crawl Control. The previous default view with controls for individual AI crawlers is available in the **Crawlers** tab.  
#### What's new

  * **Executive summary** — Monitor total requests, volume change, most common status code, most popular path, and high-volume activity
  * **Operator grouping** — Track crawlers by their operating companies (OpenAI, Microsoft, Google, ByteDance, Anthropic, Meta)
  * **Customizable filters** — Filter your snapshot by date range, crawler, operator, hostname, or path  
![AI Crawl Control Overview tab showing executive summary, metrics, and crawler groups](https://developers.cloudflare.com/_astro/ai-crawl-control-overview-tab.Duwqq4bm_ZmNhCs.webp)  
#### Get started

  1. Log in to the Cloudflare dashboard and select your account and domain.
  2. Go to **AI Crawl Control**, where the **Overview** tab opens by default with your activity snapshot.
  3. Use filters to customize your view by date range, crawler, operator, hostname, or path.
  4. Navigate to the **Crawlers** tab to manage controls for individual crawlers.  
Learn more about [analyzing AI traffic](https://developers.cloudflare.com/ai-crawl-control/features/analyze-ai-traffic/) and [managing AI crawlers](https://developers.cloudflare.com/ai-crawl-control/features/manage-ai-crawlers/).

Dec 18, 2025
1. ### [Improved accuracy of cached request classification in analytics](https://developers.cloudflare.com/changelog/post/2025-12-18-cached-request-classification/)  
[ Analytics ](https://developers.cloudflare.com/analytics/)  
The cached/uncached classification logic used in Zone Overview analytics has been updated to improve accuracy.  
Previously, requests were classified as "cached" based on an overly broad condition that included blocked 403 responses, Snippets requests, and other non-cache request types. This caused inflated cache hit ratios — in some cases showing near-100% cached — and affected approximately 15% of requests classified as cached in rollups.  
The condition has been removed from the Zone Overview page. Cached/uncached classification now aligns with the heuristics used in [HTTP Analytics](https://developers.cloudflare.com/analytics/account-and-zone-analytics/zone-analytics/), so only requests genuinely served from cache are counted as cached.

**What changed:**

  * **Zone Overview** — Cache ratios now reflect actual cache performance.
  * **HTTP Analytics** — No change. HTTP Analytics already used the correct classification logic.
  * **Historical data** — This fix applies to new requests only. Previously logged data is not retroactively updated.

Dec 18, 2025
1. ### [R2 Data Catalog now supports automatic snapshot expiration](https://developers.cloudflare.com/changelog/post/2025-12-18-r2-data-catalog-snapshot-expiration/)  
[ R2 ](https://developers.cloudflare.com/r2/)  
[R2 Data Catalog](https://developers.cloudflare.com/r2/data-catalog/) now supports automatic snapshot expiration for Apache Iceberg tables.  
In Apache Iceberg, a snapshot is metadata that represents the state of a table at a given point in time. Every mutation creates a new snapshot which enable powerful features like time travel queries and rollback capabilities but will accumulate over time.  
Without regular cleanup, these accumulated snapshots can lead to:

  * Metadata overhead
  * Slower table operations
  * Increased storage costs.  
Snapshot expiration in R2 Data Catalog automatically removes old table snapshots based on your configured retention policy, improving performance and storage costs.  
```bash  
# Enable catalog-level snapshot expiration  
# Expire snapshots older than 7 days, always retain at least 10 recent snapshots  
npx wrangler r2 bucket catalog snapshot-expiration enable my-bucket \
  --older-than-days 7 \
  --retain-last 10  
```  
Snapshot expiration uses two parameters to determine which snapshots to remove:

  * `--older-than-days`: age threshold in days
  * `--retain-last`: minimum snapshot count to retain  
Both conditions must be met before a snapshot is expired, ensuring you always retain recent snapshots even if they exceed the age threshold.  
This feature complements [automatic compaction](https://developers.cloudflare.com/r2/data-catalog/table-maintenance/), which optimizes query performance by combining small data files into larger ones. Together, these automatic maintenance operations keep your Iceberg tables performant and cost-efficient without manual intervention.  
To learn more about snapshot expiration and how to configure it, visit our [table maintenance documentation](https://developers.cloudflare.com/r2/data-catalog/table-maintenance/) or see [how to manage catalogs](https://developers.cloudflare.com/r2/data-catalog/manage-catalogs/).

Dec 18, 2025
1. ### [WAF Release - 2025-12-18](https://developers.cloudflare.com/changelog/post/2025-12-18-waf-release/)  
[ WAF ](https://developers.cloudflare.com/waf/)  
This week's release focuses on improvements to existing detections to enhance coverage.

**Key Findings**

  * Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.
  
  
| Ruleset                    | Rule ID     | Legacy Rule ID | Description                                                       | Previous Action | New Action | Comments                                                                                                                    |
| -------------------------- | ----------- | -------------- | ----------------------------------------------------------------- | --------------- | ---------- | --------------------------------------------------------------------------------------------------------------------------- |
| Cloudflare Managed Ruleset | ...be5ec20c | N/A            | Atlassian Confluence - Code Injection - CVE:CVE-2021-26084 - Beta | Log             | Block      | This rule is merged into the original rule "Atlassian Confluence - Code Injection - CVE:CVE-2021-26084" (ID: ...69e0b97a  ) |
| Cloudflare Managed Ruleset | ...0d9206e3 | N/A            | PostgreSQL - SQLi - Copy - Beta                                   | Log             | Block      | This rule is merged into the original rule "PostgreSQL - SQLi - COPY" (ID: ...e7265a4e  )                                   |
| Cloudflare Managed Ruleset | ...0cd00ba7 | N/A            | Generic Rules - Command Execution - Body                          | Log             | Disabled   | This is a new detection.                                                                                                    |
| Cloudflare Managed Ruleset | ...cd679ad4 | N/A            | Generic Rules - Command Execution - Header                        | Log             | Disabled   | This is a new detection.                                                                                                    |
| Cloudflare Managed Ruleset | ...fd181fb3 | N/A            | Generic Rules - Command Execution - URI                           | Log             | Disabled   | This is a new detection.                                                                                                    |
| Cloudflare Managed Ruleset | ...7a95bc3a | N/A            | SQLi - Tautology - URI - Beta                                     | Log             | Block      | This rule is merged into the original rule "SQLi - Tautology - URI" (ID: ...b3de2e0a  )                                     |
| Cloudflare Managed Ruleset | ...432ac90d | N/A            | SQLi - WaitFor Function - Beta                                    | Log             | Block      | This rule is merged into the original rule "SQLi - WaitFor Function" (ID: ...d5faba59  )                                    |
| Cloudflare Managed Ruleset | ...596c741e | N/A            | SQLi - AND/OR Digit Operator Digit 2 - Beta                       | Log             | Block      | This rule is merged into the original rule "SQLi - AND/OR Digit Operator Digit" (ID: ...88d80772  )                         |
| Cloudflare Managed Ruleset | ...03b2f3fe | N/A            | SQLi - Equation 2 - Beta                                          | Log             | Block      | This rule is merged into the original rule "SQLi - Equation" (ID: ...a72a6b3a  )                                            |

Dec 18, 2025
1. ### [Workers for Platforms - Dashboard Improvements](https://developers.cloudflare.com/changelog/post/2025-12-18-dashboard-improvements/)  
[ Workers for Platforms ](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/)  
[Workers for Platforms](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/) lets you build multi-tenant platforms on [Cloudflare Workers](https://developers.cloudflare.com/workers/), allowing your end users to deploy and run their own code on your platform. It's designed for anyone building an AI vibe coding platform, e-commerce platform, website builder, or any product that needs to securely execute user-generated code at scale.  
Previously, setting up Workers for Platforms required using the API. Now, the Workers for Platforms UI supports namespace creation, dispatch worker templates, and tag management, making it easier for Workers for Platforms customers to build and manage multi-tenant platforms directly from the Cloudflare dashboard.  
![Workers for Platforms Dashboard Improvements](https://developers.cloudflare.com/_astro/dashboard-improvements.ChVWUo88_ZNokyq.webp)  
#### Key improvements

  * **Namespace Management:** You can now create and configure [dispatch namespaces](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/how-workers-for-platforms-works/#dispatch-namespace) directly within the dashboard to start a new platform setup.
  * **Dispatch Worker Templates:** New Dispatch Worker templates allow you to quickly define how traffic is routed to individual Workers within your namespace. Refer to the [Dynamic Dispatch documentation](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/dynamic-dispatch/) for more examples.
  * **Tag Management:** You can now set and update [tags](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/tags/) on User Workers, making it easier to group and manage your Workers.
  * **Binding Visibility:** [Bindings](https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/bindings/) attached to User Workers are now visible directly within the User Worker view.
  * **Deploy Vibe Coding Platform in one-click:** Deploy a [reference implementation](https://developers.cloudflare.com/reference-architecture/diagrams/ai/ai-vibe-coding-platform/) of an AI vibe coding platform directly from the dashboard. Powered by the Cloudflare's [VibeSDK ↗](https://github.com/cloudflare/vibesdk), this starter kit integrates with Workers for Platforms to handle the deployment of AI-generated projects at scale.  
To get started, go to **Workers for Platforms** under **Compute & AI** in the [Cloudflare dashboard ↗](https://dash.cloudflare.com/).

Dec 18, 2025
1. ### [Build image policies for Workers Builds and Cloudflare Pages](https://developers.cloudflare.com/changelog/post/2025-12-01-build-image-policies-dev-plat/)  
[ Workers ](https://developers.cloudflare.com/workers/)  
We've published build image policies for [Workers Builds](https://developers.cloudflare.com/workers/ci-cd/builds/build-image/#build-image-policy) and [Cloudflare Pages](https://developers.cloudflare.com/pages/configuration/build-image/#build-image-policy), which establish:

  * **Minor version updates**: We typically update preinstalled software to the latest available minor version without notice. For tools that don't follow semantic versioning (e.g., Bun or Hugo), we provide 3 months’ notice.
  * **Major version updates**: Before preinstalled software reaches end-of-life, we update to the next stable LTS version with 3 months’ notice.
  * **Build image version deprecation (Pages only)**: We provide 6 months’ notice before deprecation. Projects on v1 or v2 will be automatically moved to v3 on their specified deprecation dates.  
To prepare for updates, monitor the [Cloudflare Changelog ↗](https://developers.cloudflare.com/changelog/), dashboard notifications, and email. You can also [override default versions](https://developers.cloudflare.com/workers/ci-cd/builds/build-image/#overriding-default-versions) to maintain specific versions.

Dec 18, 2025
1. ### [Retrieve your authentication token with \`wrangler auth token\`](https://developers.cloudflare.com/changelog/post/2025-12-18-wrangler-auth-token/)  
[ Workers ](https://developers.cloudflare.com/workers/)  
Wrangler now includes a new [wrangler auth token](https://developers.cloudflare.com/workers/wrangler/commands/general/#auth-token) command that retrieves your current authentication token or credentials for use with other tools and scripts.  
```sh  
wrangler auth token  
```  
The command returns whichever authentication method is currently configured, in priority order: API token from `CLOUDFLARE_API_TOKEN`, or OAuth token from `wrangler login` (automatically refreshed if expired).  
Use the `--json` flag to get structured output including the token type:  
```sh  
wrangler auth token --json  
```  
The JSON output includes the authentication type:

**JSONC**  
```jsonc  
// API token  
{ "type": "api_token", "token": "..." }  
// OAuth token  
{ "type": "oauth", "token": "..." }  
// API key/email (only available with --json)  
{ "type": "api_key", "key": "...", "email": "..." }  
```  
API key/email credentials from `CLOUDFLARE_API_KEY` and `CLOUDFLARE_EMAIL` require the `--json` flag since this method uses two values instead of a single token.

Dec 17, 2025
1. ### [Shadow IT - domain level SaaS analytics](https://developers.cloudflare.com/changelog/post/2025-12-17-shadow-it-domain-analytics/)  
[ Gateway ](https://developers.cloudflare.com/cloudflare-one/traffic-policies/)[ Cloudflare One ](https://developers.cloudflare.com/cloudflare-one/)  
Zero Trust has again upgraded its **Shadow IT analytics**, providing you with unprecedented visibility into your organizations use of SaaS tools. With this dashboard, you can review who is using an application and volumes of data transfer to the application.  
With this update, you can review data transfer metrics at the domain level, rather than just the application level, providing more granular insight into your data transfer patterns.  
![New Domain Level Metrics](https://developers.cloudflare.com/_astro/shadow-it-domain.DoZnGAtf_Z1mHw4r.webp)  
These metrics can be filtered by all available filters on the dashboard, including user, application, or content category.  
Both the analytics and policies are accessible in the Cloudflare [Zero Trust dashboard ↗](https://one.dash.cloudflare.com/), empowering organizations with better visibility and control.

Dec 16, 2025
1. ### [New duplicate action for supported Cloudflare One resources](https://developers.cloudflare.com/changelog/post/2025-12-16-new-duplicate-action-for-supported-cloudflare-one-resources/)  
[ Cloudflare One ](https://developers.cloudflare.com/cloudflare-one/)  
You can now duplicate specific Cloudflare One resources with a single click from the dashboard.  
Initially supported resources:

  * Access Applications
  * Access Policies
  * Gateway Policies  
To try this out, simply click on the overflow menu (⋮) from the resource table and click _Duplicate_. We will continue to add the Duplicate action for resources throughout 2026.

Dec 16, 2025
1. ### [Support for ctx.exports in @cloudflare/vitest-pool-workers](https://developers.cloudflare.com/changelog/post/2025-12-16-vitest-ctx-exports-support/)  
[ Workers ](https://developers.cloudflare.com/workers/)  
The [@cloudflare/vitest-pool-workers](https://developers.cloudflare.com/workers/testing/vitest-integration/) package now supports the [ctx.exports API](https://developers.cloudflare.com/workers/runtime-apis/context/#exports), allowing you to access your Worker's top-level exports during tests.  
You can access `ctx.exports` in unit tests by calling `createExecutionContext()`:

**TypeScript**  
```ts  
import { createExecutionContext } from "cloudflare:test";  
import { it, expect } from "vitest";  
it("can access ctx.exports", async () => {  
  const ctx = createExecutionContext();  
  const result = await ctx.exports.MyEntryPoint.myMethod();  
  expect(result).toBe("expected value");  
});  
```  
Alternatively, you can import `exports` directly from `cloudflare:workers`:

**TypeScript**  
```ts  
import { exports } from "cloudflare:workers";  
import { it, expect } from "vitest";  
it("can access imported exports", async () => {  
  const result = await exports.MyEntryPoint.myMethod();  
  expect(result).toBe("expected value");  
});  
```  
See the [context-exports fixture ↗](https://github.com/cloudflare/workers-sdk/tree/main/fixtures/vitest-pool-workers-examples/context-exports) for a complete example.

Dec 16, 2025
1. ### [Configure your framework for Cloudflare automatically](https://developers.cloudflare.com/changelog/post/2025-12-16-wrangler-autoconfig/)  
[ Workers ](https://developers.cloudflare.com/workers/)  
Wrangler now supports automatic configuration for popular web frameworks in experimental mode, making it even easier to deploy to Cloudflare Workers.  
Previously, if you wanted to deploy an application using a popular web framework like Next.js or Astro, you had to follow tutorials to set up your application for deployment to Cloudflare Workers. This usually involved creating a Wrangler file, installing adapters, or changing configuration options.  
Now `wrangler deploy` does this for you. Starting with Wrangler 4.55, you can use `npx wrangler deploy --x-autoconfig` in the directory of any web application using one of the supported frameworks. Wrangler will then proceed to configure and deploy it to your Cloudflare account.  
You can also configure your application without deploying it by using the new `npx wrangler setup` command. This enables you to easily review what changes we are making so your application is ready for Cloudflare Workers.  
The following application frameworks are supported starting today:

  * Next.js
  * Astro
  * Nuxt
  * TanStack Start
  * SolidStart
  * React Router
  * SvelteKit
  * Docusaurus
  * Qwik
  * Analog  
Automatic configuration also supports static sites by detecting the assets directory and build command. From a single index.html file to the output of a generator like Jekyll or Hugo, you can just run `npx wrangler deploy --x-autoconfig` to upload to Cloudflare.  
We're really excited to bring you automatic configuration so you can do more with Workers. Please let us know if you run into challenges using this experimentally. We’ve opened a [GitHub discussion ↗](https://github.com/cloudflare/workers-sdk/discussions/11667) and would love to hear your feedback.

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