Cloudflare Changelog

Workflows now supports saga-style rollbacks, allowing you to add compensating logic to each step.do() in case of downstream failures. If the instance fails, the rollback handlers will execute in reverse step-start order.

This is useful for multi-step operations that touch external systems, such as inventory reservations, payment authorization, ticket creation, or infrastructure provisioning. Instead of writing all cleanup logic in a top-level catch, you can keep each compensating action next to the step it undoes.

Rollback handlers support their own retry and timeout configuration, and Workflows now exposes rollback outcomes in instance status responses. Workflows analytics also emits rollback lifecycle events, making it easier to distinguish a forward execution failure from a rollback failure when debugging production workflows.

• JavaScript

  <div><div><span>await</span><span> </span><span>step</span><span>.</span><span>do</span><span>(</span></div></div><div><div><span>  </span><span>"provision resource"</span><span>,</span></div></div><div><div><span>  </span><span>async</span><span> </span><span>()</span><span> </span><span>=></span><span> </span><span>{</span></div></div><div><div><span>    </span><span>const</span><span> </span><span>resource</span><span> </span><span>=</span><span> </span><span>await</span><span> </span><span>provisionResource</span><span>()</span><span>;</span></div></div><div><div><span>    </span><span>return</span><span> </span><span>{</span><span> resourceId</span><span>:</span><span> </span><span>resource</span><span>.</span><span>id</span><span> </span><span>};</span></div></div><div><div><span>  </span><span>},</span></div></div><div><div><span>  </span><span>{</span></div></div><div><div><span>    </span><span>rollback</span><span>:</span><span> </span><span>async</span><span> </span><span>({</span><span> </span><span>output</span><span> </span><span>})</span><span> </span><span>=></span><span> </span><span>{</span></div></div><div><div><span>      </span><span>const</span><span> </span><span>{</span><span> </span><span>resourceId</span><span> </span><span>}</span><span> </span><span>=</span><span> </span><span>output</span><span>;</span></div></div><div><div><span>      </span><span>await</span><span> </span><span>deleteResource</span><span>(</span><span>resourceId</span><span>)</span><span>;</span></div></div><div><div><span>    </span><span>},</span></div></div><div><div><span><span>    </span></span><span>rollbackConfig</span><span>:</span><span> </span><span>{</span></div></div><div><div><span><span>      </span></span><span>retries</span><span>:</span><span> </span><span>{</span><span> limit</span><span>:</span><span> </span><span>3</span><span>,</span><span> delay</span><span>:</span><span> </span><span>"15 seconds"</span><span>,</span><span> backoff</span><span>:</span><span> </span><span>"linear"</span><span> </span><span>},</span></div></div><div><div><span><span>      </span></span><span>timeout</span><span>:</span><span> </span><span>"2 minutes"</span><span>,</span></div></div><div><div><span>    </span><span>},</span></div></div><div><div><span>  </span><span>},</span></div></div><div><div><span>)</span><span>;</span></div></div>

• TypeScript

  <div><div><span>await</span><span> </span><span>step</span><span>.</span><span>do</span><span>(</span></div></div><div><div><span>  </span><span>"provision resource"</span><span>,</span></div></div><div><div><span>  </span><span>async</span><span> </span><span>()</span><span> </span><span>=></span><span> </span><span>{</span></div></div><div><div><span>    </span><span>const</span><span> </span><span>resource</span><span> </span><span>=</span><span> </span><span>await</span><span> </span><span>provisionResource</span><span>()</span><span>;</span></div></div><div><div><span>    </span><span>return</span><span> </span><span>{</span><span> resourceId</span><span>:</span><span> </span><span>resource</span><span>.</span><span>id</span><span> </span><span>};</span></div></div><div><div><span>  </span><span>},</span></div></div><div><div><span>  </span><span>{</span></div></div><div><div><span>    </span><span>rollback</span><span>:</span><span> </span><span>async</span><span> </span><span>({</span><span> </span><span>output</span><span> </span><span>})</span><span> </span><span>=></span><span> </span><span>{</span></div></div><div><div><span>      </span><span>const</span><span> </span><span>{</span><span> </span><span>resourceId</span><span> </span><span>}</span><span> </span><span>=</span><span> </span><span>output</span><span> </span><span>as</span><span> </span><span>{</span><span> </span><span>resourceId</span><span>:</span><span> </span><span>string</span><span><span> </span><span>};</span></span></div></div><div><div><span>      </span><span>await</span><span> </span><span>deleteResource</span><span>(</span><span>resourceId</span><span>)</span><span>;</span></div></div><div><div><span>    </span><span>},</span></div></div><div><div><span><span>    </span></span><span>rollbackConfig</span><span>:</span><span> </span><span>{</span></div></div><div><div><span><span>      </span></span><span>retries</span><span>:</span><span> </span><span>{</span><span> limit</span><span>:</span><span> </span><span>3</span><span>,</span><span> delay</span><span>:</span><span> </span><span>"15 seconds"</span><span>,</span><span> backoff</span><span>:</span><span> </span><span>"linear"</span><span> </span><span>},</span></div></div><div><div><span><span>      </span></span><span>timeout</span><span>:</span><span> </span><span>"2 minutes"</span><span>,</span></div></div><div><div><span>    </span><span>},</span></div></div><div><div><span>  </span><span>},</span></div></div><div><div><span>)</span><span>;</span></div></div>

Refer to rollback options to learn more.

Workers using a VPC Network binding with network_id: "cf1:network" now egress to public Internet destinations through Cloudflare Gateway. This means your existing Zero Trust traffic policies — DNS, HTTP, Network, and egress — extend to traffic that originates from your Workers, the same way they do for WARP users today.

1. Worker

   Calls env.EGRESS.fetch()

2. VPC binding ↓

3. Cloudflare Mesh

   Bind via cf1:network

4. ↓

5. Cloudflare Gateway

   Policies applied:

   DNS HTTP Network

6. ↓

7. ↗ Public Internet

   Any public hostname or IP

Gateway logs DNS HTTP Network

What you get by default:

• Visibility. Worker egress shows up in Gateway DNS, HTTP, and Network logs alongside your other traffic, so you can audit what your Workers are calling and when.

• Enforcement. Any existing Gateway policy whose selectors match a Worker request will apply — including allow / block lists, DNS category filtering, and HTTP destination rules. If you have already blocked a category for your workforce, your Workers inherit that block.

• wrangler.jsonc

  <div><div><span>{</span></div></div><div><div><span>  </span><span>"</span><span>vpc_networks</span><span>"</span><span>:</span><span> </span><span>[</span></div></div><div><div><span>    </span><span>{</span></div></div><div><div><span>      </span><span>"</span><span>binding</span><span>"</span><span>:</span><span> </span><span>"EGRESS"</span><span>,</span></div></div><div><div><span>      </span><span>"</span><span>network_id</span><span>"</span><span>:</span><span> </span><span>"cf1:network"</span><span>,</span></div></div><div><div><span>      </span><span>"</span><span>remote</span><span>"</span><span>:</span><span> </span><span>true</span><span>,</span></div></div><div><div><span>    </span><span>},</span></div></div><div><div><span>  </span><span>],</span></div></div><div><div><span>}</span></div></div>

