---
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) 

Mar 10, 2026
1. ### [Crawl entire websites with a single API call using Browser Rendering](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-10-br-crawl-endpoint/)  
[ Browser Run ](https://edgetunnel-b2h.pages.dev/browser-run/)  
_Edit: this post has been edited to clarify crawling behavior with respect to site guidance._  
You can now crawl an entire website with a single API call using [Browser Rendering](https://edgetunnel-b2h.pages.dev/browser-run/)'s new [/crawl endpoint](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/crawl-endpoint/), available in open beta. Submit a starting URL, and pages are automatically discovered, rendered in a headless browser, and returned in multiple formats, including HTML, Markdown, and structured JSON. The endpoint is a [verified bot (intermediary agent)](https://edgetunnel-b2h.pages.dev/bots/concepts/bot/verified-bots/) that respects robots.txt and [AI Crawl Control ↗](https://www.cloudflare.com/ai-crawl-control/) by default, making it easy for developers to comply with website rules, and making it less likely for crawlers to ignore web-owner guidance. This is great for training models, building RAG pipelines, and researching or monitoring content across a site.  
Crawl jobs run asynchronously. You submit a URL, receive a job ID, and check back for results as pages are processed.  
```sh  
# Initiate a crawl  
curl -X POST 'https://api.cloudflare.com/client/v4/accounts/{account_id}/browser-rendering/crawl' \
  -H 'Authorization: Bearer <apiToken>' \
  -H 'Content-Type: application/json' \
  -d '{  
    "url": "https://blog.cloudflare.com/"  
  }'  
# Check results  
curl -X GET 'https://api.cloudflare.com/client/v4/accounts/{account_id}/browser-rendering/crawl/{job_id}' \
  -H 'Authorization: Bearer <apiToken>'  
```  
Key features:

  * **Multiple output formats** \- Return crawled content as HTML, Markdown, and structured JSON (powered by [Workers AI](https://edgetunnel-b2h.pages.dev/workers-ai/))
  * **Crawl scope controls** \- Configure crawl depth, page limits, and wildcard patterns to include or exclude specific URL paths
  * **Automatic page discovery** \- Discovers URLs from sitemaps, page links, or both
  * **Incremental crawling** \- Use `modifiedSince` and `maxAge` to skip pages that haven't changed or were recently fetched, saving time and cost on repeated crawls
  * **Static mode** \- Set `render: false` to fetch static HTML without spinning up a browser, for faster crawling of static sites
  * **Well-behaved bot** \- Honors `robots.txt` directives, including `crawl-delay`  
Available on both the Workers Free and Paid plans.

**Note**: the /crawl endpoint cannot bypass Cloudflare bot detection or captchas, and self-identifies as a bot.  
To get started, refer to the [crawl endpoint documentation](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/crawl-endpoint/). If you are setting up your own site to be crawled, review the [robots.txt and sitemaps best practices](https://edgetunnel-b2h.pages.dev/browser-run/reference/robots-txt/).

Mar 06, 2026
1. ### [Workflow steps now expose retry attempt number via step context](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-06-step-context-available/)  
[ Workflows ](https://edgetunnel-b2h.pages.dev/workflows/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
Cloudflare Workflows allows you to configure specific retry logic for each step in your workflow execution. Now, you can access **which** retry attempt is currently executing for calls to `step.do()`:

**TypeScript**  
```ts  
await step.do("my-step", async (ctx) => {  
  // ctx.attempt is 1 on first try, 2 on first retry, etc.  
  console.log(`Attempt ${ctx.attempt}`);  
});  
```  
You can use the step context for improved logging & observability, progressive backoff, or conditional logic in your workflow definition.  
Note that the current attempt number is 1-indexed. For more information on retry behavior, refer to [Sleeping and Retrying](https://edgetunnel-b2h.pages.dev/workflows/build/sleeping-and-retrying/).

Mar 06, 2026
1. ### [Real-time transcription in RealtimeKit now supports 10 languages with regional variants](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-06-realtimekit-multilingual-transcription/)  
[ Workers AI ](https://edgetunnel-b2h.pages.dev/workers-ai/)[ Realtime ](https://edgetunnel-b2h.pages.dev/realtime/)  
[Real-time transcription](https://edgetunnel-b2h.pages.dev/realtime/realtimekit/ai/transcription/) in RealtimeKit now supports 10 languages with regional variants, powered by [Deepgram Nova-3](https://edgetunnel-b2h.pages.dev/workers-ai/models/nova-3/) running on [Workers AI](https://edgetunnel-b2h.pages.dev/workers-ai/).  
During a meeting, participant audio is routed through [AI Gateway](https://edgetunnel-b2h.pages.dev/ai-gateway/) to Nova-3 on Workers AI — so transcription runs on Cloudflare's network end-to-end, reducing latency compared to routing through external speech-to-text services.  
Set the language when [creating a meeting](https://edgetunnel-b2h.pages.dev/realtime/realtimekit/concepts/meeting/) via `ai_config.transcription.language`:  
```json  
{  
  "ai_config": {  
    "transcription": {  
      "language": "fr"  
    }  
  }  
}  
```  
Supported languages include English, Spanish, French, German, Hindi, Russian, Portuguese, Japanese, Italian, and Dutch — with regional variants like `en-AU`, `en-GB`, `en-IN`, `en-NZ`, `es-419`, `fr-CA`, `de-CH`, `pt-BR`, and `pt-PT`. Use `multi` for automatic multilingual detection.  
If you are building voice agents or real-time translation workflows, your agent can now transcribe in the caller's language natively — no extra services or routing logic needed.

  * [Transcription docs](https://edgetunnel-b2h.pages.dev/realtime/realtimekit/ai/transcription/)
  * [Nova-3 model page](https://edgetunnel-b2h.pages.dev/workers-ai/models/nova-3/)
  * [Workers AI](https://edgetunnel-b2h.pages.dev/workers-ai/)
  * [AI Gateway](https://edgetunnel-b2h.pages.dev/ai-gateway/)

Mar 04, 2026
1. ### [Browser Rendering: 3x higher REST API request rate](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-04-br-rest-api-limit-increase/)  
[ Browser Run ](https://edgetunnel-b2h.pages.dev/browser-run/)  
[Browser Rendering](https://edgetunnel-b2h.pages.dev/browser-run/) REST API rate limits for Workers Paid plans have been increased from 3 requests per second (180/min) to **10 requests per second (600/min)**. No action is needed to benefit from the higher limit.  
![Browser Rendering REST API rate limit increased from 3 to 10 requests per second](https://edgetunnel-b2h.pages.dev/_astro/rest-api-limit-increase.DJHY7xYF_1U7IJn.webp)  
The [REST API](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/) lets you perform common browser tasks with a single API call, and you can now do it at a higher rate.

  * [/content - Fetch HTML](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/content-endpoint/)
  * [/screenshot - Capture screenshot](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/screenshot-endpoint/)
  * [/pdf - Render PDF](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/pdf-endpoint/)
  * [/markdown - Extract Markdown from a webpage](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/markdown-endpoint/)
  * [/snapshot - Take a webpage snapshot](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/snapshot/)
  * [/scrape - Scrape HTML elements](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/scrape-endpoint/)
  * [/json - Capture structured data using AI](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/json-endpoint/)
  * [/links - Retrieve links from a webpage](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/links-endpoint/)  
If you use the [Browser Sessions](https://edgetunnel-b2h.pages.dev/browser-run/#integration-methods) method, increases to concurrent browser and new browser limits are coming soon. Stay tuned.  
For full details, refer to the [Browser Rendering limits page](https://edgetunnel-b2h.pages.dev/browser-run/limits/).

Mar 04, 2026
1. ### [New conversion options for Markdown Conversion](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-04-new-markdown-conversion-options/)  
[ Workers AI ](https://edgetunnel-b2h.pages.dev/workers-ai/)  
You can now customize how the [Markdown Conversion](https://edgetunnel-b2h.pages.dev/workers-ai/features/markdown-conversion/) service processes different file types by passing a `conversionOptions` object.  
Available options:

  * **Images**: Set the language for AI-generated image descriptions
  * **HTML**: Use CSS selectors to extract specific content, or provide a hostname to resolve relative links
  * **PDF**: Exclude metadata from the output  
Use the [env.AI](https://edgetunnel-b2h.pages.dev/workers-ai/features/markdown-conversion/usage/binding/) binding:

  * [  JavaScript ](#tab-panel-3477)
  * [  TypeScript ](#tab-panel-3478)

**JavaScript**  
```js  
await env.AI.toMarkdown(  
  { name: "page.html", blob: new Blob([html]) },  
  {  
    conversionOptions: {  
      html: { cssSelector: "article.content" },  
      image: { descriptionLanguage: "es" },  
    },  
  },  
);  
```

**TypeScript**  
```ts  
await env.AI.toMarkdown(  
  { name: "page.html", blob: new Blob([html]) },  
  {  
    conversionOptions: {  
      html: { cssSelector: "article.content" },  
      image: { descriptionLanguage: "es" },  
    },  
  },  
);  
```  
Or call the REST API:  
```bash  
curl https://api.cloudflare.com/client/v4/accounts/{ACCOUNT_ID}/ai/tomarkdown \
  -H 'Authorization: Bearer {API_TOKEN}' \
  -F 'files=@index.html' \
  -F 'conversionOptions={"html": {"cssSelector": "article.content"}}'  
```  
For more details, refer to [Conversion Options](https://edgetunnel-b2h.pages.dev/workers-ai/features/markdown-conversion/conversion-options/).

Mar 03, 2026
1. ### [Workflows step limit increased to 25,000 steps per instance](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-03-step-limits-to-25k/)  
[ Workflows ](https://edgetunnel-b2h.pages.dev/workflows/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
Each Workflow on Workers Paid now supports 10,000 steps by default, configurable up to 25,000 steps in your `wrangler.jsonc` file:  
```json  
{  
  "workflows": [  
    {  
      "name": "my-workflow",  
      "binding": "MY_WORKFLOW",  
      "class_name": "MyWorkflow",  
      "limits": {  
        "steps": 25000  
      }  
    }  
  ]  
}  
```  
Previously, each instance was limited to 1,024 steps. Now, Workflows can support more complex, long-running executions without the additional complexity of recursive or child workflow calls.  
Note that the maximum persisted state limit per Workflow instance remains **100 MB** for Workers Free and **1 GB** for Workers Paid. Refer to [Workflows limits](https://edgetunnel-b2h.pages.dev/workflows/reference/limits/) for more information.

Mar 03, 2026
1. ### [Real-time file watching in Sandboxes](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-03-sandbox-watch-file-events/)  
[ Agents ](https://edgetunnel-b2h.pages.dev/agents/)  
[Sandboxes](https://edgetunnel-b2h.pages.dev/sandbox/) now support real-time filesystem watching via `sandbox.watch()`. The method returns a [Server-Sent Events ↗](https://developer.mozilla.org/en-US/docs/Web/API/Server-sent%5Fevents) stream backed by native inotify, so your Worker receives `create`, `modify`, `delete`, and `move` events as they happen inside the container.  
#### `sandbox.watch(path, options)`  
Pass a directory path and optional filters. The returned stream is a standard `ReadableStream` you can proxy directly to a browser client or consume server-side.

  * [  JavaScript ](#tab-panel-3479)
  * [  TypeScript ](#tab-panel-3480)

**JavaScript**  
```js  
// Stream events to a browser client  
const stream = await sandbox.watch("/workspace/src", {  
  recursive: true,  
  include: ["*.ts", "*.js"],  
});  
return new Response(stream, {  
  headers: { "Content-Type": "text/event-stream" },  
});  
```

**TypeScript**  
```ts  
// Stream events to a browser client  
const stream = await sandbox.watch("/workspace/src", {  
  recursive: true,  
  include: ["*.ts", "*.js"],  
});  
return new Response(stream, {  
  headers: { "Content-Type": "text/event-stream" },  
});  
```  
#### Server-side consumption with `parseSSEStream`  
Use `parseSSEStream` to iterate over events inside a Worker without forwarding them to a client.

  * [  JavaScript ](#tab-panel-3481)
  * [  TypeScript ](#tab-panel-3482)

**JavaScript**  
```js  
import { parseSSEStream } from "@cloudflare/sandbox";  
const stream = await sandbox.watch("/workspace/src", { recursive: true });  
for await (const event of parseSSEStream(stream)) {  
  console.log(event.type, event.path);  
}  
```

**TypeScript**  
```ts  
import { parseSSEStream } from "@cloudflare/sandbox";  
import type { FileWatchSSEEvent } from "@cloudflare/sandbox";  
const stream = await sandbox.watch("/workspace/src", { recursive: true });  
for await (const event of parseSSEStream<FileWatchSSEEvent>(stream)) {  
  console.log(event.type, event.path);  
}  
```  
Each event includes a `type` field (`create`, `modify`, `delete`, or `move`) and the affected `path`. Move events also include a `from` field with the original path.  
#### Options

| Option    | Type       | Description                                                 |
| --------- | ---------- | ----------------------------------------------------------- |
| recursive | boolean    | Watch subdirectories. Defaults to false.                    |
| include   | string\[\] | Glob patterns to filter events. Omit to receive all events. |  
#### Upgrade  
To update to the latest version:  
```sh  
npm i @cloudflare/sandbox@latest  
```  
For full API details, refer to the [Sandbox file watching reference](https://edgetunnel-b2h.pages.dev/sandbox/api/file-watching/).

Mar 02, 2026
1. ### [Agents SDK v0.7.0: Observability rewrite, keepAlive, and waitForMcpConnections](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-02-agents-sdk-v070/)  
[ Agents ](https://edgetunnel-b2h.pages.dev/agents/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
The latest release of the [Agents SDK ↗](https://github.com/cloudflare/agents) rewrites observability from scratch with `diagnostics_channel`, adds `keepAlive()` to prevent Durable Object eviction during long-running work, and introduces `waitForMcpConnections` so MCP tools are always available when `onChatMessage` runs.  
#### Observability rewrite  
The previous observability system used `console.log()` with a custom `Observability.emit()` interface. v0.7.0 replaces it with structured events published to [diagnostics channels](https://edgetunnel-b2h.pages.dev/workers/runtime-apis/nodejs/diagnostics-channel/) — silent by default, zero overhead when nobody is listening.  
Every event has a `type`, `payload`, and `timestamp`. Events are routed to seven named channels:

| Channel          | Event types                                                                                                                                      |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| agents:state     | state:update                                                                                                                                     |
| agents:rpc       | rpc, rpc:error                                                                                                                                   |
| agents:message   | message:request, message:response, message:clear, message:cancel, message:error, tool:result, tool:approval                                      |
| agents:schedule  | schedule:create, schedule:execute, schedule:cancel, schedule:retry, schedule:error, queue:retry, queue:error                                     |
| agents:lifecycle | connect, destroy                                                                                                                                 |
| agents:workflow  | workflow:start, workflow:event, workflow:approved, workflow:rejected, workflow:terminated, workflow:paused, workflow:resumed, workflow:restarted |
| agents:mcp       | mcp:client:preconnect, mcp:client:connect, mcp:client:authorize, mcp:client:discover                                                             |  
Use the typed `subscribe()` helper from `agents/observability` for type-safe access:

  * [  JavaScript ](#tab-panel-3491)
  * [  TypeScript ](#tab-panel-3492)

**JavaScript**  
```js  
import { subscribe } from "agents/observability";  
const unsub = subscribe("rpc", (event) => {  
  if (event.type === "rpc") {  
    console.log(`RPC call: ${event.payload.method}`);  
  }  
  if (event.type === "rpc:error") {  
    console.error(  
      `RPC failed: ${event.payload.method} — ${event.payload.error}`,  
    );  
  }  
});  
// Clean up when done  
unsub();  
```

**TypeScript**  
```ts  
import { subscribe } from "agents/observability";  
const unsub = subscribe("rpc", (event) => {  
  if (event.type === "rpc") {  
    console.log(`RPC call: ${event.payload.method}`);  
  }  
  if (event.type === "rpc:error") {  
    console.error(  
      `RPC failed: ${event.payload.method} — ${event.payload.error}`,  
    );  
  }  
});  
// Clean up when done  
unsub();  
```  
In production, all diagnostics channel messages are automatically forwarded to [Tail Workers](https://edgetunnel-b2h.pages.dev/workers/observability/logs/tail-workers/) — no subscription code needed in the agent itself:

  * [  JavaScript ](#tab-panel-3487)
  * [  TypeScript ](#tab-panel-3488)

**JavaScript**  
```js  
export default {  
  async tail(events) {  
    for (const event of events) {  
      for (const msg of event.diagnosticsChannelEvents) {  
        // msg.channel is "agents:rpc", "agents:workflow", etc.  
        console.log(msg.timestamp, msg.channel, msg.message);  
      }  
    }  
  },  
};  
```

**TypeScript**  
```ts  
export default {  
  async tail(events) {  
    for (const event of events) {  
      for (const msg of event.diagnosticsChannelEvents) {  
        // msg.channel is "agents:rpc", "agents:workflow", etc.  
        console.log(msg.timestamp, msg.channel, msg.message);  
      }  
    }  
  },  
};  
```  
The custom `Observability` override interface is still supported for users who need to filter or forward events to external services.  
For the full event reference, refer to the [Observability documentation](https://edgetunnel-b2h.pages.dev/agents/runtime/operations/observability/).  
#### `keepAlive()` and `keepAliveWhile()`  
Durable Objects are evicted after a period of inactivity (typically 70-140 seconds with no incoming requests, WebSocket messages, or alarms). During long-running operations — streaming LLM responses, waiting on external APIs, running multi-step computations — the agent can be evicted mid-flight.  
`keepAlive()` prevents this by creating a 30-second heartbeat schedule. The alarm firing resets the inactivity timer. Returns a disposer function that cancels the heartbeat when called.

  * [  JavaScript ](#tab-panel-3485)
  * [  TypeScript ](#tab-panel-3486)

**JavaScript**  
```js  
const dispose = await this.keepAlive();  
try {  
  const result = await longRunningComputation();  
  await sendResults(result);  
} finally {  
  dispose();  
}  
```

**TypeScript**  
```ts  
const dispose = await this.keepAlive();  
try {  
  const result = await longRunningComputation();  
  await sendResults(result);  
} finally {  
  dispose();  
}  
```  
`keepAliveWhile()` wraps an async function with automatic cleanup — the heartbeat starts before the function runs and stops when it completes:

  * [  JavaScript ](#tab-panel-3483)
  * [  TypeScript ](#tab-panel-3484)

**JavaScript**  
```js  
const result = await this.keepAliveWhile(async () => {  
  const data = await longRunningComputation();  
  return data;  
});  
```

**TypeScript**  
```ts  
const result = await this.keepAliveWhile(async () => {  
  const data = await longRunningComputation();  
  return data;  
});  
```  
Key details:

  * **Multiple concurrent callers** — Each `keepAlive()` call returns an independent disposer. Disposing one does not affect others.
  * **AIChatAgent built-in** — `AIChatAgent` automatically calls `keepAlive()` during streaming responses. You do not need to add it yourself.
  * **Uses the scheduling system** — The heartbeat does not conflict with your own schedules. It shows up in `getSchedules()` if you need to inspect it.  
Note  
`keepAlive()` is marked `@experimental` and may change between releases.  
For the full API reference and when-to-use guidance, refer to [Schedule tasks — Keeping the agent alive](https://edgetunnel-b2h.pages.dev/agents/runtime/execution/schedule-tasks/#keeping-the-agent-alive).  
#### `waitForMcpConnections`  
`AIChatAgent` now waits for MCP server connections to settle before calling `onChatMessage`. This ensures `this.mcp.getAITools()` returns the full set of tools, especially after Durable Object hibernation when connections are being restored in the background.

  * [  JavaScript ](#tab-panel-3493)
  * [  TypeScript ](#tab-panel-3494)

**JavaScript**  
```js  
export class ChatAgent extends AIChatAgent {  
  // Default — waits up to 10 seconds  
  // waitForMcpConnections = { timeout: 10_000 };  
  // Wait forever  
  waitForMcpConnections = true;  
  // Disable waiting  
  waitForMcpConnections = false;  
}  
```

**TypeScript**  
```ts  
export class ChatAgent extends AIChatAgent {  
  // Default — waits up to 10 seconds  
  // waitForMcpConnections = { timeout: 10_000 };  
  // Wait forever  
  waitForMcpConnections = true;  
  // Disable waiting  
  waitForMcpConnections = false;  
}  
```

| Value                | Behavior                                      |
| -------------------- | --------------------------------------------- |
| { timeout: 10\_000 } | Wait up to 10 seconds (default)               |
| { timeout: N }       | Wait up to N milliseconds                     |
| true                 | Wait indefinitely until all connections ready |
| false                | Do not wait (old behavior before 0.2.0)       |  
For lower-level control, call `this.mcp.waitForConnections()` directly inside `onChatMessage` instead.  
#### Other improvements

  * **MCP deduplication by name and URL** — `addMcpServer` with HTTP transport now deduplicates on both server name and URL. Calling it with the same name but a different URL creates a new connection. URLs are normalized before comparison (trailing slashes, default ports, hostname case).
  * **`callbackHost` optional for non-OAuth servers** — `addMcpServer` no longer requires `callbackHost` when connecting to MCP servers that do not use OAuth.
  * **MCP URL security** — Server URLs are validated before connection to prevent SSRF. Private IP ranges, loopback addresses, link-local addresses, and cloud metadata endpoints are blocked.
  * **Custom denial messages** — `addToolOutput` now supports `state: "output-error"` with `errorText` for custom denial messages in human-in-the-loop tool approval flows.
  * **`requestId` in chat options** — `onChatMessage` options now include a `requestId` for logging and correlating events.  
#### Upgrade  
To update to the latest version:  
```sh  
npm i agents@latest @cloudflare/ai-chat@latest  
```

Mar 02, 2026
1. ### [Get started with AI Gateway automatically](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-02-default-gateway/)  
[ AI Gateway ](https://edgetunnel-b2h.pages.dev/ai-gateway/)  
You can now start using AI Gateway with a single API call — no setup required. Use `default` as your gateway ID, and AI Gateway creates one for you automatically on the first request.  
To try it out, [create an API token](https://edgetunnel-b2h.pages.dev/fundamentals/api/get-started/create-token/) with `AI Gateway - Read`, `AI Gateway - Edit`, and `Workers AI - Read` permissions, then run:  
```bash  
curl -X POST https://gateway.ai.cloudflare.com/v1/$CLOUDFLARE_ACCOUNT_ID/default/compat/chat/completions \
  --header "cf-aig-authorization: Bearer $CLOUDFLARE_API_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{  
    "model": "workers-ai/@cf/meta/llama-3.3-70b-instruct-fp8-fast",  
    "messages": [  
      {  
        "role": "user",  
        "content": "What is Cloudflare?"  
      }  
    ]  
  }'  
```  
AI Gateway gives you logging, caching, rate limiting, and access to multiple AI providers through a single endpoint. For more information, refer to [Get started](https://edgetunnel-b2h.pages.dev/ai-gateway/get-started/).

Feb 25, 2026
1. ### [Agents SDK v0.6.0: RPC transport for MCP, optional OAuth, hardened schema conversion, and @cloudflare/ai-chat fixes](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-25-agents-sdk-v060/)  
[ Agents ](https://edgetunnel-b2h.pages.dev/agents/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
The latest release of the [Agents SDK ↗](https://github.com/cloudflare/agents) lets you define an Agent and an McpAgent in the same Worker and connect them over RPC — no HTTP, no network overhead. It also makes OAuth opt-in for simple MCP connections, hardens the schema converter for production workloads, and ships a batch of `@cloudflare/ai-chat` reliability fixes.  
#### RPC transport for MCP  
You can now connect an Agent to an McpAgent in the same Worker using a Durable Object binding instead of an HTTP URL. The connection stays entirely within the Cloudflare runtime — no network round-trips, no serialization overhead.  
Pass the Durable Object namespace directly to `addMcpServer`:

  * [  JavaScript ](#tab-panel-3495)
  * [  TypeScript ](#tab-panel-3496)

**JavaScript**  
```js  
import { Agent } from "agents";  
export class MyAgent extends Agent {  
  async onStart() {  
    // Connect via DO binding — no HTTP, no network overhead  
    await this.addMcpServer("counter", env.MY_MCP);  
    // With props for per-user context  
    await this.addMcpServer("counter", env.MY_MCP, {  
      props: { userId: "user-123", role: "admin" },  
    });  
  }  
}  
```

**TypeScript**  
```ts  
import { Agent } from "agents";  
export class MyAgent extends Agent {  
  async onStart() {  
    // Connect via DO binding — no HTTP, no network overhead  
    await this.addMcpServer("counter", env.MY_MCP);  
    // With props for per-user context  
    await this.addMcpServer("counter", env.MY_MCP, {  
      props: { userId: "user-123", role: "admin" },  
    });  
  }  
}  
```  
The `addMcpServer` method now accepts `string | DurableObjectNamespace` as the second parameter with full TypeScript overloads, so HTTP and RPC paths are type-safe and cannot be mixed.  
Key capabilities:

  * **Hibernation support** — RPC connections survive Durable Object hibernation automatically. The binding name and props are persisted to storage and restored on wake-up, matching the behavior of HTTP MCP connections.
  * **Deduplication** — Calling `addMcpServer` with the same server name returns the existing connection instead of creating duplicates. Connection IDs are stable across hibernation restore.
  * **Smaller surface area** — The RPC transport internals have been rewritten and reduced from 609 lines to 245 lines. `RPCServerTransport` now uses `JSONRPCMessageSchema` from the MCP SDK for validation instead of hand-written checks.  
Note  
RPC transport is experimental. The API may change based on feedback. Refer to [the tracking issue ↗](https://github.com/cloudflare/agents/issues/565) for updates.  
#### Optional OAuth for MCP connections  
`addMcpServer()` no longer eagerly creates an OAuth provider for every connection. For servers that do not require authentication, a simple call is all you need:

  * [  JavaScript ](#tab-panel-3489)
  * [  TypeScript ](#tab-panel-3490)

**JavaScript**  
```js  
// No callbackHost, no OAuth config — just works  
await this.addMcpServer("my-server", "https://mcp.example.com");  
```

**TypeScript**  
```ts  
// No callbackHost, no OAuth config — just works  
await this.addMcpServer("my-server", "https://mcp.example.com");  
```  
If the server responds with a 401, the SDK throws a clear error: `"This MCP server requires OAuth authentication. Provide callbackHost in addMcpServer options to enable the OAuth flow."` The restore-from-storage flow also handles missing callback URLs gracefully, skipping auth provider creation for non-OAuth servers.  
#### Hardened JSON Schema to TypeScript converter  
The schema converter used by `generateTypes()` and `getAITools()` now handles edge cases that previously caused crashes in production:

  * **Depth and circular reference guards** — Prevents stack overflows on recursive or deeply nested schemas
  * **`$ref` resolution** — Supports internal JSON Pointers (`#/definitions/...`, `#/$defs/...`, `#`)
  * **Tuple support** — `prefixItems` (JSON Schema 2020-12) and array `items` (draft-07)
  * **OpenAPI 3.0 `nullable: true`** — Supported across all schema branches
  * **Per-tool error isolation** — One malformed schema cannot crash the full pipeline in `generateTypes()` or `getAITools()`
  * **Missing `inputSchema` fallback** — `getAITools()` falls back to `{ type: "object" }` instead of throwing  
#### `@cloudflare/ai-chat` fixes

  * **Tool denial flow** — Denied tool approvals (`approved: false`) now transition to `output-denied` with a `tool_result`, fixing Anthropic provider compatibility. Custom denial messages are supported via `state: "output-error"` and `errorText`.
  * **Abort/cancel support** — Streaming responses now properly cancel the reader loop when the abort signal fires and send a done signal to the client.
  * **Duplicate message persistence** — `persistMessages()` now reconciles assistant messages by content and order, preventing duplicate rows when clients resend full history.
  * **`requestId` in `OnChatMessageOptions`** — Handlers can now send properly-tagged error responses for pre-stream failures.
  * **`redacted_thinking` preservation** — The message sanitizer no longer strips Anthropic `redacted_thinking` blocks.
  * **`/get-messages` reliability** — Endpoint handling moved from a prototype `onRequest()` override to a constructor wrapper, so it works even when users override `onRequest` without calling `super.onRequest()`.
  * **Client tool APIs undeprecated** — `createToolsFromClientSchemas`, `clientTools`, `AITool`, `extractClientToolSchemas`, and the `tools` option on `useAgentChat` are restored for SDK use cases where tools are defined dynamically at runtime.
  * **`jsonSchema` initialization** — Fixed `jsonSchema not initialized` error when calling `getAITools()` in `onChatMessage`.  
#### Upgrade  
To update to the latest version:  
```sh  
npm i agents@latest @cloudflare/ai-chat@latest  
```

Feb 25, 2026
1. ### [Run 15x more Containers with higher resource limits](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-25-higher-container-resource-limits/)  
[ Containers ](https://edgetunnel-b2h.pages.dev/containers/)  
You can now run more [Containers](https://edgetunnel-b2h.pages.dev/containers/) concurrently with significantly higher limits on memory, vCPU, and disk.

| Limit                                          | Previous Limit | New Limit |
| ---------------------------------------------- | -------------- | --------- |
| Memory for concurrent live Container instances | 400GiB         | 6TiB      |
| vCPU for concurrent live Container instances   | 100            | 1,500     |
| Disk for concurrent live Container instances   | 2TB            | 30TB      |  
This 15x increase enables larger-scale workloads on Containers. You can now run 15,000 instances of the `lite` instance type, 6,000 instances of `basic`, over 1,500 instances of `standard-1`, or over 1,000 instances of `standard-2` concurrently.  
Refer to [Limits](https://edgetunnel-b2h.pages.dev/containers/platform-details/limits/) for more details on the available instance types and limits.

Feb 25, 2026
1. ### [Better Windows support for Python Workers](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-13-pywrangler-windows-support/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
[Pywrangler ↗](https://github.com/cloudflare/workers-py?tab=readme-ov-file#pywrangler), the CLI tool for managing Python Workers and packages, now supports Windows, allowing you to develop and deploy Python Workers from Windows environments. Previously, Pywrangler was only available on macOS and Linux.  
You can install and use Pywrangler on Windows the same way you would on other platforms. [Specify your Worker's Python dependencies](https://edgetunnel-b2h.pages.dev/workers/languages/python/packages/) in your `pyproject.toml` file, then use the following commands to develop and deploy:  
```bash  
uvx --from workers-py pywrangler dev  
uvx --from workers-py pywrangler deploy  
```  
All existing Pywrangler functionality, including package management, local development, and deployment, works on Windows without any additional configuration.  
#### Requirements  
This feature requires the following minimum versions:

  * `wrangler` \>= 4.64.0
  * `workers-py` \>= 1.72.0
  * `uv` \>= 0.29.8  
To upgrade `workers-py` (which includes Pywrangler) in your project, run:  
```bash  
uv tool upgrade workers-py  
```  
To upgrade `wrangler`, run:  
```bash  
npm install -g wrangler@latest  
```  
To upgrade `uv`, run:  
```bash  
uv self update  
```  
To get started with Python Workers on Windows, refer to the [Python packages documentation](https://edgetunnel-b2h.pages.dev/workers/languages/python/packages/) for full details on Pywrangler.

Feb 25, 2026
1. ### [Write structured queries to filter and search your Workers logs and traces](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-24-observability-query-language/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
[Workers Observability](https://edgetunnel-b2h.pages.dev/workers/observability/) now includes a query language that lets you write structured queries directly in the search bar to filter your logs and traces. The search bar doubles as a free text search box — type any term to search across all metadata and attributes, or write field-level queries for precise filtering.  
![Workers Observability search bar with autocomplete suggestions and Query Builder sidebar filters](https://edgetunnel-b2h.pages.dev/_astro/2026-02-24-query-language.Ol8UX7m0_ZqdMnt.webp)  
Queries written in the search bar sync with the [Query Builder](https://edgetunnel-b2h.pages.dev/workers/observability/) sidebar, so you can write a query by hand and then refine it visually, or build filters in the Query Builder and see the corresponding query syntax. The search bar provides autocomplete suggestions for metadata fields and operators as you type.  
The query language supports:

  * **Free text search** — search everywhere with a keyword like `error`, or match an exact phrase with `"exact phrase"`
  * **Field queries** — filter by specific fields using comparison operators (for example, `status = 500` or `$workers.wallTimeMs > 100`)
  * **Operators** — `=`, `!=`, `>`, `>=`, `<`, `<=`, and `:` (contains)
  * **Functions** — `contains(field, value)`, `startsWith(field, prefix)`, `regex(field, pattern)`, and `exists(field)`
  * **Boolean logic** — add conditions with `AND`, `OR`, and `NOT`  
Select the help icon next to the search bar to view the full syntax reference, including all supported operators, functions, and keyboard shortcuts.  
Go to the [Workers Observability dashboard ↗](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/) to try the query language.

Feb 25, 2026
1. ### [No config? No problem. Just \`wrangler deploy\`](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-25-wrangler-autoconfig-ga/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
You can now deploy any existing project to Cloudflare Workers — even without a Wrangler configuration file — and `wrangler deploy` will _just work_.  
Starting with Wrangler **4.68.0**, running [wrangler deploy](https://edgetunnel-b2h.pages.dev/workers/wrangler/commands/general/#deploy) [automatically configures your project](https://edgetunnel-b2h.pages.dev/workers/framework-guides/automatic-configuration/) by detecting your framework, installing required adapters, and deploying it to Cloudflare Workers.  
#### Using Wrangler locally  
```sh  
npx wrangler deploy  
```  
When you run `wrangler deploy` in a project without a configuration file, Wrangler:

  1. Detects your framework from `package.json`
  2. Prompts you to confirm the detected settings
  3. Installs any required adapters
  4. Generates a `wrangler.jsonc` [configuration file](https://edgetunnel-b2h.pages.dev/workers/wrangler/configuration/)
  5. Deploys your project to Cloudflare Workers  
You can also use [wrangler setup](https://edgetunnel-b2h.pages.dev/workers/wrangler/commands/general/#setup) to configure without deploying, or pass [\--yes](https://edgetunnel-b2h.pages.dev/workers/wrangler/commands/general/#deploy) to skip prompts.  
#### Using the Cloudflare dashboard  
![Automatic configuration pull request created by Workers Builds](https://edgetunnel-b2h.pages.dev/_astro/automatic-pr.CwJG6Bec_1cC506.webp)  
When you connect a repository through the [Workers dashboard ↗](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create), a [pull request is generated](https://edgetunnel-b2h.pages.dev/workers/ci-cd/builds/automatic-prs/) for you with all necessary files, and a [preview deployment](https://edgetunnel-b2h.pages.dev/workers/versions-and-deployments/preview-urls/) to check before merging.  
Note  
A pull request is only generated when your deploy command is `npx wrangler deploy`. If you use a custom deploy command, automatic configuration still runs but a PR is not created.  
#### Background  
In December 2025, we [introduced automatic configuration](https://edgetunnel-b2h.pages.dev/changelog/2025-12-16-wrangler-autoconfig/) as an experimental feature. It is now generally available and the default behavior.  
If you have questions or run into issues, join the [GitHub discussion ↗](https://github.com/cloudflare/workers-sdk/discussions/11667).

Feb 24, 2026
1. ### [deleteAll() now deletes Durable Object alarm](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-24-deleteall-deletes-alarms/)  
[ Durable Objects ](https://edgetunnel-b2h.pages.dev/durable-objects/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
`deleteAll()` now deletes a Durable Object alarm in addition to stored data for Workers with a compatibility date of `2026-02-24` or later. This change simplifies clearing a Durable Object's storage with a single API call.  
Previously, `deleteAll()` only deleted user-stored data for an object. Alarm usage stores metadata in an object's storage, which required a separate `deleteAlarm()` call to fully clean up all storage for an object. The `deleteAll()` change applies to both KV-backed and SQLite-backed Durable Objects.

**JavaScript**  
```js  
// Before: two API calls required to clear all storage  
await this.ctx.storage.deleteAlarm();  
await this.ctx.storage.deleteAll();  
// Now: a single call clears both data and the alarm  
await this.ctx.storage.deleteAll();  
```  
For more information, refer to the [Storage API documentation](https://edgetunnel-b2h.pages.dev/durable-objects/api/sqlite-storage-api/#deleteall).

Feb 24, 2026
1. ### [Dropped event metrics, typed Pipelines bindings, and improved setup](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-24-typed-bindings-setup-improvements-error-metrics/)  
[ Pipelines ](https://edgetunnel-b2h.pages.dev/pipelines/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
[Cloudflare Pipelines](https://edgetunnel-b2h.pages.dev/pipelines/) ingests streaming data via [Workers](https://edgetunnel-b2h.pages.dev/workers/) or HTTP endpoints, transforms it with SQL, and writes it to [R2](https://edgetunnel-b2h.pages.dev/r2/) as Apache Iceberg tables. Today we're shipping three improvements to help you understand why streaming events get dropped, catch data quality issues early, and set up Pipelines faster.  
#### Dropped event metrics  
When [stream](https://edgetunnel-b2h.pages.dev/pipelines/streams/) events don't match the expected schema, Pipelines accepts them during ingestion but drops them when attempting to deliver them to the [sink](https://edgetunnel-b2h.pages.dev/pipelines/sinks/). To help you identify the root cause of these issues, we are introducing a new dashboard and metrics that surface dropped events with detailed error messages.  
![The Errors tab in the Cloudflare dashboard showing deserialization errors grouped by type with individual error details](https://edgetunnel-b2h.pages.dev/_astro/pipelines-error-log-dash.6JIa7r5d_Z1ILPxd.webp)  
Dropped events can also be queried programmatically via the new `pipelinesUserErrorsAdaptiveGroups` GraphQL dataset. The dataset breaks down failures by specific error type (`missing_field`, `type_mismatch`, `parse_failure`, or `null_value`) so you can trace issues back to the source.  
```graphql  
query GetPipelineUserErrors(  
  $accountTag: String!  
  $pipelineId: String!  
  $datetimeStart: Time!  
  $datetimeEnd: Time!  
) {  
  viewer {  
    accounts(filter: { accountTag: $accountTag }) {  
      pipelinesUserErrorsAdaptiveGroups(  
        limit: 100  
        filter: {  
          pipelineId: $pipelineId  
          datetime_geq: $datetimeStart  
          datetime_leq: $datetimeEnd  
        }  
        orderBy: [count_DESC]  
      ) {  
        count  
        dimensions {  
          errorFamily  
          errorType  
        }  
      }  
    }  
  }  
}  
```  
For the full list of dimensions, error types, and additional query examples, refer to [User error metrics](https://edgetunnel-b2h.pages.dev/pipelines/observability/metrics/#user-error-metrics).  
#### Typed Pipelines bindings  
Sending data to a Pipeline from a Worker previously used a generic `Pipeline<PipelineRecord>` type, which meant schema mismatches (wrong field names, incorrect types) were only caught at runtime as dropped events.  
Running `wrangler types` now generates schema-specific TypeScript types for your [Pipeline bindings](https://edgetunnel-b2h.pages.dev/pipelines/streams/writing-to-streams/#send-via-workers). TypeScript catches missing required fields and incorrect field types at compile time, before your code is deployed.

**TypeScript**  
```ts  
declare namespace Cloudflare {  
  type EcommerceStreamRecord = {  
    user_id: string;  
    event_type: string;  
    product_id?: string;  
    amount?: number;  
  };  
  interface Env {  
    STREAM: import("cloudflare:pipelines").Pipeline<Cloudflare.EcommerceStreamRecord>;  
  }  
}  
```  
For more information, refer to [Typed Pipeline bindings](https://edgetunnel-b2h.pages.dev/pipelines/streams/writing-to-streams/#typed-pipeline-bindings).  
#### Improved Pipelines setup  
Setting up a new Pipeline previously required multiple manual steps: creating an R2 bucket, enabling R2 Data Catalog, generating an API token, and configuring format, compression, and rolling policies individually.  
The `wrangler pipelines setup` command now offers a **Simple** setup mode that applies recommended defaults and automatically creates the [R2 bucket](https://edgetunnel-b2h.pages.dev/r2/buckets/) and enables [R2 Data Catalog](https://edgetunnel-b2h.pages.dev/r2/data-catalog/) if they do not already exist. Validation errors during setup prompt you to retry inline rather than restarting the entire process.  
For a full walkthrough, refer to the [Getting started guide](https://edgetunnel-b2h.pages.dev/pipelines/getting-started/).

Feb 24, 2026
1. ### [Stream live inputs can now be disabled and enabled](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-24-disable-live-inputs/)  
[ Stream ](https://edgetunnel-b2h.pages.dev/stream/)  
You can now disable a live input to reject incoming RTMPS and SRT connections. When a live input is disabled, any broadcast attempts will fail to connect.  
This gives you more control over your live inputs:

  * Temporarily pause an input without deleting it
  * Programmatically end creator broadcasts
  * Prevent new broadcasts from starting on a specific input  
To disable a live input via the API, set the `enabled` property to `false`:  
```bash  
curl --request PUT \  
https://api.cloudflare.com/client/v4/accounts/{account_id}/stream/live_inputs/{input_id} \
--header "Authorization: Bearer <API_TOKEN>" \
--data '{"enabled": false}'  
```  
You can also disable or enable a live input from the **Live inputs** list page or the live input detail page in the Dashboard.  
All existing live inputs remain enabled by default. For more information, refer to [Start a live stream](https://edgetunnel-b2h.pages.dev/stream/stream-live/start-stream-live/).

Feb 23, 2026
1. ### [Backup and restore API for Sandbox SDK](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-23-sandbox-backup-restore-api/)  
[ Agents ](https://edgetunnel-b2h.pages.dev/agents/)[ R2 ](https://edgetunnel-b2h.pages.dev/r2/)[ Containers ](https://edgetunnel-b2h.pages.dev/containers/)  
[Sandboxes](https://edgetunnel-b2h.pages.dev/sandbox/) now support `createBackup()` and `restoreBackup()` methods for creating and restoring point-in-time snapshots of directories.  
This allows you to restore environments quickly. For instance, in order to develop in a sandbox, you may need to include a user's codebase and run a build step. Unfortunately `git clone` and `npm install` can take minutes, and you don't want to run these steps every time the user starts their sandbox.  
Now, after the initial setup, you can just call `createBackup()`, then `restoreBackup()` the next time this environment is needed. This makes it practical to pick up exactly where a user left off, even after days of inactivity, without repeating expensive setup steps.

**TypeScript**  
```ts  
const sandbox = getSandbox(env.Sandbox, "my-sandbox");  
// Make non-trivial changes to the file system  
await sandbox.gitCheckout(endUserRepo, { targetDir: "/workspace" });  
await sandbox.exec("npm install", { cwd: "/workspace" });  
// Create a point-in-time backup of the directory  
const backup = await sandbox.createBackup({ dir: "/workspace" });  
// Store the handle for later use  
await env.KV.put(`backup:${userId}`, JSON.stringify(backup));  
// ... in a future session...  
// Restore instead of re-cloning and reinstalling  
await sandbox.restoreBackup(backup);  
```  
Backups are stored in [R2](https://edgetunnel-b2h.pages.dev/r2) and can take advantage of [R2 object lifecycle rules](https://edgetunnel-b2h.pages.dev/sandbox/guides/backup-restore/#configure-r2-lifecycle-rules-for-automatic-cleanup) to ensure they do not persist forever.  
Key capabilities:

  * **Persist and reuse across sandbox sessions** — Easily store backup handles in KV, D1, or Durable Object storage for use in subsequent sessions
  * **Usable across multiple instances** — Fork a backup across many sandboxes for parallel work
  * **Named backups** — Provide optional human-readable labels for easier management
  * **TTLs** — Set time-to-live durations so backups are automatically removed from storage once they are no longer needed  
Note  
Backup and restore currently uses a FUSE overlay. Soon, native snapshotting at a lower level will be added to Containers and Sandboxes, improving speed and ergonomics. The current backup functionality provides a significant speed improvement over manually recreating a file system, but it will be further optimized in the future. The new snapshotting system will use a similar API, so changing to this system will be simple once it is available.  
To get started, refer to the [backup and restore guide](https://edgetunnel-b2h.pages.dev/sandbox/guides/backup-restore/) for setup instructions and usage patterns, or the [Backups API reference](https://edgetunnel-b2h.pages.dev/sandbox/api/backups/) for full method documentation.

Feb 23, 2026
1. ### [Hyperdrive no longer caches queries using STABLE PostgreSQL functions](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-23-hyperdrive-stable-functions-uncacheable/)  
[ Hyperdrive ](https://edgetunnel-b2h.pages.dev/hyperdrive/)  
Hyperdrive now treats queries containing PostgreSQL `STABLE` functions as uncacheable, in addition to `VOLATILE` functions.  
Previously, only functions [that PostgreSQL categorizes ↗](https://www.postgresql.org/docs/current/xfunc-volatility.html) as `VOLATILE` (for example, `RANDOM()`, `LASTVAL()`) were detected as uncacheable. `STABLE` functions (for example, `NOW()`, `CURRENT_TIMESTAMP`, `CURRENT_DATE`) were incorrectly allowed to be cached.  
Because `STABLE` functions can return different results across different SQL statements within the same transaction, caching their results could serve stale or incorrect data. This change aligns Hyperdrive's caching behavior with PostgreSQL's function volatility semantics.  
If your queries use `STABLE` functions, and you were relying on them being cached, move the function call to your application code and pass the result as a query parameter. For example, instead of `WHERE created_at > NOW()`, compute the timestamp in your Worker and pass it as `WHERE created_at > $1`.  
Hyperdrive uses text-based pattern matching to detect uncacheable functions. References to function names like `NOW()` in SQL comments also cause the query to be marked as uncacheable.  
For more information, refer to [Query caching](https://edgetunnel-b2h.pages.dev/hyperdrive/concepts/query-caching/) and [Troubleshoot and debug](https://edgetunnel-b2h.pages.dev/hyperdrive/observability/troubleshooting/).

Feb 20, 2026
1. ### [@cloudflare/codemode v0.1.0: a new runtime agnostic modular architecture](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-20-codemode-sdk-rewrite/)  
[ Agents ](https://edgetunnel-b2h.pages.dev/agents/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
The [@cloudflare/codemode ↗](https://www.npmjs.com/package/@cloudflare/codemode) package has been rewritten into a modular, runtime-agnostic SDK.  
[Code Mode ↗](https://blog.cloudflare.com/code-mode/) enables LLMs to write and execute code that orchestrates your tools, instead of calling them one at a time. This can (and does) yield significant token savings, reduces context window pressure and improves overall model performance on a task.  
The new `Executor` interface is runtime agnostic and comes with a prebuilt `DynamicWorkerExecutor` to run generated code in a [Dynamic Worker Loader](https://edgetunnel-b2h.pages.dev/workers/runtime-apis/bindings/worker-loader/).  
#### Breaking changes

  * Removed `experimental_codemode()` and `CodeModeProxy` — the package no longer owns an LLM call or model choice
  * New import path: `createCodeTool()` is now exported from `@cloudflare/codemode/ai`  
#### New features

  * **`createCodeTool()`** — Returns a standard AI SDK `Tool` to use in your AI agents.
  * **`Executor` interface** — Minimal `execute(code, fns)` contract. Implement for any code sandboxing primitive or runtime.  
#### `DynamicWorkerExecutor`  
Runs code in a [Dynamic Worker](https://edgetunnel-b2h.pages.dev/workers/runtime-apis/bindings/worker-loader/). It comes with the following features:

  * **Network isolation** — `fetch()` and `connect()` blocked by default (`globalOutbound: null`) when using `DynamicWorkerExecutor`
  * **Console capture** — `console.log/warn/error` captured and returned in `ExecuteResult.logs`
  * **Execution timeout** — Configurable via `timeout` option (default 30s)  
#### Usage

  * [  JavaScript ](#tab-panel-3499)
  * [  TypeScript ](#tab-panel-3500)

**JavaScript**  
```js  
import { createCodeTool } from "@cloudflare/codemode/ai";  
import { DynamicWorkerExecutor } from "@cloudflare/codemode";  
import { streamText } from "ai";  
const executor = new DynamicWorkerExecutor({ loader: env.LOADER });  
const codemode = createCodeTool({ tools: myTools, executor });  
const result = streamText({  
  model,  
  tools: { codemode },  
  messages,  
});  
```

**TypeScript**  
```ts  
import { createCodeTool } from "@cloudflare/codemode/ai";  
import { DynamicWorkerExecutor } from "@cloudflare/codemode";  
import { streamText } from "ai";  
const executor = new DynamicWorkerExecutor({ loader: env.LOADER });  
const codemode = createCodeTool({ tools: myTools, executor });  
const result = streamText({  
  model,  
  tools: { codemode },  
  messages,  
});  
```  
#### Wrangler configuration

  * [  wrangler.jsonc ](#tab-panel-3475)
  * [  wrangler.toml ](#tab-panel-3476)

**JSONC**  
```jsonc  
{  
  "worker_loaders": [{ "binding": "LOADER" }],  
}  
```

**TOML**  
```toml  
[[worker_loaders]]  
binding = "LOADER"  
```  
See the [Code Mode documentation](https://edgetunnel-b2h.pages.dev/agents/tools/codemode/) for full API reference and examples.  
#### Upgrade  
```sh  
npm i @cloudflare/codemode@latest  
```

Feb 20, 2026
1. ### [Manage Cloudflare Tunnel directly from the main Cloudflare Dashboard](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-20-tunnel-core-dashboard/)  
[ Cloudflare Tunnel ](https://edgetunnel-b2h.pages.dev/tunnel/)[ Cloudflare Tunnel for SASE ](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/)  
[Cloudflare Tunnel](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/) is now available in the main Cloudflare Dashboard at [Networking > Tunnels ↗](https://dash.cloudflare.com/?to=/:account/tunnels), bringing first-class Tunnel management to developers using Tunnel for securing origin servers.  
![Manage Tunnels in the Core Dashboard](https://edgetunnel-b2h.pages.dev/_astro/tunnel-core-dashboard.BGPqaHfo_Pi6HO.webp)  
This new experience provides everything you need to manage Tunnels for [public applications](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/), including:

  * **Full Tunnel lifecycle management**: Create, configure, delete, and monitor all your Tunnels in one place.
  * **Native integrations**: View Tunnels by name when configuring [DNS records](https://edgetunnel-b2h.pages.dev/dns/manage-dns-records/how-to/create-dns-records/) and [Workers VPC](https://edgetunnel-b2h.pages.dev/workers-vpc/) — no more copy-pasting UUIDs.
  * **Real-time visibility**: Monitor [replicas](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) and Tunnel [health status](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/troubleshoot-tunnels/common-errors/#tunnel-status) directly in the dashboard.
  * **Routing map**: Manage all ingress routes for your Tunnel, including [public applications](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/), [private hostnames](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/), [private CIDRs](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-cidr/), and [Workers VPC services](https://edgetunnel-b2h.pages.dev/workers-vpc/), from a single interactive interface.  
#### Choose the right dashboard for your use case

**Core Dashboard**: Navigate to [Networking > Tunnels ↗](https://dash.cloudflare.com/?to=/:account/tunnels) to manage Tunnels for:

  * Securing origin servers and [public applications](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/routing-to-tunnel/) with CDN, WAF, Load Balancing, and DDoS protection
  * Connecting [Workers to private services](https://edgetunnel-b2h.pages.dev/workers-vpc/) via Workers VPC

**Cloudflare One Dashboard**: Navigate to [Zero Trust > Networks > Connectors ↗](https://one.dash.cloudflare.com/?to=/:account/networks/connectors) to manage Tunnels for:

  * Securing your public applications with [Zero Trust access policies](https://edgetunnel-b2h.pages.dev/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/)
  * Connecting users to [private applications](https://edgetunnel-b2h.pages.dev/cloudflare-one/access-controls/applications/non-http/self-hosted-private-app/)
  * Building a [private mesh network](https://edgetunnel-b2h.pages.dev/reference-architecture/architectures/sase/#connecting-networks)  
Both dashboards provide complete Tunnel management capabilities — choose based on your primary workflow.  
#### Get started  
New to Tunnel? Learn how to [get started with Cloudflare Tunnel](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/create-remote-tunnel/) or explore advanced use cases like [securing SSH servers](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/) or [running Tunnels in Kubernetes](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/kubernetes/).

Feb 19, 2026
1. ### [AI dashboard experience improvements](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-19-ai-dashboard-experience-improvements/)  
[ AI Gateway ](https://edgetunnel-b2h.pages.dev/ai-gateway/)[ Workers AI ](https://edgetunnel-b2h.pages.dev/workers-ai/)  
[Workers AI](https://edgetunnel-b2h.pages.dev/workers-ai/) and [AI Gateway](https://edgetunnel-b2h.pages.dev/ai-gateway/) have received a series of dashboard improvements to help you get started faster and manage your AI workloads more easily.

**Navigation and discoverability**  
AI now has its own top-level section in the Cloudflare dashboard sidebar, so you can find AI features without digging through menus.  
![AI sidebar navigation in the Cloudflare dashboard](https://edgetunnel-b2h.pages.dev/_astro/sidebar-navigation.BQNFBmAk_1GqV9H.webp)  

**Onboarding and getting started**  
[Getting started](https://edgetunnel-b2h.pages.dev/ai-gateway/get-started/) with AI Gateway is now simpler. When you create your first gateway, we now show your gateway's OpenAI-compatible endpoint and step-by-step guidance to help you configure it. The Playground also includes helpful prompts, and usage pages have clear next steps if you have not made any requests yet.  
![AI Gateway onboarding flow](https://edgetunnel-b2h.pages.dev/_astro/onboarding-flow.DZ7aMcHa_Z2hyg1I.webp)  
We've also combined the previously separate code example sections into one view with dropdown selectors for API type, provider, SDK, and authentication method so you can now customize the exact code snippet you need from one place.

**Dynamic Routing**

  * The [route builder](https://edgetunnel-b2h.pages.dev/ai-gateway/features/dynamic-routing/) is now more performant and responsive.
  * You can now copy route names to your clipboard with a single click.
  * Code examples use the [Universal Endpoint](https://edgetunnel-b2h.pages.dev/ai-gateway/usage/universal/) format, making it easier to integrate routes into your application.

**Observability and analytics**

  * Small monetary values now display correctly in [cost analytics](https://edgetunnel-b2h.pages.dev/ai-gateway/observability/costs/) charts, so you can accurately track spending at any scale.

**Accessibility**

  * Improvements to keyboard navigation within the AI Gateway, specifically when exploring usage by [provider](https://edgetunnel-b2h.pages.dev/ai-gateway/usage/providers/).
  * Improvements to sorting and filtering components on the [Workers AI](https://edgetunnel-b2h.pages.dev/workers-ai/models/) models page.  
For more information, refer to the [AI Gateway documentation](https://edgetunnel-b2h.pages.dev/ai-gateway/).

Feb 17, 2026
1. ### [Agents SDK v0.5.0: Protocol message control, retry utilities, data parts, and @cloudflare/ai-chat v0.1.0](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-17-agents-sdk-v050/)  
[ Agents ](https://edgetunnel-b2h.pages.dev/agents/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
The latest release of the [Agents SDK ↗](https://github.com/cloudflare/agents) adds built-in retry utilities, per-connection protocol message control, and a fully rewritten `@cloudflare/ai-chat` with data parts, tool approval persistence, and zero breaking changes.  
#### Retry utilities  
A new `this.retry()` method lets you retry any async operation with exponential backoff and jitter. You can pass an optional `shouldRetry` predicate to bail early on non-retryable errors.

  * [  JavaScript ](#tab-panel-3497)
  * [  TypeScript ](#tab-panel-3498)

**JavaScript**  
```js  
class MyAgent extends Agent {  
  async onRequest(request) {  
    const data = await this.retry(() => callUnreliableService(), {  
      maxAttempts: 4,  
      shouldRetry: (err) => !(err instanceof PermanentError),  
    });  
    return Response.json(data);  
  }  
}  
```

**TypeScript**  
```ts  
class MyAgent extends Agent {  
  async onRequest(request: Request) {  
    const data = await this.retry(() => callUnreliableService(), {  
      maxAttempts: 4,  
      shouldRetry: (err) => !(err instanceof PermanentError),  
    });  
    return Response.json(data);  
  }  
}  
```  
Retry options are also available per-task on `queue()`, `schedule()`, `scheduleEvery()`, and `addMcpServer()`:

  * [  JavaScript ](#tab-panel-3503)
  * [  TypeScript ](#tab-panel-3504)

**JavaScript**  
```js  
// Per-task retry configuration, persisted in SQLite alongside the task  
await this.schedule(  
  Date.now() + 60_000,  
  "sendReport",  
  { userId: "abc" },  
  {  
    retry: { maxAttempts: 5 },  
  },  
);  
// Class-level retry defaults  
class MyAgent extends Agent {  
  static options = {  
    retry: { maxAttempts: 3 },  
  };  
}  
```

**TypeScript**  
```ts  
// Per-task retry configuration, persisted in SQLite alongside the task  
await this.schedule(Date.now() + 60_000, "sendReport", { userId: "abc" }, {  
  retry: { maxAttempts: 5 },  
});  
// Class-level retry defaults  
class MyAgent extends Agent {  
  static options = {  
    retry: { maxAttempts: 3 },  
  };  
}  
```  
Retry options are validated eagerly at enqueue/schedule time, and invalid values throw immediately. Internal retries have also been added for workflow operations (`terminateWorkflow`, `pauseWorkflow`, and others) with Durable Object-aware error detection.  
#### Per-connection protocol message control  
Agents automatically send JSON text frames (identity, state, MCP server lists) to every WebSocket connection. You can now suppress these per-connection for clients that cannot handle them — binary-only devices, MQTT clients, or lightweight embedded systems.

  * [  JavaScript ](#tab-panel-3501)
  * [  TypeScript ](#tab-panel-3502)

**JavaScript**  
```js  
class MyAgent extends Agent {  
  shouldSendProtocolMessages(connection, ctx) {  
    // Suppress protocol messages for MQTT clients  
    const subprotocol = ctx.request.headers.get("Sec-WebSocket-Protocol");  
    return subprotocol !== "mqtt";  
  }  
}  
```

**TypeScript**  
```ts  
class MyAgent extends Agent {  
  shouldSendProtocolMessages(connection: Connection, ctx: ConnectionContext) {  
    // Suppress protocol messages for MQTT clients  
    const subprotocol = ctx.request.headers.get("Sec-WebSocket-Protocol");  
    return subprotocol !== "mqtt";  
  }  
}  
```  
Connections with protocol messages disabled still fully participate in RPC and regular messaging. Use `isConnectionProtocolEnabled(connection)` to check a connection's status at any time. The flag persists across Durable Object hibernation.  
See [Protocol messages](https://edgetunnel-b2h.pages.dev/agents/runtime/communication/protocol-messages/) for full documentation.  
#### `@cloudflare/ai-chat` v0.1.0  
The first stable release of `@cloudflare/ai-chat` ships alongside this release with a major refactor of `AIChatAgent` internals — new `ResumableStream` class, WebSocket `ChatTransport`, and simplified SSE parsing — with zero breaking changes. Existing code using `AIChatAgent` and `useAgentChat` works as-is.  
Key new features:

  * **Data parts** — Attach typed JSON blobs (`data-*`) to messages alongside text. Supports reconciliation (type+id updates in-place), append, and transient parts (ephemeral via `onData` callback). See [Data parts](https://edgetunnel-b2h.pages.dev/agents/communication-channels/chat/chat-agents/#data-parts).
  * **Tool approval persistence** — The `needsApproval` approval UI now survives page refresh and DO hibernation. The streaming message is persisted to SQLite when a tool enters `approval-requested` state.
  * **`maxPersistedMessages`** — Cap SQLite message storage with automatic oldest-message deletion.
  * **`body` option on `useAgentChat`** — Send custom data with every request (static or dynamic).
  * **Incremental persistence** — Hash-based cache to skip redundant SQL writes.
  * **Row size guard** — Automatic two-pass compaction when messages approach the SQLite 2 MB limit.
  * **`autoContinueAfterToolResult` defaults to `true`** — Client-side tool results and tool approvals now automatically trigger a server continuation, matching server-executed tool behavior. Set `autoContinueAfterToolResult: false` in `useAgentChat` to restore the previous behavior.  
Notable bug fixes:

  * Resolved stream resumption race conditions
  * Resolved an issue where `setMessages` functional updater sent empty arrays
  * Resolved an issue where client tool schemas were lost after DO hibernation
  * Resolved `InvalidPromptError` after tool approval (`approval.id` was dropped)
  * Resolved an issue where message metadata was not propagated on broadcast/resume paths
  * Resolved an issue where `clearAll()` did not clear in-memory chunk buffers
  * Resolved an issue where `reasoning-delta` silently dropped data when `reasoning-start` was missed during stream resumption  
#### Synchronous queue and schedule getters  
`getQueue()`, `getQueues()`, `getSchedule()`, `dequeue()`, `dequeueAll()`, and `dequeueAllByCallback()` were unnecessarily `async` despite only performing synchronous SQL operations. They now return values directly instead of wrapping them in Promises. This is backward compatible — existing code using `await` on these methods will continue to work.  
#### Other improvements

  * **Fix TypeScript "excessively deep" error** — A depth counter on `CanSerialize` and `IsSerializableParam` types bails out to `true` after 10 levels of recursion, preventing the "Type instantiation is excessively deep" error with deeply nested types like AI SDK `CoreMessage[]`.
  * **POST SSE keepalive** — The POST SSE handler now sends `event: ping` every 30 seconds to keep the connection alive, matching the existing GET SSE handler behavior. This prevents POST response streams from being silently dropped by proxies during long-running tool calls.
  * **Widened peer dependency ranges** — Peer dependency ranges across packages have been widened to prevent cascading major bumps during 0.x minor releases. `@cloudflare/ai-chat` and `@cloudflare/codemode` are now marked as optional peer dependencies.  
#### Upgrade  
To update to the latest version:  
```sh  
npm i agents@latest @cloudflare/ai-chat@latest  
```

Feb 17, 2026
1. ### [Docker-in-Docker support added to Containers and Sandboxes](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-17-docker-in-docker/)  
[ Containers ](https://edgetunnel-b2h.pages.dev/containers/)  
[Sandboxes](https://edgetunnel-b2h.pages.dev/sandbox/) and [Containers](https://edgetunnel-b2h.pages.dev/containers/) now support running Docker for "Docker-in-Docker" setups. This is particularly useful when your end users or [agents](https://edgetunnel-b2h.pages.dev/agents) want to run a full sandboxed development environment.  
This allows you to:

  * Develop containerized applications with your Sandbox
  * Run isolated test environments for images
  * Build container images as part of CI/CD workflows
  * Deploy arbitrary images supplied at runtime within a container  
For [Sandbox SDK](https://edgetunnel-b2h.pages.dev/sandbox/) users, see the [Docker-in-Docker guide](https://edgetunnel-b2h.pages.dev/sandbox/guides/docker-in-docker/) for instructions on combining Docker with the SandboxSDK. For general Containers usage, see the [Containers FAQ](https://edgetunnel-b2h.pages.dev/containers/faq/#can-i-run-docker-inside-a-container-docker-in-docker).

Feb 16, 2026
1. ### [Quick Editor devtools replaced with log viewer](https://edgetunnel-b2h.pages.dev/changelog/post/2026-02-12-quick-editor-dev-tools-deprecation/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
Cloudflare has deprecated the Workers Quick Editor dev tools inspector and replaced it with a lightweight log viewer.  
This aligns our logging with `wrangler tail` and gives us the opportunity to focus our efforts on bringing benefits from the work we have invested in observability, which would not be possible otherwise.  
We have made improvements to this logging viewer based on your feedback such that you can log object and array types, and easily clear the list of logs. This does not include class instances. Limitations are documented in the [Workers Playground docs](https://edgetunnel-b2h.pages.dev/workers/playground/).  
If you do need to develop your Worker with a remote inspector, you can still do this using Wrangler locally. Cloning a project from your quick editor to your computer for local development can be done with the `wrangler init --from-dash` command. For more information, refer to [Wrangler commands](https://edgetunnel-b2h.pages.dev/workers/wrangler/commands/general/#init).

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