--- title: Changelogs image: https://edgetunnel-b2h.pages.dev/cf-twitter-card.png --- > Documentation Index > Fetch the complete documentation index at: https://edgetunnel-b2h.pages.dev/changelog/llms.txt > Use this file to discover all available pages before exploring further. [Skip to content](#%5Ftop) # Changelog New updates and improvements at Cloudflare. [ Subscribe to RSS ](https://edgetunnel-b2h.pages.dev/changelog/rss/index.xml) [ View RSS feeds ](https://edgetunnel-b2h.pages.dev/fundamentals/new-features/available-rss-feeds/) All products ![hero image](https://edgetunnel-b2h.pages.dev/_astro/hero.CVYJHPAd_26AMqX.svg) Mar 26, 2026 1. ### [Easily connect Containers and Sandboxes to Workers](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-26-outbound-workers/) [ Containers ](https://edgetunnel-b2h.pages.dev/containers/) [Containers](https://edgetunnel-b2h.pages.dev/containers/) and [Sandboxes](https://edgetunnel-b2h.pages.dev/sandbox/) now support connecting directly to Workers over HTTP. This allows you to call Workers functions and [bindings](https://edgetunnel-b2h.pages.dev/workers/runtime-apis/bindings/), like [KV](https://edgetunnel-b2h.pages.dev/kv) or [R2](https://edgetunnel-b2h.pages.dev/r2/), from within the container at specific hostnames. #### Run Worker code Define an `outbound` handler to capture any HTTP request or use `outboundByHost` to capture requests to individual hostnames and IPs. **JavaScript** ```js export class MyApp extends Sandbox {} MyApp.outbound = async (request, env, ctx) => { // you can run arbitrary functions defined in your Worker on any HTTP request return await someWorkersFunction(request.body); }; MyApp.outboundByHost = { "my.worker": async (request, env, ctx) => { return await anotherFunction(request.body); }, }; ``` In this example, requests from the container to `http://my.worker` will run the function defined within `outboundByHost`, and any other HTTP requests will run the `outbound` handler. These handlers run entirely inside the Workers runtime, outside of the container sandbox. #### Access Workers bindings Each handler has access to `env`, so it can call any binding set in [Wrangler config](https://edgetunnel-b2h.pages.dev/workers/wrangler/configuration/#bindings). Code inside the container makes a standard HTTP request to that hostname and the outbound Worker translates it into a binding call. **JavaScript** ```js export class MyApp extends Sandbox {} MyApp.outboundByHost = { "my.kv": async (request, env, ctx) => { const key = new URL(request.url).pathname.slice(1); const value = await env.KV.get(key); return new Response(value ?? "", { status: value ? 200 : 404 }); }, "my.r2": async (request, env, ctx) => { const key = new URL(request.url).pathname.slice(1); const object = await env.BUCKET.get(key); return new Response(object?.body ?? "", { status: object ? 200 : 404 }); }, }; ``` Now, from inside the container sandbox, `curl http://my.kv/some-key` will access [Workers KV](https://edgetunnel-b2h.pages.dev/kv) and `curl http://my.r2/some-object` will access [R2](https://edgetunnel-b2h.pages.dev/r2/). #### Access Durable Object state Use `ctx.containerId` to reference the container's automatically provisioned [Durable Object](https://edgetunnel-b2h.pages.dev/durable-objects). **JavaScript** ```js export class MyContainer extends Container {} MyContainer.outboundByHost = { "get-state.do": async (request, env, ctx) => { const id = env.MY_CONTAINER.idFromString(ctx.containerId); const stub = env.MY_CONTAINER.get(id); return stub.getStateForKey(request.body); }, }; ``` This provides an easy way to associate state with any container instance, and includes a [built-in SQLite database](https://edgetunnel-b2h.pages.dev/durable-objects/get-started/#2-write-a-durable-object-class-using-sql-api). #### Get Started Today Upgrade to `@cloudflare/containers` version 0.2.0 or later, or `@cloudflare/sandbox` version 0.8.0 or later to use outbound Workers. Refer to [Containers outbound traffic](https://edgetunnel-b2h.pages.dev/containers/platform-details/outbound-traffic/) and [Sandboxes outbound traffic](https://edgetunnel-b2h.pages.dev/sandbox/guides/outbound-traffic/) for more details and examples. Mar 26, 2026 1. ### [Streaming ZIP file scanning removes per-file size limits](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-26-streaming-zip-handler/) [ Data Loss Prevention ](https://edgetunnel-b2h.pages.dev/cloudflare-one/data-loss-prevention/) DLP now processes ZIP files using a streaming handler that scans archive contents element-by-element as data arrives. This removes previous file size limitations and improves memory efficiency when scanning large archives. Microsoft Office documents (DOCX, XLSX, PPTX) also benefit from this improvement, as they use ZIP as a container format. This improvement is automatic — no configuration changes are required. Mar 26, 2026 1. ### [Access Durable Object jurisdiction via \`ctx.id.jurisdiction\`](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-26-durable-object-id-jurisdiction/) [ Durable Objects ](https://edgetunnel-b2h.pages.dev/durable-objects/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/) `ctx.id.jurisdiction` inside a Durable Object now reports the [jurisdiction](https://edgetunnel-b2h.pages.dev/durable-objects/reference/data-location/#restrict-durable-objects-to-a-jurisdiction) the object was created in — for example `"eu"` when accessed through `env.MY_DURABLE_OBJECT.jurisdiction("eu")` — so you can make region-aware decisions without passing the jurisdiction through method arguments or persisting it in storage. For the full list of ID-construction paths that preserve `jurisdiction`, refer to the [Durable Object ID documentation](https://edgetunnel-b2h.pages.dev/durable-objects/api/id/#jurisdiction). **JavaScript** ```js export class RegionalRoom extends DurableObject { async fetch(request) { // "eu" when accessed through env.MY_DURABLE_OBJECT.jurisdiction("eu") const region = this.ctx.id.jurisdiction; return new Response(`Hello from ${region ?? "the default region"}!`); } } // Worker export default { async fetch(request, env) { const stub = env.MY_DURABLE_OBJECT.jurisdiction("eu").getByName("general"); return stub.fetch(request); }, }; ``` `ctx.id.jurisdiction` is `undefined` for Durable Objects that were not created in a jurisdiction-restricted namespace. Alarms scheduled before 2026-03-15 also do not have `jurisdiction` stored; to backfill the value, reschedule the alarm from a `fetch()` or RPC handler. Mar 26, 2026 1. ### [URL Scanner improvements on Cloudflare Radar](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-26-url-scanner-improvements/) [ Radar ](https://edgetunnel-b2h.pages.dev/radar/) [**Radar**](https://edgetunnel-b2h.pages.dev/radar/) ships several improvements to the [URL Scanner ↗](https://radar.cloudflare.com/scan) that make scan reports more informative and easier to share: * **Live screenshots** — the summary card now includes an option to capture a live screenshot of the scanned URL on demand using the [Browser Rendering](https://edgetunnel-b2h.pages.dev/browser-run/) API. * **Save as PDF** — a new button generates a print-optimized document aggregating all tab contents (Summary, Security, Network, Behavior, and Indicators) into a single file. * **Download as JSON** — raw scan data is available as a JSON download for programmatic use. * **Redesigned summary layout** — page information and security details are now displayed side by side with the screenshot, with a layout that adapts to narrower viewports. * **File downloads** — downloads are separated into a dedicated card with expandable rows showing each file's source URL and SHA256 hash. * **Detailed IP address data** — the Network tab now includes additional detail per IP address observed during the scan. ![Screenshot of the redesigned URL Scanner summary on Radar](https://edgetunnel-b2h.pages.dev/_astro/url-scanner-summary-redesign.DO4wDjQ3_ZcLVPN.webp) Explore these improvements on the [Cloudflare Radar URL Scanner ↗](https://radar.cloudflare.com/scan). Mar 25, 2026 1. ### [Detect and sanitize HAR files](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-25-har-file-detection-and-sanitization/) [ Data Loss Prevention ](https://edgetunnel-b2h.pages.dev/cloudflare-one/data-loss-prevention/) HTTP Archive (HAR) files are used by engineering and support teams to capture and share web traffic logs for troubleshooting. However, these files routinely contain highly sensitive data — including session cookies, authorization headers, and other credentials — that can pose a significant risk if uploaded to third-party services without being reviewed or cleaned first. Gateway now includes a predefined DLP profile called **Unsanitized HAR** that detects HAR files in HTTP traffic. You can use this profile in a Gateway HTTP policy to either block HAR file uploads entirely or redirect users to a sanitization tool before allowing the upload to proceed. #### How to configure a HAR file policy In the [Cloudflare dashboard ↗](https://dash.cloudflare.com/), go to **Zero Trust** \> **Traffic policies** \> **Firewall Policies** \> **HTTP** and create a new HTTP policy using the **DLP Profile** selector: | Selector | Operator | Value | Action | | ----------- | -------- | ----------------- | ------ | | DLP Profile | in | _Unsanitized HAR_ | | Then choose one of the following actions: * **Block**: Prevents the upload of any HAR file that has not been sanitized by Cloudflare's sanitizer. Use this for strict environments where HAR file sharing must be disallowed entirely. * **Block** with **Gateway Redirect**: Intercepts the upload and redirects the user to `https://har-sanitizer.pages.dev/`, where they can sanitize the file. Once sanitized, the user can re-upload the clean file and proceed with their workflow. #### Sanitized HAR recognition HAR files processed by the Cloudflare HAR sanitizer receive a tamper-evident sanitized marker. DLP recognizes this marker and will not re-trigger the policy on a file that has already been sanitized and has not been modified since. If a previously sanitized file is edited, it will be treated as unsanitized and flagged again. #### Visibility in Gateway logs Gateway logs will reflect whether a detected HAR file was classified as **Unsanitized** or **Sanitized**, giving your security team full visibility into HAR file activity across your organization. For more information, refer to [predefined DLP profiles](https://edgetunnel-b2h.pages.dev/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles/). Mar 25, 2026 1. ### [Logpush — More granular timestamps](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-25-logpush-granular-timestamps/) [ Logpush ](https://edgetunnel-b2h.pages.dev/logs/logpush/)[ Logs ](https://edgetunnel-b2h.pages.dev/logs/) Logpush now supports higher-precision timestamp formats for log output. You can configure jobs to output timestamps at millisecond or nanosecond precision. This is available in both the Logpush UI in the Cloudflare dashboard and the [Logpush API](https://edgetunnel-b2h.pages.dev/api/resources/logpush/subresources/jobs/). To use the new formats, set `timestamp_format` in your Logpush job's `output_options`: * `rfc3339ms` — `2024-02-17T23:52:01.123Z` * `rfc3339ns` — `2024-02-17T23:52:01.123456789Z` Default timestamp formats apply unless explicitly set. The dashboard defaults to `rfc3339` and the API defaults to `unixnano`. For more information, refer to the [Log output options](https://edgetunnel-b2h.pages.dev/logs/logpush/logpush-job/log-output-options/) documentation. Mar 25, 2026 1. ### [New mTLS certificate fields for Transform Rules](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-25-rfc9440-mtls-fields/) [ Rules ](https://edgetunnel-b2h.pages.dev/rules/) Cloudflare now exposes four new fields in the Transform Rules phase that encode client certificate data in [RFC 9440 ↗](https://www.rfc-editor.org/rfc/rfc9440) format. Previously, forwarding client certificate information to your origin required custom parsing of PEM-encoded fields or non-standard HTTP header formats. These new fields produce output in the standardized `Client-Cert` and `Client-Cert-Chain` header format defined by RFC 9440, so your origin can consume them directly without any additional decoding logic. Each certificate is DER-encoded, Base64-encoded, and wrapped in colons. For example, `:MIIDsT...Vw==:`. A chain of intermediates is expressed as a comma-separated list of such values. #### New fields | Field | Type | Description | | ----------------------------------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | cf.tls\_client\_auth.cert\_rfc9440 | String | The client leaf certificate in RFC 9440 format. Empty if no client certificate was presented. | | cf.tls\_client\_auth.cert\_rfc9440\_too\_large | Boolean | true if the leaf certificate exceeded 10 KB and was omitted. In practice this will almost always be false. | | cf.tls\_client\_auth.cert\_chain\_rfc9440 | String | The intermediate certificate chain in RFC 9440 format as a comma-separated list. Empty if no intermediate certificates were sent or if the chain exceeded 16 KB. | | cf.tls\_client\_auth.cert\_chain\_rfc9440\_too\_large | Boolean | true if the intermediate chain exceeded 16 KB and was omitted. | The chain encoding follows the same ordering as the TLS handshake: the certificate closest to the leaf appears first, working up toward the trust anchor. The root certificate is not included. #### Example: Forwarding client certificate headers to your origin server Add a request header transform rule to set the `Client-Cert` and `Client-Cert-Chain` headers on requests forwarded to your origin server. For example, to forward headers for verified, non-revoked certificates: **Rule expression:** ```txt cf.tls_client_auth.cert_verified and not cf.tls_client_auth.cert_revoked ``` **Header modifications:** | Operation | Header name | Value | | --------- | ----------------- | ----------------------------------------- | | Set | Client-Cert | cf.tls\_client\_auth.cert\_rfc9440 | | Set | Client-Cert-Chain | cf.tls\_client\_auth.cert\_chain\_rfc9440 | To get the most out of these fields, upload your client CA certificate to Cloudflare so that Cloudflare validates the client certificate at the edge and populates `cf.tls_client_auth.cert_verified` and `cf.tls_client_auth.cert_revoked`. Prevent header injection You should ensure that `Client-Cert` and `Client-Cert-Chain` headers received by your origin server can only originate from this transform rule — any client could send these headers directly. * **If you use WAF custom rules to block requests with invalid mTLS connections:** The transform rule is sufficient. For all requests that reach your origin server, the rule will overwrite any existing `Client-Cert` and `Client-Cert-Chain` headers. * **If you do not enforce mTLS at the WAF:** Add another transform rule that removes any incoming `Client-Cert` and `Client-Cert-Chain` headers from all requests (use expression `true`), ordered before the rule above. This ensures your origin server cannot receive client-supplied values for these HTTP headers. For more information, refer to [Mutual TLS authentication](https://edgetunnel-b2h.pages.dev/cloudflare-one/access-controls/service-credentials/mutual-tls-authentication/), [Request Header Transform Rules](https://edgetunnel-b2h.pages.dev/rules/transform/request-header-modification/), and the [fields reference](https://edgetunnel-b2h.pages.dev/ruleset-engine/rules-language/fields/reference/). Mar 25, 2026 1. ### [Declare required secrets in your Wrangler configuration](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-24-secrets-config-property/) [ Workers ](https://edgetunnel-b2h.pages.dev/workers/) The new `secrets` configuration property lets you declare the secret names your Worker requires in your Wrangler configuration file. Required secrets are validated during local development and deploy, and used as the source of truth for type generation. * [ wrangler.jsonc ](#tab-panel-5031) * [ wrangler.toml ](#tab-panel-5032) **JSONC** ```jsonc { "secrets": { "required": ["API_KEY", "DB_PASSWORD"], }, } ``` **TOML** ```toml [secrets] required = [ "API_KEY", "DB_PASSWORD" ] ``` #### Local development When `secrets` is defined, `wrangler dev` and `vite dev` load only the keys listed in `secrets.required` from `.dev.vars` or `.env`/`process.env`. Additional keys in those files are excluded. If any required secrets are missing, a warning is logged listing the missing names. #### Type generation `wrangler types` generates typed bindings from `secrets.required` instead of inferring names from `.dev.vars` or `.env`. This lets you run type generation in CI or other environments where those files are not present. Per-environment secrets are supported — the aggregated `Env` type marks secrets that only appear in some environments as optional. #### Deploy `wrangler deploy` and `wrangler versions upload` validate that all secrets in `secrets.required` are configured on the Worker before the operation succeeds. If any required secrets are missing, the command fails with an error listing which secrets need to be set. For more information, refer to the [secrets configuration property](https://edgetunnel-b2h.pages.dev/workers/wrangler/configuration/#secrets-configuration-property) reference. Mar 24, 2026 1. ### [Advanced WAF customization for AI Crawl Control blocks](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-24-waf-rule-preservation/) [ AI Crawl Control ](https://edgetunnel-b2h.pages.dev/ai-crawl-control/) AI Crawl Control now supports extending the underlying WAF rule with custom modifications. Any changes you make directly in the WAF custom rules editor — such as adding path-based exceptions, extra user agents, or additional expression clauses — are preserved when you update crawler actions in AI Crawl Control. If the WAF rule expression has been modified in a way AI Crawl Control cannot parse, a warning banner appears on the **Crawlers** page with a link to view the rule directly in WAF. For more information, refer to [WAF rule management](https://edgetunnel-b2h.pages.dev/ai-crawl-control/features/manage-ai-crawlers/#waf-rule-management). Mar 24, 2026 1. ### [Cache Response Rules](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-24-cache-response-rules/) [ Cache / CDN ](https://edgetunnel-b2h.pages.dev/cache/) You can now control how Cloudflare handles origin responses without changing your origin. Cache Response Rules let you modify `Cache-Control` directives, manage cache tags, and strip headers like `Set-Cookie` from origin responses _before_ they reach Cloudflare's cache. Whether traffic is cached or passed through dynamically, these rules give you control over origin response behavior that was previously out of reach. #### What changed Cache Rules previously only operated on request attributes. Cache Response Rules introduce a new response phase that evaluates origin responses and lets you act on them before caching. You can now: * **Modify `Cache-Control` directives**: Set or remove individual directives like `no-store`, `no-cache`, `max-age`, `s-maxage`, `stale-while-revalidate`, `immutable`, and more. For example, remove a `no-cache` directive your origin sends so Cloudflare can cache the asset, or set an `s-maxage` to control how long Cloudflare stores it. * **Set a different browser `Cache-Control`**: Send a different `Cache-Control` header downstream to browsers and other clients than what Cloudflare uses internally, giving you independent control over edge and browser caching strategies. * **Manage cache tags**: Add, set, or remove cache tags on responses, including converting tags from another CDN's header format into Cloudflare's `Cache-Tag` header. This is especially useful if you are migrating from a CDN that uses a different tag header or delimiter. * **Strip headers that block caching**: Remove `Set-Cookie`, `ETag`, or `Last-Modified` headers from origin responses before caching, so responses that would otherwise be treated as uncacheable can be stored and served from cache. #### Benefits * **No origin changes required**: Fix caching behavior entirely from Cloudflare, even when your origin configuration is locked down or managed by a different team. * **Simpler CDN migration**: Match caching behavior from other CDN providers without rewriting your origin. Translate cache tag formats and override directives that do not align with Cloudflare's defaults. * **Native support, fewer workarounds**: Functionality that previously required workarounds is now built into Cache Rules with full Tiered Cache compatibility. * **Fine-grained control**: Use expressions to match on request and response attributes, then apply precise cache settings per rule. Rules are stackable and composable with existing Cache Rules. #### Get started Configure Cache Response Rules in the [Cloudflare dashboard ↗](https://dash.cloudflare.com/?to=/:account/:zone/caching/cache-rules) under **Caching** \> **Cache Rules**, or via the [Rulesets API ↗](https://edgetunnel-b2h.pages.dev/ruleset-engine/rulesets-api/). For more details, refer to the [Cache Rules documentation ↗](https://edgetunnel-b2h.pages.dev/cache/how-to/cache-response-rules/). Mar 24, 2026 1. ### [Use Docker Hub images with Containers](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-24-docker-hub-images/) [ Containers ](https://edgetunnel-b2h.pages.dev/containers/) Containers now support [Docker Hub ↗](https://hub.docker.com/) images. You can use a fully qualified Docker Hub image reference in your [Wrangler configuration ↗](https://edgetunnel-b2h.pages.dev/workers/wrangler/configuration/#containers) instead of first pushing the image to Cloudflare Registry. * [ wrangler.jsonc ](#tab-panel-5033) * [ wrangler.toml ](#tab-panel-5034) **JSONC** ```jsonc { "containers": [ { // Example: docker.io/cloudflare/sandbox:0.7.18 "image": "docker.io//:", }, ], } ``` **TOML** ```toml [[containers]] image = "docker.io//:" ``` Containers also support private Docker Hub images. To configure credentials, refer to [Use private Docker Hub images](https://edgetunnel-b2h.pages.dev/containers/platform-details/image-management/#use-private-docker-hub-images). For more information, refer to [Image management](https://edgetunnel-b2h.pages.dev/containers/platform-details/image-management/). Mar 24, 2026 1. ### [OIDC Claims filtering now available in Gateway Firewall, Resolver, and Egress policies](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-24-oidc-claims-filtering-gateway-policies/) [ Gateway ](https://edgetunnel-b2h.pages.dev/cloudflare-one/traffic-policies/) Cloudflare Gateway now supports [OIDC Claims](https://edgetunnel-b2h.pages.dev/cloudflare-one/traffic-policies/identity-selectors/#oidc-claims) as a selector in Firewall, Resolver, and Egress policies. Administrators can use custom OIDC claims from their identity provider to build fine-grained, identity-based traffic policies across all Gateway policy types. With this update, you can: * Filter traffic in [DNS](https://edgetunnel-b2h.pages.dev/cloudflare-one/traffic-policies/dns-policies/), [HTTP](https://edgetunnel-b2h.pages.dev/cloudflare-one/traffic-policies/http-policies/), and [Network](https://edgetunnel-b2h.pages.dev/cloudflare-one/traffic-policies/network-policies/) firewall policies based on OIDC claim values. * Apply custom [resolver policies](https://edgetunnel-b2h.pages.dev/cloudflare-one/traffic-policies/resolver-policies/) to route DNS queries to specific resolvers depending on a user's OIDC claims. * Control [egress policies](https://edgetunnel-b2h.pages.dev/cloudflare-one/traffic-policies/egress-policies/) to assign dedicated egress IPs based on OIDC claim attributes. For example, you can create a policy that routes traffic differently for users with `department=engineering` in their OIDC claims, or restrict access to certain destinations based on a user's role claim. To get started, configure [custom OIDC claims](https://edgetunnel-b2h.pages.dev/cloudflare-one/integrations/identity-providers/generic-oidc/#custom-oidc-claims) on your identity provider and use the **OIDC Claims** selector in the Gateway policy builder. For more information, refer to [Identity-based policies](https://edgetunnel-b2h.pages.dev/cloudflare-one/traffic-policies/identity-selectors/). Mar 24, 2026 1. ### [Interconnects moved to Connectors](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-24-interconnects-navigation-update/) [ Network Interconnect ](https://edgetunnel-b2h.pages.dev/network-interconnect/) The top-level **Interconnects** page in the Cloudflare dashboard has been removed. Interconnects are now located under **Connectors** \> **Interconnects**. Your existing configurations and functionality remain the same. Mar 24, 2026 1. ### [Dynamic Workers, now in open beta](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-24-dynamic-workers-open-beta/) [ Workers ](https://edgetunnel-b2h.pages.dev/workers/) [Dynamic Workers](https://edgetunnel-b2h.pages.dev/dynamic-workers/) are now in [open beta ↗](https://blog.cloudflare.com/dynamic-workers/) for all paid Workers users. You can now have a Worker spin up other Workers, called Dynamic Workers, at runtime to execute code on-demand in a secure, sandboxed environment. Dynamic Workers start in milliseconds, making them well suited for fast, secure code execution at scale. #### Use Dynamic Workers for * **[Code Mode](https://edgetunnel-b2h.pages.dev/agents/tools/codemode/)**: LLMs are trained to write code. Run tool-calling logic written in code instead of stepping through many tool calls, which can save up to 80% in inference tokens and cost. * **AI agents executing code**: Run code for tasks like data analysis, file transformation, API calls, and chained actions. * **Running AI-generated code**: Run generated code for prototypes, projects, and automations in a secure, isolated sandboxed environment. * **Fast development and previews**: Load prototypes, previews, and playgrounds in milliseconds. * **Custom automations**: Create custom tools on the fly that execute a task, call an integration, or automate a workflow. #### Executing Dynamic Workers Dynamic Workers support two loading modes: * `load(code)` — for one-time code execution (equivalent to calling `get()` with a null ID). * `get(id, callback)` — caches a Dynamic Worker by ID so it can stay warm across requests. Use this when the same code will receive subsequent requests. * [ JavaScript ](#tab-panel-5045) * [ TypeScript ](#tab-panel-5046) **JavaScript** ```js export default { async fetch(request, env) { const worker = env.LOADER.load({ compatibilityDate: "2026-01-01", mainModule: "src/index.js", modules: { "src/index.js": ` export default { fetch() { return new Response("Hello from a dynamic Worker"); }, }; `, }, // Block all outbound network access from the Dynamic Worker. globalOutbound: null, }); return worker.getEntrypoint().fetch(request); }, }; ``` **TypeScript** ```ts export default { async fetch(request: Request, env: Env): Promise { const worker = env.LOADER.load({ compatibilityDate: "2026-01-01", mainModule: "src/index.js", modules: { "src/index.js": ` export default { fetch() { return new Response("Hello from a dynamic Worker"); }, }; `, }, // Block all outbound network access from the Dynamic Worker. globalOutbound: null, }); return worker.getEntrypoint().fetch(request); }, }; ``` #### Helper libraries for Dynamic Workers Here are 3 new libraries to help you build with Dynamic Workers: * **[@cloudflare/codemode ↗](https://www.npmjs.com/package/@cloudflare/codemode)**: Replace individual tool calls with a single `code()` tool, so LLMs write and execute TypeScript that orchestrates multiple API calls in one pass. * **[@cloudflare/worker-bundler ↗](https://www.npmjs.com/package/@cloudflare/worker-bundler)**: Resolve npm dependencies and bundle source files into ready-to-load modules for Dynamic Workers, all at runtime. * **[@cloudflare/shell ↗](https://www.npmjs.com/package/@cloudflare/shell)**: Give your agent a virtual filesystem inside a Dynamic Worker with persistent storage backed by SQLite and R2. #### Try it out **Dynamic Workers Starter** [![Deploy to Workers](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/agents/tree/main/examples/dynamic-workers) Use this [starter ↗](https://github.com/cloudflare/agents/tree/main/examples/dynamic-workers) to deploy a Worker that can load and execute Dynamic Workers. **Dynamic Workers Playground** [![Deploy to Workers](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/agents/tree/main/examples/dynamic-workers-playground) Deploy the [Dynamic Workers Playground ↗](https://github.com/cloudflare/agents/tree/main/examples/dynamic-workers-playground) to write or import code, bundle it at runtime with `@cloudflare/worker-bundler`, execute it through a Dynamic Worker, and see real-time responses and execution logs. For the full API reference and configuration options, refer to the [Dynamic Workers documentation](https://edgetunnel-b2h.pages.dev/dynamic-workers/). #### Pricing Dynamic Workers [pricing](https://edgetunnel-b2h.pages.dev/dynamic-workers/pricing/) is based on three dimensions: Dynamic Workers created daily, requests, and CPU time. | | Included | Additional usage | | --------------------------------- | -------------------------------------- | ----------------------------------- | | **Dynamic Workers created daily** | 1,000 unique Dynamic Workers per month | +$0.002 per Dynamic Worker per day | | **Requests** ¹ | 10 million per month | +$0.30 per million requests | | **CPU time** ¹ | 30 million CPU milliseconds per month | +$0.02 per million CPU milliseconds | ¹ Uses [Workers Standard rates](https://edgetunnel-b2h.pages.dev/workers/platform/pricing/#workers) and will appear as part of your existing Workers bill, not as separate Dynamic Workers charges. Note: Dynamic Workers requests and CPU time are already billed as part of your Workers plan and will count toward your Workers requests and CPU usage. The Dynamic Workers created daily charge is not yet active — you will not be billed for the number of Dynamic Workers created at this time. Pricing information is shared in advance so you can estimate future costs. Mar 23, 2026 1. ### [Workflow instances now support pause(), resume(), restart(), and terminate() methods in local development](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-23-local-dev-instance-methods/) [ Workflows ](https://edgetunnel-b2h.pages.dev/workflows/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/) Workflow instance methods `pause()`, `resume()`, `restart()`, and `terminate()` are now available in local development when using `wrangler dev`. You can now test the full Workflow instance lifecycle locally: **TypeScript** ```ts const instance = await env.MY_WORKFLOW.create({ id: "my-instance-id", }); await instance.pause(); // pauses a running workflow instance await instance.resume(); // resumes a paused instance await instance.restart(); // restarts the instance from the beginning await instance.terminate(); // terminates the instance immediately ``` Mar 23, 2026 1. ### [Agents SDK v0.8.0: readable state, idempotent schedules, typed AgentClient, and Zod 4](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-23-agents-sdk-v080/) [ 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) exposes agent state as a readable property, prevents duplicate schedule rows across Durable Object restarts, brings full TypeScript inference to `AgentClient`, and migrates to Zod 4. #### Readable `state` on `useAgent` and `AgentClient` Both `useAgent` (React) and `AgentClient` (vanilla JS) now expose a `state` property that reflects the current agent state. Previously, reading state required manually tracking it through the `onStateUpdate` callback. **React (`useAgent`)** * [ JavaScript ](#tab-panel-5035) * [ TypeScript ](#tab-panel-5036) **JavaScript** ```js const agent = useAgent({ agent: "game-agent", name: "room-123", }); // Read state directly — no separate useState + onStateUpdate needed return
Score: {agent.state?.score}
; // Spread for partial updates agent.setState({ ...agent.state, score: (agent.state?.score ?? 0) + 10 }); ``` **TypeScript** ```ts const agent = useAgent({ agent: "game-agent", name: "room-123", }); // Read state directly — no separate useState + onStateUpdate needed return
Score: {agent.state?.score}
; // Spread for partial updates agent.setState({ ...agent.state, score: (agent.state?.score ?? 0) + 10 }); ``` `agent.state` is reactive — the component re-renders when state changes from either the server or a client-side `setState()` call. **Vanilla JS (`AgentClient`)** * [ JavaScript ](#tab-panel-5037) * [ TypeScript ](#tab-panel-5038) **JavaScript** ```js const client = new AgentClient({ agent: "game-agent", name: "room-123", host: "your-worker.workers.dev", }); client.setState({ score: 100 }); console.log(client.state); // { score: 100 } ``` **TypeScript** ```ts const client = new AgentClient({ agent: "game-agent", name: "room-123", host: "your-worker.workers.dev", }); client.setState({ score: 100 }); console.log(client.state); // { score: 100 } ``` State starts as `undefined` and is populated when the server sends the initial state on connect (from `initialState`) or when `setState()` is called. Use optional chaining (`agent.state?.field`) for safe access. The `onStateUpdate` callback continues to work as before — the new `state` property is additive. #### Idempotent `schedule()` `schedule()` now supports an `idempotent` option that deduplicates by `(type, callback, payload)`, preventing duplicate rows from accumulating when called in places that run on every Durable Object restart such as `onStart()`. **Cron schedules are idempotent by default.** Calling `schedule("0 * * * *", "tick")` multiple times with the same callback, expression, and payload returns the existing schedule row instead of creating a new one. Pass `{ idempotent: false }` to override. Delayed and date-scheduled types support opt-in idempotency: * [ JavaScript ](#tab-panel-5039) * [ TypeScript ](#tab-panel-5040) **JavaScript** ```js import { Agent } from "agents"; class MyAgent extends Agent { async onStart() { // Safe across restarts — only one row is created await this.schedule(60, "maintenance", undefined, { idempotent: true }); } } ``` **TypeScript** ```ts import { Agent } from "agents"; class MyAgent extends Agent { async onStart() { // Safe across restarts — only one row is created await this.schedule(60, "maintenance", undefined, { idempotent: true }); } } ``` Two new warnings help catch common foot-guns: * Calling `schedule()` inside `onStart()` without `{ idempotent: true }` emits a `console.warn` with actionable guidance (once per callback; skipped for cron and when `idempotent` is set explicitly). * If an alarm cycle processes 10 or more stale one-shot rows for the same callback, the SDK emits a `console.warn` and a `schedule:duplicate_warning` diagnostics channel event. #### Typed `AgentClient` with `call` inference and `stub` proxy `AgentClient` now accepts an optional agent type parameter for full type inference on RPC calls, matching the typed experience already available with `useAgent`. * [ JavaScript ](#tab-panel-5043) * [ TypeScript ](#tab-panel-5044) **JavaScript** ```js const client = new AgentClient({ agent: "my-agent", host: window.location.host, }); // Typed call — method name autocompletes, args and return type inferred const value = await client.call("getValue"); // Typed stub — direct RPC-style proxy await client.stub.getValue(); await client.stub.add(1, 2); ``` **TypeScript** ```ts const client = new AgentClient({ agent: "my-agent", host: window.location.host, }); // Typed call — method name autocompletes, args and return type inferred const value = await client.call("getValue"); // Typed stub — direct RPC-style proxy await client.stub.getValue(); await client.stub.add(1, 2); ``` State is automatically inferred from the agent type, so `onStateUpdate` is also typed: * [ JavaScript ](#tab-panel-5041) * [ TypeScript ](#tab-panel-5042) **JavaScript** ```js const client = new AgentClient({ agent: "my-agent", host: window.location.host, onStateUpdate: (state) => { // state is typed as MyAgent's state type }, }); ``` **TypeScript** ```ts const client = new AgentClient({ agent: "my-agent", host: window.location.host, onStateUpdate: (state) => { // state is typed as MyAgent's state type }, }); ``` Existing untyped usage continues to work without changes. The RPC type utilities (`AgentMethods`, `AgentStub`, `RPCMethods`) are now exported from `agents/client` for advanced typing scenarios. `agents`, `@cloudflare/ai-chat`, and `@cloudflare/codemode` now require `zod ^4.0.0`. Zod v3 is no longer supported. #### `@cloudflare/ai-chat` fixes * **Turn serialization** — `onChatMessage()` and `_reply()` work is now queued so user requests, tool continuations, and `saveMessages()` never stream concurrently. * **Duplicate messages on stop** — Clicking stop during an active stream no longer splits the assistant message into two entries. * **Duplicate messages after tool calls** — Orphaned client IDs no longer leak into persistent storage. #### `keepAlive()` and `keepAliveWhile()` are no longer experimental `keepAlive()` now uses a lightweight in-memory ref count instead of schedule rows. Multiple concurrent callers share a single alarm cycle. The `@experimental` tag has been removed from both `keepAlive()` and `keepAliveWhile()`. #### `@cloudflare/codemode`: TanStack AI integration A new entry point `@cloudflare/codemode/tanstack-ai` adds support for [TanStack AI's ↗](https://tanstack.com/ai) `chat()` as an alternative to the Vercel AI SDK's `streamText()`: * [ JavaScript ](#tab-panel-5047) * [ TypeScript ](#tab-panel-5048) **JavaScript** ```js import { createCodeTool, tanstackTools, } from "@cloudflare/codemode/tanstack-ai"; import { chat } from "@tanstack/ai"; const codeTool = createCodeTool({ tools: [tanstackTools(myServerTools)], executor, }); const stream = chat({ adapter, tools: [codeTool], messages }); ``` **TypeScript** ```ts import { createCodeTool, tanstackTools } from "@cloudflare/codemode/tanstack-ai"; import { chat } from "@tanstack/ai"; const codeTool = createCodeTool({ tools: [tanstackTools(myServerTools)], executor, }); const stream = chat({ adapter, tools: [codeTool], messages }); ``` #### Upgrade To update to the latest version: ```sh npm i agents@latest @cloudflare/ai-chat@latest ``` Mar 23, 2026 1. ### [New AI Search REST API endpoints for /search and /chat/completions](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-23-ai-search-new-rest-api/) [ AI Search ](https://edgetunnel-b2h.pages.dev/ai-search/) [AI Search](https://edgetunnel-b2h.pages.dev/ai-search/) now offers new [REST API](https://edgetunnel-b2h.pages.dev/ai-search/api/search/rest-api/) endpoints for search and chat that use an OpenAI compatible format. This means you can use the familiar `messages` array structure that works with existing OpenAI SDKs and tools. The messages array also lets you pass previous messages within a session, so the model can maintain context across multiple turns. | Endpoint | Path | | ---------------- | ------------------------------------------------------------------------ | | Chat Completions | POST /accounts/{account\_id}/ai-search/instances/{name}/chat/completions | | Search | POST /accounts/{account\_id}/ai-search/instances/{name}/search | Here is an example request to the Chat Completions endpoint using the new `messages` array format: ```bash curl https://api.cloudflare.com/client/v4/accounts/{ACCOUNT_ID}/ai-search/instances/{NAME}/chat/completions \ -H "Content-Type: application/json" \ -H "Authorization: Bearer {API_TOKEN}" \ -d '{ "messages": [ { "role": "system", "content": "You are a helpful documentation assistant." }, { "role": "user", "content": "How do I get started?" } ] }' ``` For more details, refer to the [AI Search REST API guide](https://edgetunnel-b2h.pages.dev/ai-search/api/search/rest-api/). #### Migration from existing AutoRAG API (recommended) If you are using the previous AutoRAG API endpoints (`/autorag/rags/`), we recommend migrating to the new endpoints. The previous AutoRAG API endpoints will continue to be fully supported. Refer to the [migration guide](https://edgetunnel-b2h.pages.dev/ai-search/api/migration/rest-api/) for step-by-step instructions. Mar 23, 2026 1. ### [AI Search UI snippets and MCP support](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-23-ai-search-public-endpoint-and-snippets/) [ AI Search ](https://edgetunnel-b2h.pages.dev/ai-search/) [AI Search](https://edgetunnel-b2h.pages.dev/ai-search/) now supports public endpoints, UI snippets, and MCP, making it easy to add search to your website or connect AI agents. Public endpoints allow you to expose AI Search capabilities without requiring API authentication. To enable public endpoints: 1. Go to **AI Search** in the Cloudflare dashboard. [ Go to **AI Search** ](https://dash.cloudflare.com/?to=/:account/ai/ai-search) 2. Select your instance, and turn on **Public Endpoint** in **Settings**. For more details, refer to [Public endpoint configuration](https://edgetunnel-b2h.pages.dev/ai-search/configuration/retrieval/public-endpoint/). #### UI snippets UI snippets are pre-built search and chat components you can embed in your website. Visit [search.ai.cloudflare.com ↗](https://search.ai.cloudflare.com/) to configure and preview components for your AI Search instance. ![Example of the search-modal-snippet component](https://edgetunnel-b2h.pages.dev/_astro/ui-snippet-search-modal.nSXbvcsi_1H402.webp) To add a search modal to your page: ```html ``` For more details, refer to the [UI snippets documentation](https://edgetunnel-b2h.pages.dev/ai-search/configuration/retrieval/embed-search-snippets/). #### MCP The MCP endpoint allows AI agents to search your content via the Model Context Protocol. Connect your MCP client to: ```txt https://.search.ai.cloudflare.com/mcp ``` For more details, refer to the [MCP documentation](https://edgetunnel-b2h.pages.dev/ai-search/api/search/mcp/). Mar 23, 2026 1. ### [Custom metadata filtering for AI Search](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-23-custom-metadata-filtering/) [ AI Search ](https://edgetunnel-b2h.pages.dev/ai-search/) [AI Search](https://edgetunnel-b2h.pages.dev/ai-search/) now supports custom metadata filtering, allowing you to define your own metadata fields and filter search results based on attributes like category, version, or any custom field you define. #### Define a custom metadata schema You can define up to 5 custom metadata fields per AI Search instance. Each field has a name and data type (`text`, `number`, or `boolean`): ```bash curl -X POST https://api.cloudflare.com/client/v4/accounts/{ACCOUNT_ID}/ai-search/instances \ -H "Content-Type: application/json" \ -H "Authorization: Bearer {API_TOKEN}" \ -d '{ "id": "my-instance", "type": "r2", "source": "my-bucket", "custom_metadata": [ { "field_name": "category", "data_type": "text" }, { "field_name": "version", "data_type": "number" }, { "field_name": "is_public", "data_type": "boolean" } ] }' ``` #### Add metadata to your documents How you attach metadata depends on your data source: * **R2 bucket**: Set metadata using S3-compatible custom headers (`x-amz-meta-*`) when uploading objects. Refer to [R2 custom metadata](https://edgetunnel-b2h.pages.dev/ai-search/configuration/data-source/r2/#custom-metadata) for examples. * **Website**: Add `` tags to your HTML pages. Refer to [Website custom metadata](https://edgetunnel-b2h.pages.dev/ai-search/configuration/data-source/website/#custom-metadata) for details. #### Filter search results Use custom metadata fields in your search queries alongside built-in attributes like `folder` and `timestamp`: ```bash curl https://api.cloudflare.com/client/v4/accounts/{ACCOUNT_ID}/ai-search/instances/{NAME}/search \ -H "Content-Type: application/json" \ -H "Authorization: Bearer {API_TOKEN}" \ -d '{ "messages": [ { "content": "How do I configure authentication?", "role": "user" } ], "ai_search_options": { "retrieval": { "filters": { "category": "documentation", "version": { "$gte": 2.0 } } } } }' ``` Learn more in the [metadata filtering documentation](https://edgetunnel-b2h.pages.dev/ai-search/configuration/indexing/metadata/). Mar 23, 2026 1. ### [Web Assets fields now available in GraphQL Analytics API](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-23-web-assets-graphql-fields/) [ API Shield ](https://edgetunnel-b2h.pages.dev/api-shield/) Two new fields are now available in the `httpRequestsAdaptive` and `httpRequestsAdaptiveGroups` [GraphQL Analytics API](https://edgetunnel-b2h.pages.dev/analytics/graphql-api/) datasets: * `webAssetsOperationId` — the ID of the [saved endpoint](https://edgetunnel-b2h.pages.dev/api-shield/management-and-monitoring/) that matched the incoming request. * `webAssetsLabelsManaged` — the [managed labels](https://edgetunnel-b2h.pages.dev/api-shield/management-and-monitoring/endpoint-labels/#managed-labels) mapped to the matched operation at the time of the request (for example, `cf-llm`, `cf-log-in`). At most 10 labels are returned per request. Both fields are empty when no operation matched. `webAssetsLabelsManaged` is also empty when no managed labels are assigned to the matched operation. These fields allow you to determine, per request, which Web Assets operation was matched and which managed labels were active. This is useful for troubleshooting downstream security detection verdicts — for example, understanding why [AI Security for Apps](https://edgetunnel-b2h.pages.dev/waf/detections/ai-security-for-apps/) did or did not flag a request. Refer to [Endpoint labeling service](https://edgetunnel-b2h.pages.dev/api-shield/management-and-monitoring/endpoint-labels/#analytics) for GraphQL query examples. Mar 23, 2026 1. ### [R2 SQL now supports over 190 new functions, expressions, and complex types](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-23-expanded-sql-functions-expressions-complex-types/) [ R2 SQL ](https://edgetunnel-b2h.pages.dev/r2-sql/) [R2 SQL](https://edgetunnel-b2h.pages.dev/r2-sql/) now supports an expanded SQL grammar so you can write richer analytical queries without exporting data. This release adds CASE expressions, column aliases, arithmetic in clauses, 163 scalar functions, 33 aggregate functions, EXPLAIN, Common Table Expressions (CTEs),and full struct/array/map access. R2 SQL is Cloudflare's serverless, distributed, analytics query engine for querying [Apache Iceberg ↗](https://iceberg.apache.org/) tables stored in [R2 Data Catalog](https://edgetunnel-b2h.pages.dev/r2/data-catalog/). This page documents the supported SQL syntax. #### Highlights * **Column aliases** — `SELECT col AS alias` now works in all clauses * **CASE expressions** — conditional logic directly in SQL (searched and simple forms) * **Scalar functions** — 163 new functions across math, string, datetime, regex, crypto, encoding, and type inspection categories * **Aggregate functions** — statistical (variance, stddev, correlation, regression), bitwise, boolean, and positional aggregates join the existing basic and approximate functions * **Complex types** — query struct fields with bracket notation, use 46 array functions, and extract map keys/values * **Common table expressions (CTEs)** — use `WITH ... AS` to define named temporary result sets. Chained CTEs are supported. All CTEs must reference the same single table. * **Full expression support** — arithmetic, type casting (`CAST`, `TRY_CAST`, `::` shorthand), and `EXTRACT` in SELECT, WHERE, GROUP BY, HAVING, and ORDER BY #### Examples #### CASE expressions with statistical aggregates ```sql SELECT source, CASE WHEN AVG(price) > 30 THEN 'premium' WHEN AVG(price) > 10 THEN 'mid-tier' ELSE 'budget' END AS tier, round(stddev(price), 2) AS price_volatility, approx_percentile_cont(price, 0.95) AS p95_price FROM my_namespace.sales_data GROUP BY source ``` #### Struct and array access ```sql SELECT product_name, pricing['price'] AS price, array_to_string(tags, ', ') AS tag_list FROM my_namespace.products WHERE array_has(tags, 'Action') ORDER BY pricing['price'] DESC LIMIT 10 ``` #### Chained CTEs with time-series analysis ```sql WITH monthly AS ( SELECT date_trunc('month', sale_timestamp) AS month, department, COUNT(*) AS transactions, round(AVG(total_amount), 2) AS avg_amount FROM my_namespace.sales_data WHERE sale_timestamp BETWEEN '2025-01-01T00:00:00Z' AND '2025-12-31T23:59:59Z' GROUP BY date_trunc('month', sale_timestamp), department ), ranked AS ( SELECT month, department, transactions, avg_amount, CASE WHEN avg_amount > 1000 THEN 'high-value' WHEN avg_amount > 500 THEN 'mid-value' ELSE 'standard' END AS tier FROM monthly WHERE transactions > 100 ) SELECT * FROM ranked ORDER BY month, avg_amount DESC ``` For the full function reference and syntax details, refer to the [SQL reference](https://edgetunnel-b2h.pages.dev/r2-sql/sql-reference/). For limitations and best practices, refer to [Limitations and best practices](https://edgetunnel-b2h.pages.dev/r2-sql/reference/limitations-best-practices/). Mar 23, 2026 1. ### [WAF Release - 2026-03-23](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-23-waf-release/) [ WAF ](https://edgetunnel-b2h.pages.dev/waf/) This week's release focuses on new improvements 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 | ...97321c6c | N/A | Command Injection - Generic 9 - URI Vector | Log | Disabled | This is a new detection. | | Cloudflare Managed Ruleset | ...1eb7a999 | N/A | Command Injection - Generic 9 - Header Vector | Log | Disabled | This is a new detection. | | Cloudflare Managed Ruleset | ...0677175f | N/A | Command Injection - Generic 9 - Body Vector | Log | Disabled | This is a new detection. | | Cloudflare Managed Ruleset | ...479da68f | N/A | PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132 (beta) | Log | Block | This rule has been merged into the original rule "PHP, vBulletin, jQuery File Upload - Code Injection, Dangerous File Upload - CVE:CVE-2018-9206, CVE:CVE-2019-17132" (ID: ...824b817c ) | Mar 20, 2026 1. ### [Managed OAuth for Cloudflare Access](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-20-managed-oauth/) [ Access ](https://edgetunnel-b2h.pages.dev/cloudflare-one/access-controls/policies/) Cloudflare Access supports managed OAuth, which allows non-browser clients — such as CLIs, AI agents, SDKs, and scripts — to authenticate with Access-protected applications using a standard OAuth 2.0 authorization code flow. Previously, non-browser clients that attempted to access a protected application received a `302` redirect to a login page they could not complete. The established workaround was `cloudflared access curl`, which required installing additional tooling. With managed OAuth, clients instead receive a `401` response with a `WWW-Authenticate` header that points to Access's OAuth discovery endpoints ([RFC 8414 ↗](https://datatracker.ietf.org/doc/html/rfc8414) and [RFC 9728 ↗](https://datatracker.ietf.org/doc/html/rfc9728)). The client opens the end user's browser to the Access login page. The end user authenticates with their identity provider, and the client receives an OAuth access token for subsequent requests. Access enforces the same policies as a browser login; the OAuth layer is a new transport mechanism, not a separate authentication path. Managed OAuth can be enabled on any self-hosted Access application or [MCP server portal](https://edgetunnel-b2h.pages.dev/cloudflare-one/access-controls/ai-controls/mcp-portals/). It is opt-in for existing applications to avoid interfering with those that run their own OAuth servers and rely on their own `WWW-Authenticate` headers. Note For MCP server portals, managed OAuth is enabled by default on new portals. It remains opt-in for self-hosted applications. To enable managed OAuth, go to **Zero Trust** \> **Access controls** \> **Applications**, edit the application, and turn on **Managed OAuth** under **Advanced settings**. You can also enable it via the API by setting `oauth_configuration.enabled` to `true` on the [Access applications endpoint](https://edgetunnel-b2h.pages.dev/api/resources/zero%5Ftrust/subresources/access/subresources/applications/methods/update/). ![Managed OAuth settings in the Cloudflare dashboard](https://edgetunnel-b2h.pages.dev/_astro/managed-oauth.BirLnBpy_Zjg97R.webp) For setup instructions, refer to [Enable managed OAuth](https://edgetunnel-b2h.pages.dev/cloudflare-one/access-controls/applications/http-apps/managed-oauth/). Mar 20, 2026 1. ### [Route MCP server portal traffic through Cloudflare Gateway](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-20-mcp-portal-gateway-routing/) [ Access ](https://edgetunnel-b2h.pages.dev/cloudflare-one/access-controls/policies/) [MCP server portals](https://edgetunnel-b2h.pages.dev/cloudflare-one/access-controls/ai-controls/mcp-portals/) can now route traffic through [Cloudflare Gateway](https://edgetunnel-b2h.pages.dev/cloudflare-one/traffic-policies/) for richer HTTP request logging and data loss prevention (DLP) scanning. When Gateway routing is turned on, portal traffic appears in your [Gateway HTTP logs](https://edgetunnel-b2h.pages.dev/cloudflare-one/insights/logs/dashboard-logs/gateway-logs/). You can create [Gateway HTTP policies](https://edgetunnel-b2h.pages.dev/cloudflare-one/traffic-policies/) with [DLP profiles](https://edgetunnel-b2h.pages.dev/cloudflare-one/data-loss-prevention/dlp-profiles/) to detect and block sensitive data sent to upstream MCP servers. Note DLP [AI prompt profiles](https://edgetunnel-b2h.pages.dev/cloudflare-one/data-loss-prevention/dlp-profiles/predefined-profiles/#ai-prompt) do not apply to MCP server portal traffic. To enable Gateway routing, go to **Access controls** \> **AI controls**, edit the portal, and turn on **Route traffic through Cloudflare Gateway** under **Basic information**. ![Route MCP server portal traffic through Cloudflare Gateway](https://edgetunnel-b2h.pages.dev/_astro/portal-route-through-gateway.0KMUAXBm_Z1B5rry.webp) For more details, refer to [Route traffic through Gateway](https://edgetunnel-b2h.pages.dev/cloudflare-one/access-controls/ai-controls/mcp-portals/#route-portal-traffic-through-gateway). Mar 20, 2026 1. ### [DNS Analytics for Customer Metadata Boundary set to EU region](https://edgetunnel-b2h.pages.dev/changelog/post/2026-03-20-dns-analytics-cmb-eu/) [ DNS ](https://edgetunnel-b2h.pages.dev/dns/) DNS Analytics is now available for customers with [Customer Metadata Boundary](https://edgetunnel-b2h.pages.dev/data-localization/metadata-boundary/) (CMB) set to EU. Query your DNS analytics data while keeping metadata stored in the EU region. This update includes: * **DNS Analytics** — Access the same DNS analytics experience for zones in CMB=EU accounts. * **EU data residency** — Analytics data is stored and queried from the EU region, meeting data localization requirements. * **DNS Firewall Analytics** — DNS Firewall analytics is now supported for CMB=EU customers. #### Availability Available to customers with the [Data Localization Suite](https://edgetunnel-b2h.pages.dev/data-localization/) who have Customer Metadata Boundary configured for the EU region. #### Where to find it * **Authoritative DNS:** In the Cloudflare dashboard, select your zone and go to the **Analytics** page. [ Go to **Analytics** ](https://dash.cloudflare.com/?to=/:account/:zone/dns/analytics) * **DNS Firewall:** In the Cloudflare dashboard, go to the **DNS Firewall Analytics** page. [ Go to **Analytics** ](https://dash.cloudflare.com/?to=/:account/dns-firewall/analytics) For more information, refer to [DNS Analytics](https://edgetunnel-b2h.pages.dev/dns/additional-options/analytics/) and [DNS Firewall Analytics](https://edgetunnel-b2h.pages.dev/dns/dns-firewall/analytics/). ```json {"@context":"https://schema.org","@type":"BlogPosting","@id":"https://edgetunnel-b2h.pages.dev/changelog/14/#page","headline":"Changelogs | Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/changelog/14/","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/"}} ```