• wrangler.toml

  <div><div><span>[[</span><span>vpc_networks</span><span>]]</span></div></div><div><div><span>binding</span><span> </span><span>=</span><span> </span><span>"EGRESS"</span></div></div><div><div><span>network_id</span><span> </span><span>=</span><span> </span><span>"cf1:network"</span></div></div><div><div><span>remote</span><span> </span><span>=</span><span> </span><span>true</span></div></div>

• JavaScript

  <div><div><span>// Egress to a public destination — subject to your Gateway policies and logged</span></div></div><div><div><span>const</span><span> </span><span>response</span><span> </span><span>=</span><span> </span><span>await</span><span> </span><span>env</span><span>.</span><span>EGRESS</span><span>.</span><span>fetch</span><span>(</span><span>"https://api.example.com/data"</span><span>)</span><span>;</span></div></div>

• TypeScript

  <div><div><span>// Egress to a public destination — subject to your Gateway policies and logged</span></div></div><div><div><span>const</span><span> </span><span>response</span><span> </span><span>=</span><span> </span><span>await</span><span> </span><span>env</span><span>.</span><span>EGRESS</span><span>.</span><span>fetch</span><span>(</span><span>"https://api.example.com/data"</span><span>)</span><span>;</span></div></div>

For configuration options, refer to VPC Networks. For policy authoring, refer to Cloudflare Gateway traffic policies.

Radar now provides finer-grained traffic charts for longer time ranges. Previously, selecting a 1-3 month view on HTTP and NetFlows charts defaulted to weekly aggregation, which was too coarse to surface meaningful trends. Views longer than 3 months defaulted to monthly aggregation, returning as few as 7 data points for a 6-month range.

The new defaults are:

• 1-3 months: daily granularity (7x more data points)
• Longer than 3 months (HTTP and NetFlows): weekly granularity (4x more data points)

For example, a 12-week traffic view previously showed weekly data:

The same view now shows daily data:

Similarly, a 1-year HTTP traffic view that previously showed just 12 monthly data points now provides 52 weekly data points.

Visit Cloudflare Radar to explore the new granular views.

AI Gateway now supports spend limits — cost-based budgets that track cumulative dollar spend and block requests when the budget is exceeded. Unlike rate limiting, which caps the number of requests, spend limits track actual cost based on token usage and model pricing.

You can scope limits by model, provider, or custom metadata dimensions. For example, give each user a $200/day budget, cap total gateway spend at $10,000/day, or limit a specific model to $50/day per user. Each rule uses a configurable time window with fixed or sliding enforcement.

Spend limits work with both Unified Billing and BYOK requests for models with known pricing.

For more details, refer to the Spend limits documentation.

Cloudflare Access now supports IdP federation, which allows organizations to share a single identity provider across multiple Cloudflare accounts.

Instead of configuring the same IdP (for example, Okta or Entra ID) separately in every account, you configure it once in a source account and share it with the other accounts in your organization. Each recipient account gets a read-only IdP connection that routes authentication back to the source account through a bridge — a hidden application in the source account that brokers the cross-account login. End users sign in with their existing IdP credentials, and each account's Access policies evaluate the resulting identity just like any other IdP login.

Key capabilities:

• One IdP, many accounts — Configure your IdP once and share it with all accounts in your organization.
• Lifecycle management — As accounts join or leave your Cloudflare organization, their IdP connections are provisioned and removed automatically — no manual cleanup required.
• Immutable recipient connections — IdP connections in recipient accounts cannot be accidentally modified or deleted.

To get started, refer to IdP federation.

Pay-as-you-go customers can now view billable usage and create budget alerts directly from the product overview pages for Workers & Pages, D1, R2, Workers KV, Queues, Vectorize, Durable Objects, and Containers. A new sidebar widget shows current-period spend and the billing cycle date range, alongside a button to create a budget alert.

The widget pulls from the same data as the Billable Usage dashboard and aligns to your billing cycle (or the current day on Free plans), so the numbers match your invoice. Enterprise contract accounts are not yet supported.

Selecting Create budget alert opens the budget alert flow inline so you can set a dollar threshold in the same place you are reviewing usage. Budget alerts apply to your total account-level spend across all products, not just the product page you create them from.

For more information, refer to the Usage-based billing documentation.

The pipeline field inside the pipelines binding configuration in your Wrangler configuration file has been renamed to stream. The old field is deprecated but still accepted.

Update your configuration to use stream to avoid the deprecation warning.

Before (deprecated):

• wrangler.jsonc

  <div><div><span>{</span></div></div><div><div><span>  </span><span>"</span><span>$schema</span><span>"</span><span>:</span><span> </span><span>"./node_modules/wrangler/config-schema.json"</span><span>,</span></div></div><div><div><span>  </span><span>"</span><span>pipelines</span><span>"</span><span>:</span><span> </span><span>[</span></div></div><div><div><span>    </span><span>{</span></div></div><div><div><span>      </span><span>"</span><span>binding</span><span>"</span><span>:</span><span> </span><span>"MY_PIPELINE"</span><span>,</span></div></div><div><div><span>      </span><span>"</span><span>pipeline</span><span>"</span><span>:</span><span> </span><span>"<STREAM_ID>"</span></div></div><div><div><span>    </span><span>}</span></div></div><div><div><span>  </span><span>]</span></div></div><div><div><span>}</span></div></div>

• wrangler.toml

  <div><div><span>[[</span><span>pipelines</span><span>]]</span></div></div><div><div><span>binding</span><span> </span><span>=</span><span> </span><span>"MY_PIPELINE"</span></div></div><div><div><span>pipeline</span><span> </span><span>=</span><span> </span><span>"<STREAM_ID>"</span></div></div>

After:

• wrangler.jsonc

  <div><div><span>{</span></div></div><div><div><span>  </span><span>"</span><span>$schema</span><span>"</span><span>:</span><span> </span><span>"./node_modules/wrangler/config-schema.json"</span><span>,</span></div></div><div><div><span>  </span><span>"</span><span>pipelines</span><span>"</span><span>:</span><span> </span><span>[</span></div></div><div><div><span>    </span><span>{</span></div></div><div><div><span>      </span><span>"</span><span>binding</span><span>"</span><span>:</span><span> </span><span>"MY_PIPELINE"</span><span>,</span></div></div><div><div><span>      </span><span>"</span><span>stream</span><span>"</span><span>:</span><span> </span><span>"<STREAM_ID>"</span></div></div><div><div><span>    </span><span>}</span></div></div><div><div><span>  </span><span>]</span></div></div><div><div><span>}</span></div></div>

• wrangler.toml

  <div><div><span>[[</span><span>pipelines</span><span>]]</span></div></div><div><div><span>binding</span><span> </span><span>=</span><span> </span><span>"MY_PIPELINE"</span></div></div><div><div><span>stream</span><span> </span><span>=</span><span> </span><span>"<STREAM_ID>"</span></div></div>

No other changes are required. The binding name, TypeScript types, and runtime API (env.MY_PIPELINE.send(...)) remain the same.

For more information on configuring pipeline bindings, refer to Writing to streams.

Cloudflare Access now supports SAML assertion encryption for identity provider integrations. When turned on, your identity provider encrypts SAML assertions using a Cloudflare-managed certificate before sending them through the user's browser. Only Access can decrypt these assertions, protecting sensitive identity data even after TLS termination.

Without encryption, SAML assertions are transmitted in plaintext and could be visible to browser extensions or client-side malware.

SAML encryption includes built-in certificate lifecycle management:

• Automatic certificate generation: Access generates an encryption certificate when you turn on SAML encryption for an identity provider.
• Certificate rotation: Rotate certificates without downtime. The previous certificate remains valid until expiration, giving you time to update your IdP.
• PEM export: Copy the certificate in PEM format for manual upload to your IdP, or point your IdP to the SAML metadata endpoint for automatic retrieval.

To get started, refer to Encrypt SAML assertions.

Today we are launching self-managed OAuth, enabling developers to build third-party applications that integrate with Cloudflare via OAuth. This provides a more secure, user-friendly, and manageable alternative to API tokens.

OAuth lets third-party applications act on behalf of a user to access their Cloudflare account. For example, after a user grants consent, Wrangler can deploy Workers into that account.

What is new

Cloudflare Developers can now create and manage their own OAuth applications to integrate with Cloudflare.

Create an application

To create an application, go to Manage account > OAuth clients in your account on the Cloudflare dashboard.

Go to OAuth clients

Select limited scopes

If you have used an API token to call Cloudflare APIs, OAuth client scopes will look familiar. Select only the scopes your application needs during application creation, and include that scope list when sending users to Cloudflare for consent.

Users can review the requested scopes before they consent.

Apps for both private and public use

Applications start with private visibility. Private applications can only be used by members of the account where the application was created.

To make an application available to any Cloudflare user, complete the prerequisites for public visibility.

For more information, refer to client visibility.

Client domain verification

Before an application can be made public, you must verify the client domain. Domain verification helps users confirm that the application owner controls the domain shown on the consent page.

After verification, users see a verified badge on the consent page.

For more information, refer to domain verification.

Learn more

For more information, refer to OAuth clients.

You can now create, update, or delete multiple secrets for your Worker in a single request using the bulk secrets endpoint.

• Include a secret with a value to create or update.
• Set a secret to null to delete.
• Secrets not included in the request are left unchanged.

The following example creates API_KEY, updates the already existing DB_PASSWORD, and deletes OLD_SECRET:

<div><div><span>{</span></div></div><div><div><span>  </span><span>"</span><span>secrets</span><span>"</span><span>:</span><span> </span><span>{</span></div></div><div><div><span>    </span><span>"</span><span>API_KEY</span><span>"</span><span>:</span><span> </span><span>{</span><span> </span><span>"</span><span>type</span><span>"</span><span>:</span><span> </span><span>"secret_text"</span><span>,</span><span> </span><span>"</span><span>name</span><span>"</span><span>:</span><span> </span><span>"API_KEY"</span><span>,</span><span> </span><span>"</span><span>text</span><span>"</span><span>:</span><span> </span><span>"my-api-key"</span><span> </span><span>},</span></div></div><div><div><span>    </span><span>"</span><span>DB_PASSWORD</span><span>"</span><span>:</span><span> </span><span>{</span><span> </span><span>"</span><span>type</span><span>"</span><span>:</span><span> </span><span>"secret_text"</span><span>,</span><span> </span><span>"</span><span>name</span><span>"</span><span>:</span><span> </span><span>"DB_PASSWORD"</span><span>,</span><span> </span><span>"</span><span>text</span><span>"</span><span>:</span><span> </span><span>"my-db-password"</span><span> </span><span>},</span></div></div><div><div><span>    </span><span>"</span><span>OLD_SECRET</span><span>"</span><span>:</span><span> </span><span>null</span></div></div><div><div><span>  </span><span>}</span></div></div><div><div><span>}</span></div></div>

You can do the same from the command line using wrangler secret bulk:

<div><div><span>npx</span><span> </span><span>wrangler</span><span> </span><span>secret</span><span> </span><span>bulk</span><span> </span><span><</span><span> </span><span>secrets.json</span></div></div>

To delete a key, set its value to null in the JSON file. Deletion is not supported with .env files.

Each request supports up to 100 total operations (creates, updates, and deletes combined).

You can now attach cron schedules directly to a Workflow binding in wrangler.jsonc. Each scheduled run creates a new Workflow instance automatically, so you do not need to define a separate Worker with a scheduled handler just to trigger your Workflow on an interval.

For example, you can configure hourly, every-15-minute, or weekday schedules on the same Workflow:

<div><div><span>{</span></div></div><div><div><span>  </span><span>"</span><span>workflows</span><span>"</span><span>:</span><span> </span><span>[</span></div></div><div><div><span>    </span><span>{</span></div></div><div><div><span>      </span><span>"</span><span>name</span><span>"</span><span>:</span><span> </span><span>"my-scheduled-workflow"</span><span>,</span></div></div><div><div><span>      </span><span>"</span><span>binding</span><span>"</span><span>:</span><span> </span><span>"MY_WORKFLOW"</span><span>,</span></div></div><div><div><span>      </span><span>"</span><span>class_name</span><span>"</span><span>:</span><span> </span><span>"MyScheduledWorkflow"</span><span>,</span></div></div><div><div><span>      </span><span>"</span><span>schedules</span><span>"</span><span>:</span><span> </span><span>[</span><span>"0 * * * *"</span><span>,</span><span> </span><span>"*/15 * * * *"</span><span>,</span><span> </span><span>"0 9 * * MON-FRI"</span><span>]</span></div></div><div><div><span>    </span><span>}</span></div></div><div><div><span>  </span><span>]</span></div></div><div><div><span>}</span></div></div>

This makes it easier to build recurring jobs such as database backups, invoice generation, report aggregation, and cleanup tasks without wiring up a separate Cron Trigger entrypoint.

For more information, refer to Trigger Workflows.

The Cisco IOS XE third-party integration guide for Cloudflare WAN has been updated to include:

• Post Quantum Cryptography (PQC)
• Policy-Based Routing (PBR)
• IP Service Level Agreement (IP SLA)

This link will take you directly to the updated Cisco IOS XE guide.

The latest release of the Agents SDK adds four new ways to build with @cloudflare/think: on-demand Agent Skills, chat messengers (starting with Telegram), declarative scheduled tasks, and durable reasoning steps inside Workflows. This release also significantly hardens durable chat recovery, so turns reliably ride through deploys, evictions, and stalled model streams in production.

Agent Skills (experimental)

Give an agent a catalog of on-demand instructions, resources, and scripts. A skill source adds a catalog to the system prompt, and the model activates a skill only when a task matches — so a large library of capabilities does not bloat every prompt.

• JavaScript

  <div><div><span>import </span><span>{</span><span><span> </span><span>Think</span></span><span>,</span><span><span> </span><span>skills</span><span> </span></span><span>}</span><span> from </span><span>"@cloudflare/think"</span><span>;</span></div></div><div><div><span><span>import </span><span>bundledSkills</span><span> from </span></span><span>"agents:skills"</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>export</span><span> </span><span>class</span><span> </span><span>SkillsAgent</span><span> </span><span>extends</span><span> </span><span>Think</span><span> </span><span>{</span></div></div><div><div><span>  </span><span>getSkills</span><span>()</span><span> </span><span>{</span></div></div><div><div><span>    </span><span>return</span><span> [</span></div></div><div><div><span>      </span><span>bundledSkills</span><span>,</span></div></div><div><div><span><span>      </span></span><span>skills</span><span>.</span><span>r2</span><span>(</span><span>this</span><span>.</span><span>env</span><span>.</span><span>SKILLS_BUCKET</span><span>,</span><span> </span><span>{</span><span> prefix</span><span>:</span><span> </span><span>"skills/"</span><span> </span><span>}</span><span>)</span><span>,</span></div></div><div><div><span><span>    </span></span><span>]</span><span>;</span></div></div><div><div><span>  </span><span>}</span></div></div><div><div><span>}</span></div></div>

• TypeScript

  <div><div><span>import </span><span>{</span><span><span> </span><span>Think</span></span><span>,</span><span><span> </span><span>skills</span><span> </span></span><span>}</span><span> from </span><span>"@cloudflare/think"</span><span>;</span></div></div><div><div><span><span>import </span><span>bundledSkills</span><span> from </span></span><span>"agents:skills"</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>export</span><span> </span><span>class</span><span> </span><span>SkillsAgent</span><span> </span><span>extends</span><span> </span><span>Think</span><span><</span><span>Env</span><span>></span><span> </span><span>{</span></div></div><div><div><span>  </span><span>getSkills</span><span>()</span><span> </span><span>{</span></div></div><div><div><span>    </span><span>return</span><span> [</span></div></div><div><div><span>      </span><span>bundledSkills</span><span>,</span></div></div><div><div><span><span>      </span></span><span>skills</span><span>.</span><span>r2</span><span>(</span><span>this</span><span>.</span><span>env</span><span>.</span><span>SKILLS_BUCKET</span><span>,</span><span> </span><span>{</span><span> prefix</span><span>:</span><span> </span><span>"skills/"</span><span> </span><span>}</span><span>)</span><span>,</span></div></div><div><div><span><span>    </span></span><span>]</span><span>;</span></div></div><div><div><span>  </span><span>}</span></div></div><div><div><span>}</span></div></div>

The agents:skills import bundles a local ./skills directory through the Agents Vite plugin (one directory per skill, each with a SKILL.md). Skills can also load from R2 or a manifest. When skills are available, Think exposes activate_skill, read_skill_resource, and an optional run_skill_script tool. Skill loading is resilient: a duplicate or failing source is skipped with a warning instead of breaking the agent.

Agent Skills are experimental, and script execution in particular is early. The API may change in a future release. We would love your feedback — tell us what you are building and what is missing in the Agents repository.

Messengers

Connect a Think agent directly to a chat platform. Think owns the webhook route, conversation routing, durable reply fiber, and streamed delivery back to the provider. Telegram ships as the first provider.

• JavaScript

  <div><div><span>import </span><span>{</span><span><span> </span><span>Think</span><span> </span></span><span>}</span><span> from </span><span>"@cloudflare/think"</span><span>;</span></div></div><div><div><span>import </span><span>{</span></div></div><div><div><span><span>  </span></span><span>defineMessengers</span><span>,</span></div></div><div><div><span><span>  </span></span><span>ThinkMessengerStateAgent</span><span>,</span></div></div><div><div><span>}</span><span> from </span><span>"@cloudflare/think/messengers"</span><span>;</span></div></div><div><div><span><span>import </span><span>telegramMessenger</span><span> from </span></span><span>"@cloudflare/think/messengers/telegram"</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>export</span><span> </span><span>{</span><span> </span><span>ThinkMessengerStateAgent</span><span> </span><span>};</span></div></div><div><div>
  </div></div><div><div><span>export</span><span> </span><span>class</span><span> </span><span>SupportAgent</span><span> </span><span>extends</span><span> </span><span>Think</span><span> </span><span>{</span></div></div><div><div><span>  </span><span>getMessengers</span><span>()</span><span> </span><span>{</span></div></div><div><div><span>    </span><span>return</span><span> </span><span>defineMessengers</span><span>(</span><span>{</span></div></div><div><div><span><span>      </span></span><span>telegram</span><span>:</span><span> </span><span>telegramMessenger</span><span>(</span><span>{</span></div></div><div><div><span><span>        </span></span><span>token</span><span>:</span><span> </span><span>this</span><span>.</span><span>env</span><span>.</span><span>TELEGRAM_BOT_TOKEN</span><span>,</span></div></div><div><div><span><span>        </span></span><span>userName</span><span>:</span><span> </span><span>"support_bot"</span><span>,</span></div></div><div><div><span><span>        </span></span><span>secretToken</span><span>:</span><span> </span><span>this</span><span>.</span><span>env</span><span>.</span><span>TELEGRAM_WEBHOOK_SECRET_TOKEN</span><span>,</span></div></div><div><div><span>      </span><span>}</span><span>)</span><span>,</span></div></div><div><div><span>    </span><span>}</span><span>)</span><span>;</span></div></div><div><div><span>  </span><span>}</span></div></div><div><div><span>}</span></div></div>

• TypeScript

  <div><div><span>import </span><span>{</span><span><span> </span><span>Think</span><span> </span></span><span>}</span><span> from </span><span>"@cloudflare/think"</span><span>;</span></div></div><div><div><span>import </span><span>{</span></div></div><div><div><span><span>  </span></span><span>defineMessengers</span><span>,</span></div></div><div><div><span><span>  </span></span><span>ThinkMessengerStateAgent</span><span>,</span></div></div><div><div><span>}</span><span> from </span><span>"@cloudflare/think/messengers"</span><span>;</span></div></div><div><div><span><span>import </span><span>telegramMessenger</span><span> from </span></span><span>"@cloudflare/think/messengers/telegram"</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>export</span><span> </span><span>{</span><span> </span><span>ThinkMessengerStateAgent</span><span> </span><span>};</span></div></div><div><div>
  </div></div><div><div><span>export</span><span> </span><span>class</span><span> </span><span>SupportAgent</span><span> </span><span>extends</span><span> </span><span>Think</span><span><</span><span>Env</span><span>></span><span> </span><span>{</span></div></div><div><div><span>  </span><span>getMessengers</span><span>()</span><span> </span><span>{</span></div></div><div><div><span>    </span><span>return</span><span> </span><span>defineMessengers</span><span>(</span><span>{</span></div></div><div><div><span><span>      </span></span><span>telegram</span><span>:</span><span> </span><span>telegramMessenger</span><span>(</span><span>{</span></div></div><div><div><span><span>        </span></span><span>token</span><span>:</span><span> </span><span>this</span><span>.</span><span>env</span><span>.</span><span>TELEGRAM_BOT_TOKEN</span><span>,</span></div></div><div><div><span><span>        </span></span><span>userName</span><span>:</span><span> </span><span>"support_bot"</span><span>,</span></div></div><div><div><span><span>        </span></span><span>secretToken</span><span>:</span><span> </span><span>this</span><span>.</span><span>env</span><span>.</span><span>TELEGRAM_WEBHOOK_SECRET_TOKEN</span><span>,</span></div></div><div><div><span>      </span><span>}</span><span>)</span><span>,</span></div></div><div><div><span>    </span><span>}</span><span>)</span><span>;</span></div></div><div><div><span>  </span><span>}</span></div></div><div><div><span>}</span></div></div>

Each Chat SDK thread maps to its own Think sub-agent by default, so group chats and direct messages do not share memory. Multiple bots, custom conversation routing, and custom providers are all supported.

Scheduled tasks

Declare recurring, timezone-aware prompts and handlers with a typed domain-specific language (DSL). Think reconciles the declarations on startup and re-arms the next occurrence after each run, backed by durable idempotent submissions.

• JavaScript

  <div><div><span>import </span><span>{</span><span><span> </span><span>Think</span></span><span>,</span><span><span> </span><span>defineScheduledTasks</span><span> </span></span><span>}</span><span> from </span><span>"@cloudflare/think"</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>export</span><span> </span><span>class</span><span> </span><span>DigestAgent</span><span> </span><span>extends</span><span> </span><span>Think</span><span> </span><span>{</span></div></div><div><div><span>  </span><span>getScheduledTasks</span><span>()</span><span> </span><span>{</span></div></div><div><div><span>    </span><span>return</span><span> </span><span>defineScheduledTasks</span><span>(</span><span>{</span></div></div><div><div><span><span>      </span></span><span>weeklyCommitReport</span><span>:</span><span> </span><span>{</span></div></div><div><div><span><span>        </span></span><span>schedule</span><span>:</span><span> </span><span>"every week on monday at 09:00"</span><span>,</span></div></div><div><div><span><span>        </span></span><span>prompt</span><span>:</span></div></div><div><div><span>          </span><span>"Compile my GitHub commits for the last week and summarize them."</span><span>,</span></div></div><div><div><span>      </span><span>},</span></div></div><div><div><span><span>      </span></span><span>workout</span><span>:</span><span> </span><span>{</span></div></div><div><div><span><span>        </span></span><span>schedule</span><span>:</span><span> </span><span>"every day at 08:00 in Europe/London"</span><span>,</span></div></div><div><div><span><span>        </span></span><span>prompt</span><span>:</span><span> </span><span>"Start my workout."</span><span>,</span></div></div><div><div><span>      </span><span>},</span></div></div><div><div><span>    </span><span>}</span><span>)</span><span>;</span></div></div><div><div><span>  </span><span>}</span></div></div><div><div><span>}</span></div></div>

• TypeScript

  <div><div><span>import </span><span>{</span><span><span> </span><span>Think</span></span><span>,</span><span><span> </span><span>defineScheduledTasks</span><span> </span></span><span>}</span><span> from </span><span>"@cloudflare/think"</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>export</span><span> </span><span>class</span><span> </span><span>DigestAgent</span><span> </span><span>extends</span><span> </span><span>Think</span><span><</span><span>Env</span><span>></span><span> </span><span>{</span></div></div><div><div><span>  </span><span>getScheduledTasks</span><span>()</span><span> </span><span>{</span></div></div><div><div><span>    </span><span>return</span><span> </span><span>defineScheduledTasks</span><span>(</span><span>{</span></div></div><div><div><span><span>      </span></span><span>weeklyCommitReport</span><span>:</span><span> </span><span>{</span></div></div><div><div><span><span>        </span></span><span>schedule</span><span>:</span><span> </span><span>"every week on monday at 09:00"</span><span>,</span></div></div><div><div><span><span>        </span></span><span>prompt</span><span>:</span></div></div><div><div><span>          </span><span>"Compile my GitHub commits for the last week and summarize them."</span><span>,</span></div></div><div><div><span>      </span><span>},</span></div></div><div><div><span><span>      </span></span><span>workout</span><span>:</span><span> </span><span>{</span></div></div><div><div><span><span>        </span></span><span>schedule</span><span>:</span><span> </span><span>"every day at 08:00 in Europe/London"</span><span>,</span></div></div><div><div><span><span>        </span></span><span>prompt</span><span>:</span><span> </span><span>"Start my workout."</span><span>,</span></div></div><div><div><span>      </span><span>},</span></div></div><div><div><span>    </span><span>}</span><span>)</span><span>;</span></div></div><div><div><span>  </span><span>}</span></div></div><div><div><span>}</span></div></div>

Think Workflows

Run a model-driven reasoning step inside a Cloudflare Workflow with ThinkWorkflow and step.prompt(), with durable typed structured output, long waits, and approval gates.

• JavaScript

  <div><div><span>import </span><span>{</span><span><span> </span><span>z</span><span> </span></span><span>}</span><span> from </span><span>"zod"</span><span>;</span></div></div><div><div><span>import </span><span>{</span><span><span> </span><span>ThinkWorkflow</span><span> </span></span><span>}</span><span> from </span><span>"@cloudflare/think/workflows"</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>const</span><span> </span><span>draftSchema</span><span> </span><span>=</span><span> </span><span>z</span><span>.</span><span>object</span><span>(</span><span>{</span></div></div><div><div><span><span>  </span></span><span>title</span><span>:</span><span> </span><span>z</span><span>.</span><span>string</span><span>()</span><span>,</span></div></div><div><div><span><span>  </span></span><span>summary</span><span>:</span><span> </span><span>z</span><span>.</span><span>string</span><span>()</span><span>,</span></div></div><div><div><span><span>  </span></span><span>labels</span><span>:</span><span> </span><span>z</span><span>.</span><span>array</span><span>(</span><span>z</span><span>.</span><span>string</span><span>())</span><span>,</span></div></div><div><div><span>}</span><span>)</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>export</span><span> </span><span>class</span><span> </span><span>TriageWorkflow</span><span> </span><span>extends</span><span> </span><span>ThinkWorkflow</span><span> </span><span>{</span></div></div><div><div><span>  </span><span>async</span><span> </span><span>run</span><span>(</span><span>event</span><span>,</span><span> </span><span>step</span><span>)</span><span> </span><span>{</span></div></div><div><div><span>    </span><span>const</span><span> </span><span>draft</span><span> </span><span>=</span><span> </span><span>await</span><span> </span><span>step</span><span>.</span><span>prompt</span><span>(</span><span>"triage-issue"</span><span>,</span><span> </span><span>{</span></div></div><div><div><span><span>      </span></span><span>prompt</span><span>:</span><span> </span><span>`Triage issue #</span><span>${</span><span>event</span><span>.</span><span>payload</span><span>.</span><span>issueNumber</span><span>}</span><span>`</span><span>,</span></div></div><div><div><span><span>      </span></span><span>output</span><span>:</span><span> </span><span>draftSchema</span><span>,</span></div></div><div><div><span><span>      </span></span><span>timeout</span><span>:</span><span> </span><span>"3 days"</span><span>,</span></div></div><div><div><span>    </span><span>}</span><span>)</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>    </span><span>await</span><span> </span><span>step</span><span>.</span><span>do</span><span>(</span><span>"apply-labels"</span><span>,</span><span> </span><span>async</span><span> </span><span>()</span><span> </span><span>=></span><span> </span><span>{</span></div></div><div><div><span>      </span><span>await</span><span> </span><span>this</span><span>.</span><span>agent</span><span>.</span><span>applyLabels</span><span>(</span><span>draft</span><span>.</span><span>labels</span><span>)</span><span>;</span></div></div><div><div><span>    </span><span>}</span><span>)</span><span>;</span></div></div><div><div><span>  </span><span>}</span></div></div><div><div><span>}</span></div></div>

• TypeScript

  <div><div><span>import </span><span>{</span><span><span> </span><span>z</span><span> </span></span><span>}</span><span> from </span><span>"zod"</span><span>;</span></div></div><div><div><span>import </span><span>{</span><span><span> </span><span>ThinkWorkflow</span><span> </span></span><span>}</span><span> from </span><span>"@cloudflare/think/workflows"</span><span>;</span></div></div><div><div><span>import type </span><span>{</span><span><span> </span><span>ThinkWorkflowStep</span><span> </span></span><span>}</span><span> from </span><span>"@cloudflare/think/workflows"</span><span>;</span></div></div><div><div><span>import type </span><span>{</span><span><span> </span><span>AgentWorkflowEvent</span><span> </span></span><span>}</span><span> from </span><span>"agents/workflows"</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>const</span><span> </span><span>draftSchema</span><span> </span><span>=</span><span> </span><span>z</span><span>.</span><span>object</span><span>(</span><span>{</span></div></div><div><div><span><span>  </span></span><span>title</span><span>:</span><span> </span><span>z</span><span>.</span><span>string</span><span>()</span><span>,</span></div></div><div><div><span><span>  </span></span><span>summary</span><span>:</span><span> </span><span>z</span><span>.</span><span>string</span><span>()</span><span>,</span></div></div><div><div><span><span>  </span></span><span>labels</span><span>:</span><span> </span><span>z</span><span>.</span><span>array</span><span>(</span><span>z</span><span>.</span><span>string</span><span>())</span><span>,</span></div></div><div><div><span>}</span><span>)</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>export</span><span> </span><span>class</span><span> </span><span>TriageWorkflow</span><span> </span><span>extends</span><span> </span><span>ThinkWorkflow</span><span><</span><span>TriageAgent</span><span>,</span><span> </span><span>Params</span><span>></span><span> </span><span>{</span></div></div><div><div><span>  </span><span>async</span><span> </span><span>run</span><span>(</span><span>event</span><span>:</span><span> </span><span>AgentWorkflowEvent</span><span><</span><span>Params</span><span>>,</span><span> </span><span>step</span><span>:</span><span> </span><span>ThinkWorkflowStep</span><span>)</span><span> </span><span>{</span></div></div><div><div><span>    </span><span>const</span><span> </span><span>draft</span><span> </span><span>=</span><span> </span><span>await</span><span> </span><span>step</span><span>.</span><span>prompt</span><span>(</span><span>"triage-issue"</span><span>,</span><span> </span><span>{</span></div></div><div><div><span><span>      </span></span><span>prompt</span><span>:</span><span> </span><span>`Triage issue #</span><span>${</span><span>event</span><span>.</span><span>payload</span><span>.</span><span>issueNumber</span><span>}</span><span>`</span><span>,</span></div></div><div><div><span><span>      </span></span><span>output</span><span>:</span><span> </span><span>draftSchema</span><span>,</span></div></div><div><div><span><span>      </span></span><span>timeout</span><span>:</span><span> </span><span>"3 days"</span><span>,</span></div></div><div><div><span>    </span><span>}</span><span>)</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>    </span><span>await</span><span> </span><span>step</span><span>.</span><span>do</span><span>(</span><span>"apply-labels"</span><span>,</span><span> </span><span>async</span><span> </span><span>()</span><span> </span><span>=></span><span> </span><span>{</span></div></div><div><div><span>      </span><span>await</span><span> </span><span>this</span><span>.</span><span>agent</span><span>.</span><span>applyLabels</span><span>(</span><span>draft</span><span>.</span><span>labels</span><span>)</span><span>;</span></div></div><div><div><span>    </span><span>}</span><span>)</span><span>;</span></div></div><div><div><span>  </span><span>}</span></div></div><div><div><span>}</span></div></div>

Production hardening for durable chat recovery

Durable chat turns have always been designed to survive a mid-turn deploy or Durable Object eviction. This release is a major hardening pass on that machinery for production.

• Better recovery during deploys. Turns now ride through continuous deploys and evictions without losing completed work or re-running tools that already ran.
• A live "recovering…" signal. useAgentChat exposes a new isRecovering flag, so a recovering turn shows progress instead of looking frozen. Most UIs render isStreaming || isRecovering as "busy".
• Stalled streams recover. Set chatStreamStallTimeoutMs to route a hung provider stream into the same recovery path instead of leaving an infinite spinner.
• Sub-agents re-attach. On parent recovery, an in-flight agentTool() child is re-attached to its result rather than abandoned and re-run, so long-running children no longer lose work under deploys.

MCP transport improvements

• Resumable streams — In-flight tool calls over Server-Sent Events (SSE) survive a dropped connection. Clients reconnect with Last-Event-ID and replay anything they missed.
• Readable server IDs — addMcpServer accepts an optional id, so tools surface as readable keys (for example tool_github_create_pull_request) instead of opaque connection IDs.
• Better handling of concurrent requests — Overlapping JSON-RPC requests are now correctly correlated to their responses across the HTTP and RPC transports.

Other improvements

• Compaction — A Session's tokenCounter now also drives the compaction boundary decision ("what to compress"), not just the fire/no-fire trigger.
• @cloudflare/worker-bundler — Adds a virtualModules option to createWorker to provide in-memory module source during bundling.
• Client-tool continuations — Parallel tool results now coalesce into a single continuation, immediate resume requests attach to the pending continuation, and server-side needsApproval continuations resume reliably after approval.

Upgrade

To update to the latest version:

<span>npm</span><span> i agents@latest @cloudflare/think@latest @cloudflare/ai-chat@latest</span>

<span>yarn</span><span> add agents@latest @cloudflare/think@latest @cloudflare/ai-chat@latest</span>

<span>pnpm</span><span> add agents@latest @cloudflare/think@latest @cloudflare/ai-chat@latest</span>

<span>bun</span><span> add agents@latest @cloudflare/think@latest @cloudflare/ai-chat@latest</span>

Refer to the Agents API reference and Chat agents documentation for more information.

Cloudflare has updated Logpush datasets:

New datasets

• Turnstile Events: A new dataset with fields including ASN, Action, BrowserMajor, BrowserName, ClientIP, CountryCode, EventType, Hostname, OSMajor, OSName, Sitekey, Timestamp, and UserAgent.

For the complete field definitions for each dataset, refer to Logpush datasets.

A new Beta release for the macOS Cloudflare One Client is now available on the beta releases downloads page.

This release introduces the new Cloudflare One Client UI for macOS! You can expect a cleaner and more intuitive design as well as easier access to common actions and information. Here are some of the many things we have found our users appreciate:

• Right click context menu to access the most common client actions quickly
• Built-in captive portal login experience

Additional Changes and improvements

• The client now applies DNS search suffixes configured in your device profile / network policy. Administrators can push a list of DNS search domains that the client appends to single-label queries, alongside any system-configured suffixes. See DNS search suffixes for details.
• Administrators can now control which virtual networks (VNETs) are available to which users via WARP device profile settings in the Zero Trust dashboard. Previously, every VNET in the organization was visible to every device; you can now scope the VNET picker per profile so users only see the networks relevant to them. See VNET availability for details.
• Added a local-file signal source for Emergency Disconnect. In addition to the existing HTTPS polling mechanism, administrators can now configure WARP to monitor for a file on disk; the presence of the file triggers an emergency disconnect even if both Cloudflare and your own infrastructure are unreachable. Either signal being asserted triggers disconnect; both must be cleared for normal operation to resume.
• Added new warp-cli debug commands for interactive connection diagnosis. See Extra debug logging for details.
• The local DNS proxy now supports DNSSEC passthrough. DNSSEC-signed responses are forwarded to the application intact (including DO/AD bits and RRSIG records), so applications that validate DNSSEC locally — including resolvers and the dig/drill tooling — work correctly through the client.
• Added a new MDM format for organization-wide settings, including a cleaner way to configure the compliance environment (e.g. FedRAMP). The previous per-configuration approach still works, but the new format is now recommended. See the updated Cloudflare One MDM documentation for details.
• Client Certificate device-posture checks now support template variables (e.g. ${serial_number}, ${device_uuid}) in the Subject Alternative Name field, matching what the documentation has always claimed. Previously only the Common Name field accepted variables, which broke posture rules that pinned identity to a SAN entry.
• Fixed the in-client captive-portal browser rendering a blank "Success" page on some airline Wi-Fi networks (United inflight Wi-Fi was the reported case). The browser now reliably loads the airline's real portal page so users can complete sign-in from inside the client instead of having to open a separate browser.
• Fixed an issue in proxy mode where hostnames containing underscores (e.g. ai_app.com) were rejected, breaking apps that depend on such hostnames (notably ChatGPT sandbox apps). The local proxy now accepts underscore-containing hostnames in CONNECT requests.

Known issues

• Registration may hang at "Checking your organization configuration" due to IPC errors. A system reboot should resolve the error, allowing registration to proceed.
• Split tunnel list configuration is not available in the new UI. Management of split tunnel entries is currently only possible via warp-cli tunnel ip and warp-cli tunnel host. UI support will be added in a future release.

A new Beta release for the Windows Cloudflare One Client is now available on the beta releases downloads page.

This release introduces the new Cloudflare One Client UI for Windows! You can expect a cleaner and more intuitive design as well as easier access to common actions and information. Here are some of the many things we have found our users appreciate:

• Right click context menu to access the most common client actions quickly
• Built-in captive portal login experience

Additional Changes and improvements

• The client now applies DNS search suffixes configured in your device profile / network policy. Administrators can push a list of DNS search domains that the client appends to single-label queries, alongside any system-configured suffixes. See DNS search suffixes for details.
• Administrators can now control which virtual networks (VNETs) are available to which users via WARP device profile settings in the Zero Trust dashboard. Previously, every VNET in the organization was visible to every device; you can now scope the VNET picker per profile so users only see the networks relevant to them. See VNET availability for details.
• Added mandatory authentication. When enabled via MDM, the Cloudflare One Client blocks all Internet traffic from the moment the machine boots until the user authenticates, closing the visibility gap on newly deployed devices and during re-authentication. See the announcement blog and documentation for details.
• Added a local-file signal source for Emergency Disconnect. In addition to the existing HTTPS polling mechanism, administrators can now configure WARP to monitor for a file on disk; the presence of the file triggers an emergency disconnect even if both Cloudflare and your own infrastructure are unreachable. Either signal being asserted triggers disconnect; both must be cleared for normal operation to resume.
• Added new warp-cli debug commands for interactive connection diagnosis. See Extra debug logging for details.
• The local DNS proxy now supports DNSSEC passthrough. DNSSEC-signed responses are forwarded to the application intact (including DO/AD bits and RRSIG records), so applications that validate DNSSEC locally — including resolvers and the dig/drill tooling — work correctly through the client.
• Added a new MDM format for organization-wide settings, including a cleaner way to configure the compliance environment (e.g. FedRAMP). The previous per-configuration approach still works, but the new format is now recommended. See the updated Cloudflare One MDM documentation for details.
• Client Certificate device-posture checks now support template variables (e.g. ${serial_number}, ${device_uuid}) in the Subject Alternative Name field, matching what the documentation has always claimed. Previously only the Common Name field accepted variables, which broke posture rules that pinned identity to a SAN entry.
• The UseWebView2 registry value (HKLM\SOFTWARE\Cloudflare\CloudflareWARP\UseWebView2 = y) is once again honored by the new GUI for authentication, so administrators who prefer the embedded WebView2 browser for sign-in can opt back in. This setting was effectively ignored in the previous release; the default browser was always used. This key is now also honored for re-authentications.
• Fixed a crash in the authentication browser when navigating to a site that prompts for browser permissions (microphone, camera, notifications, etc.). The same fix had previously landed for the captive-portal browser; this extends it to the auth browser.
• Fixed an issue in proxy mode where hostnames containing underscores (e.g. ai_app.com) were rejected, breaking apps that depend on such hostnames (notably ChatGPT sandbox apps). The local proxy now accepts underscore-containing hostnames in CONNECT requests.

Known issues

• Registration authentication for devices via the integrated WebView2 browser is unavailable in this version as a temporary measure. As a result, the client will utilize the default browser on the device to complete the authentication process.
• An error indicating that Microsoft Edge can't read and write to its data directory may be displayed during captive portal login; this error is benign and can be dismissed.
• Registration may hang at "Checking your organization configuration" due to IPC errors. A system reboot should resolve the error, allowing registration to proceed.
• Split tunnel list configuration is not available in the new UI. Management of Split Tunnel entries is currently only possible via warp-cli tunnel ip and warp-cli tunnel host. UI support will be added in a future release.
• Windows ARM may prompt the user to close running applications while trying to install this version. Simply click “Ok” with the default highlighted option.
• DNS resolution may be broken when the following conditions are all true:
  • The client is in Secure Web Gateway without DNS filtering (tunnel-only) mode.
  • A custom DNS server address is configured on the primary network adapter.
  • The custom DNS server address on the primary network adapter is changed while the client is connected.
    To work around this issue, please reconnect the client by selecting "disconnect" and then "connect" in the client user interface.

Security Insights scans now run more often. Cloudflare scans Free accounts every 7 days, Pro and Business accounts every 3 days, and Enterprise accounts daily.

In addition, all accounts and zones now receive scans by default. You no longer need to enable scans before Cloudflare checks your account for misconfigurations, vulnerabilities, and other security risks.

Granular on-demand scans are now available on any plan. You can trigger an on-demand scan for any zone, insight, insight type from the Cloudflare dashboard in order to quickly re-check your security posture after remediating an issue.

To learn more, refer to the Security Insights documentation.

Sandboxes can expose a service running inside the container on a public preview URL through the sandbox.tunnels namespace. The SDK uses cloudflared inside the sandbox so you can share a running service without configuring exposePort() or a custom domain.

By default, sandbox.tunnels.get(port) creates a quick tunnel on a zero-config *.trycloudflare.com URL — no Cloudflare account, DNS record, or custom domain required. This is perfect for quick development and for .workers.dev deployments.

• JavaScript

  <div><div><span>import </span><span>{</span><span><span> </span><span>getSandbox</span><span> </span></span><span>}</span><span> from </span><span>"@cloudflare/sandbox"</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>const</span><span> </span><span>sandbox</span><span> </span><span>=</span><span> </span><span>getSandbox</span><span>(</span><span>env</span><span>.</span><span>Sandbox</span><span>,</span><span> </span><span>"my-sandbox"</span><span>)</span><span>;</span></div></div><div><div><span>await</span><span> </span><span>sandbox</span><span>.</span><span>startProcess</span><span>(</span><span>"python -m http.server 8080"</span><span>)</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>const</span><span> </span><span>tunnel</span><span> </span><span>=</span><span> </span><span>await</span><span> </span><span>sandbox</span><span>.</span><span>tunnels</span><span>.</span><span>get</span><span>(</span><span>8080</span><span>)</span><span>;</span></div></div><div><div><span>console</span><span>.</span><span>log</span><span>(</span><span>tunnel</span><span>.</span><span>url</span><span>)</span><span>;</span><span> </span><span>// → https://random-words-here.trycloudflare.com</span></div></div>

• TypeScript

  <div><div><span>import </span><span>{</span><span><span> </span><span>getSandbox</span><span> </span></span><span>}</span><span> from </span><span>"@cloudflare/sandbox"</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>const</span><span> </span><span>sandbox</span><span> </span><span>=</span><span> </span><span>getSandbox</span><span>(</span><span>env</span><span>.</span><span>Sandbox</span><span>,</span><span> </span><span>"my-sandbox"</span><span>)</span><span>;</span></div></div><div><div><span>await</span><span> </span><span>sandbox</span><span>.</span><span>startProcess</span><span>(</span><span>"python -m http.server 8080"</span><span>)</span><span>;</span></div></div><div><div>
  </div></div><div><div><span>const</span><span> </span><span>tunnel</span><span> </span><span>=</span><span> </span><span>await</span><span> </span><span>sandbox</span><span>.</span><span>tunnels</span><span>.</span><span>get</span><span>(</span><span>8080</span><span>)</span><span>;</span></div></div><div><div><span>console</span><span>.</span><span>log</span><span>(</span><span>tunnel</span><span>.</span><span>url</span><span>)</span><span>;</span><span> </span><span>// → https://random-words-here.trycloudflare.com</span></div></div>

Named tunnels

For more control you can create a named tunnel through sandbox.tunnels.get(port, { name }). A named tunnel binds a hostname (<name>.<your-zone>) backed by a Cloudflare Tunnel and a CNAME record on your zone resulting in something like https://my-app-preview.example.com.

Unlike quick tunnels, which generate a new random URL each time, a named tunnel produces a persistent URL that survives container restarts. This makes named tunnels suitable for production use cases where you want control over the tunnel and it's origin.

• JavaScript

  <div><div><span>const</span><span> </span><span>tunnel</span><span> </span><span>=</span><span> </span><span>await</span><span> </span><span>sandbox</span><span>.</span><span>tunnels</span><span>.</span><span>get</span><span>(</span><span>8080</span><span>,</span><span> </span><span>{</span><span> name</span><span>:</span><span> </span><span>"my-app-preview"</span><span> </span><span>}</span><span>)</span><span>;</span></div></div><div><div><span>console</span><span>.</span><span>log</span><span>(</span><span>tunnel</span><span>.</span><span>url</span><span>)</span><span>;</span><span> </span><span>// → https://my-app-preview.example.com</span></div></div>

• TypeScript

  <div><div><span>const</span><span> </span><span>tunnel</span><span> </span><span>=</span><span> </span><span>await</span><span> </span><span>sandbox</span><span>.</span><span>tunnels</span><span>.</span><span>get</span><span>(</span><span>8080</span><span>,</span><span> </span><span>{</span><span> name</span><span>:</span><span> </span><span>"my-app-preview"</span><span> </span><span>}</span><span>)</span><span>;</span></div></div><div><div><span>console</span><span>.</span><span>log</span><span>(</span><span>tunnel</span><span>.</span><span>url</span><span>)</span><span>;</span><span> </span><span>// → https://my-app-preview.example.com</span></div></div>

Calling sandbox.destroy() tears down the Cloudflare Tunnel and the associated DNS record alongside the container, so you do not leave dangling tunnels or records behind.

Upgrade

To update to the latest version:

<span>npm</span><span> i @cloudflare/sandbox@latest</span>

<span>yarn</span><span> add @cloudflare/sandbox@latest</span>

<span>pnpm</span><span> add @cloudflare/sandbox@latest</span>

<span>bun</span><span> add @cloudflare/sandbox@latest</span>

For full API details, refer to the Sandbox tunnels reference.