Skip to content
Cloudflare Docs
Docs DirectoryAPIsSDKs

Changelog

New updates and improvements at Cloudflare.

Subscribe to RSS View RSS feeds
All products
hero image

  1. AI Search instances now include built-in storage and namespace Workers Bindings

    AI Search

    New AI Search instances created after today will work differently. New instances come with built-in storage and a vector index, so you can upload a file, have it indexed immediately, and search it right away.

    Additionally new Workers Bindings are now available to use with AI Search. The new namespace binding lets you create and manage instances at runtime, and cross-instance search API lets you query across multiple instances in one call.

    Built-in storage and vector index

    All new instances now comes with built-in storage which allows you to upload files directly to it using the Items API or the dashboard. No R2 buckets to set up, no external data sources to connect first.

    TypeScript
    const instance = env.AI_SEARCH.get("my-instance");
    

    // upload and wait for indexing to complete
    const item = await instance.items.uploadAndPoll("faq.md", content);
    

    // search immediately after indexing
    const results = await instance.search({
      messages: [{ role: "user", content: "onboarding guide" }],
    });

    Namespace binding

    The new ai_search_namespaces binding replaces the previous env.AI.autorag() API provided through the AI binding. It gives your Worker access to all instances within a namespace and lets you create, update, and delete instances at runtime without redeploying.

    JSONC
    // wrangler.jsonc
    {
      "ai_search_namespaces": [
        {
          "binding": "AI_SEARCH",
          "namespace": "default",
        },
      ],
    }
    TypeScript
    // create an instance at runtime
    const instance = await env.AI_SEARCH.create({
      id: "my-instance",
    });

    For migration details, refer to Workers binding migration. For more on namespaces, refer to Namespaces.

    Within the new AI Search binding, you now have access to a Search and Chat API on the namespace level. Pass an array of instance IDs and get one ranked list of results back.

    TypeScript
    const results = await env.AI_SEARCH.search({
      messages: [{ role: "user", content: "What is Cloudflare?" }],
      ai_search_options: {
        instance_ids: ["product-docs", "customer-abc123"],
      },
    });

    Refer to Namespace-level search for details.

  1. AI Search now has hybrid search and relevance boosting

    AI Search

    AI Search now supports hybrid search and relevance boosting, giving you more control over how results are found and ranked.

    Hybrid search combines vector (semantic) search with BM25 keyword search in a single query. Vector search finds chunks with similar meaning, even when the exact words differ. Keyword search matches chunks that contain your query terms exactly. When you enable hybrid search, both run in parallel and the results are fused into a single ranked list.

    You can configure the tokenizer (porter for natural language, trigram for code), keyword match mode (and for precision, or for recall), and fusion method (rrf or max) per instance:

    TypeScript
    const instance = await env.AI_SEARCH.create({
      id: "my-instance",
      index_method: { vector: true, keyword: true },
      fusion_method: "rrf",
      indexing_options: { keyword_tokenizer: "porter" },
      retrieval_options: { keyword_match_mode: "and" },
    });

    Refer to Search modes for an overview and Hybrid search for configuration details.

    Relevance boosting

    Relevance boosting lets you nudge search rankings based on document metadata. For example, you can prioritize recent documents by boosting on timestamp, or surface high-priority content by boosting on a custom metadata field like priority.

    Configure up to 3 boost fields per instance or override them per request:

    TypeScript
    const results = await env.AI_SEARCH.get("my-instance").search({
      messages: [{ role: "user", content: "deployment guide" }],
      ai_search_options: {
        retrieval: {
          boost_by: [
            { field: "timestamp", direction: "desc" },
            { field: "priority", direction: "desc" },
          ],
        },
      },
    });

    Refer to Relevance boosting for configuration details.

  1. Artifacts now in beta: versioned filesystem with Git access

    Artifacts

    Artifacts is now in private beta. Artifacts is Git-compatible storage built for scale: create tens of millions of repos, fork from any remote, and hand off a URL to any Git client. It provides a versioned filesystem for storing and exchanging file trees across Workers, the REST API, and any Git client, running locally or within an agent.

    You can read the announcement blog ↗ to learn more about what Artifacts does, how it works, and how to create repositories for your agents to use.

    Artifacts has three API surfaces:

    • Workers bindings (for creating and managing repositories)
    • REST API (for creating and managing repos from any other compute platform)
    • Git protocol (for interacting with repos)

    As an example: you can use the Workers binding to create a repo and read back its remote URL:

    TypeScript
    # Create a thousand, a million or ten million repos: one for every agent, for every upstream branch, or every user.
    const created = await env.PROD_ARTIFACTS.create("agent-007");
    const remote = (await created.repo.info())?.remote;

    Or, use the REST API to create a repo inside a namespace from your agent(s) running on any platform:

    Terminal window
    curl --request POST "https://artifacts.cloudflare.net/v1/api/namespaces/some-namespace/repos" --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" --header "Content-Type: application/json" --data '{"name":"agent-007"}'

    Any Git client that speaks smart HTTP can use the returned remote URL:

    Terminal window
    # Agents know git.
    # Every repository can act as a git repo, allowing agents to interact with Artifacts the way they know best: using the git CLI.
    git clone https://x:${REPO_TOKEN}@artifacts.cloudflare.net/some-namespace/agent-007.git

    To learn more, refer to Get started, Workers binding, and Git protocol.

  1. Increased concurrency, creation rate, and queued instance limits for Workflows instances

    Workflows Workers

    Workflows limits have been raised to the following:

    LimitPreviousNew
    Concurrent instances (running in parallel)10,00050,000
    Instance creation rate (per account)100/second per account300/second per account, 100/second per workflow
    Queued instances per Workflow 11 million2 million

    These increases apply to all users on the Workers Paid plan. Refer to the Workflows limits documentation for more details.

    Footnotes

    1. Queued instances are instances that have been created or awoken and are waiting for a concurrency slot. ↩

  1. Browser Rendering is now Browser Run

    Browser Run

    We are renaming Browser Rendering to Browser Run. The name Browser Rendering never fully captured what the product does. Browser Run lets you run full browser sessions on Cloudflare's global network, drive them with code or AI, record and replay sessions, crawl pages for content, debug in real time, and let humans intervene when your agent needs help.

    Along with the rename, we have increased limits for Workers Paid plans and redesigned the Browser Run dashboard.

    We have 4x-ed concurrency limits for Workers Paid plan users:

    • Concurrent browsers per account: 30 → 120 per account
    • New browser instances: 30 per minute → 1 per second
    • REST API rate limits: recently increased from 3 to 10 requests per second

    Rate limits across the limits page are now expressed in per-second terms, matching how they are enforced. No action is needed to benefit from the higher limits.

    The redesigned dashboard ↗ now shows every request in a single Runs tab, not just browser sessions but also quick actions like screenshots, PDFs, markdown, and crawls. Filter by endpoint, view target URLs, status, and duration, and expand any row for more detail.

    Browser Run dashboard Runs tab with browser sessions and quick actions visible in one list, and an expanded crawl job showing its progress

    We are also shipping several new features:

    • Live View, Human in the Loop, and Session Recordings - See what your agent is doing in real time, let humans step in when automation hits a wall, and replay any session after it ends.
    • WebMCP - Websites can expose structured tools for AI agents to discover and call directly, replacing slow screenshot-analyze-click loops.

    For the full story, read our Agents Week blog Browser Run: Give your agents a browser ↗.

  1. Browser Run adds Live View, Human in the Loop, and Session Recordings

    Browser Run

    When browser automation fails or behaves unexpectedly, it can be hard to understand what happened. We are shipping three new features in Browser Run (formerly Browser Rendering) to help:

    Live View

    Live View lets you see what your agent is doing in real time. The page, DOM, console, and network requests are all visible for any active browser session. Access Live View from the Cloudflare dashboard, via the hosted UI at live.browser.run, or using native Chrome DevTools.

    Human in the Loop

    When your agent hits a snag like a login page or unexpected edge case, it can hand off to a human instead of failing. With Human in the Loop, a human steps into the live browser session through Live View, resolves the issue, and hands control back to the script.

    Today, you can step in by opening the Live View URL for any active session. Next, we are adding a handoff flow where the agent can signal that it needs help, notify a human to step in, then hand control back to the agent once the issue is resolved.

    Browser Run Human in the Loop demo where an AI agent searches Amazon, selects a product, and requests human help when authentication is needed to buy

    Session Recordings

    Session Recordings records DOM state so you can replay any session after it ends. Enable recordings by passing recording: true when launching a browser. After the session closes, view the recording in the Cloudflare dashboard under Browser Run > Runs, or retrieve via API using the session ID. Next, we are adding the ability to inspect DOM state and console output at any point during the recording.

    Browser Run session recording showing an automated browser navigating the Sentry Shop and adding a bomber jacket to the cart

    To get started, refer to the documentation for Live View, Human in the Loop, and Session Recording.

  1. Browser Run adds WebMCP support

    Browser Run

    Browser Run (formerly Browser Rendering) now supports WebMCP ↗ (Web Model Context Protocol), a new browser API from the Google Chrome team.

    The Internet was built for humans, so navigating as an AI agent today is unreliable. WebMCP lets websites expose structured tools for AI agents to discover and call directly. Instead of slow screenshot-analyze-click loops, agents can call website functions like searchFlights() or bookTicket() with typed parameters, making browser automation faster, more reliable, and less fragile.

    Browser Run lab session showing WebMCP tools being discovered and executed in the Chrome DevTools console to book a hotel

    With WebMCP, you can:

    • Discover website tools - Use navigator.modelContextTesting.listTools() to see available actions on any WebMCP-enabled site
    • Execute tools directly - Call navigator.modelContextTesting.executeTool() with typed parameters
    • Handle human-in-the-loop interactions - Some tools pause for user confirmation before completing sensitive actions

    WebMCP requires Chrome beta features. We have an experimental pool with browser instances running Chrome beta so you can test emerging browser features before they reach stable Chrome. To start a WebMCP session, add lab=true to your /devtools/browser request:

    Terminal window
    curl -X POST "https://api.cloudflare.com/client/v4/accounts/{account_id}/browser-rendering/devtools/browser?lab=true&keep_alive=300000" \
      -H "Authorization: Bearer {api_token}"

    Combined with the recently launched CDP endpoint, AI agents can also use WebMCP. Connect an MCP client to Browser Run via CDP, and your agent can discover and call website tools directly. Here's the same hotel booking demo, this time driven by an AI agent through OpenCode:

    Browser Run Live View showing an AI agent navigating a hotel booking site in real time

    For a step-by-step guide, refer to the WebMCP documentation.

  1. Independent MFA for Access applications

    Access

    Cloudflare Access now supports independent multi-factor authentication (MFA), allowing you to enforce MFA requirements without relying on your identity provider (IdP). This feature addresses common gaps in IdP-based MFA, such as inconsistent MFA policies across different identity providers or the need for additional security layers beyond what the IdP provides.

    Independent MFA supports the following authenticator types:

    • Authenticator application — Time-based one-time passwords (TOTP) using apps like Google Authenticator, Microsoft Authenticator, or Authy.
    • Security key — Hardware security keys such as YubiKeys.
    • Biometrics — Built-in device authenticators including Apple Touch ID, Apple Face ID, and Windows Hello.

    Configuration levels

    You can configure MFA requirements at three levels:

    LevelDescription
    OrganizationEnforce MFA by default for all applications in your account.
    ApplicationRequire or turn off MFA for a specific application.
    PolicyRequire or turn off MFA for users who match a specific policy.

    Settings at lower levels (policy) override settings at higher levels (organization), giving you granular control over MFA enforcement.

    User enrollment

    Users enroll their authenticators through the App Launcher. To help with onboarding, administrators can share a direct enrollment link: <your-team-name>.cloudflareaccess.com/AddMfaDevice.

    To get started with Independent MFA, refer to Independent MFA.

  1. Agent Lee adds Write Operations and Generative UI

    Agents

    Agent Lee adds Write Operations and Generative UI

    We are excited to announce two major capability upgrades for Agent Lee, the AI co-pilot built directly into the Cloudflare dashboard. Agent Lee is designed to understand your specific account configuration, and with this release, it moves from a passive advisor to an active assistant that can help you manage your infrastructure and visualize your data through natural language.

    Take action with Write Operations

    Agent Lee can now perform changes on your behalf across your Cloudflare account. Whether you need to update DNS records, modify SSL/TLS settings, or configure Workers routes, you can simply ask.

    To ensure security and accuracy, every write operation requires explicit user approval. Before any change is committed, Agent Lee will present a summary of the proposed action in plain language. No action is taken until you select Confirm, and this approval requirement is enforced at the infrastructure level to prevent unauthorized changes.

    Example requests:

    • "Add an A record for blog.example.com pointing to 192.0.2.10."
    • "Enable Always Use HTTPS on my zone."
    • "Set the SSL mode for example.com to Full (strict)."

    Visualize data with Generative UI

    Understanding your traffic and security trends is now as easy as asking a question. Agent Lee now features Generative UI, allowing it to render inline charts and structured data visualizations directly within the chat interface using your actual account telemetry.

    Example requests:

    • "Show me a chart of my traffic over the last 7 days."
    • "What does my error rate look like for the past 24 hours?"
    • "Graph my cache hit rate for example.com this week."

    Availability

    These features are currently available in Beta for all users on the Free plan. To get started, log in to the Cloudflare dashboard ↗ and select Ask AI in the upper right corner.

    To learn more about how to interact with your account using AI, refer to the Agent Lee documentation.

  1. New, streamlined creation experience for Access Applications and Gateway Policies

    Cloudflare One

    The Cloudflare One dashboard now features redesigned builders for two core workflows: creating Gateway policies and configuring self-hosted Access applications.

    Gateway rule builder

    The Gateway rule builder now features a redesigned user experience, bringing it in line with the Access policy builder experience. Improvements include:

    • Streamlined UX with clearer states and improved user interactions
    • Wirefilter editing for viewing and editing Gateway rules directly from wirefilter expressions
    • Preview state to review the impact of your policy in a simple graphic
    New Gateway rule builder

    For more information, refer to Traffic policies.

    Access application builder for self-hosted apps

    The self-hosted Access application builder now offers a simplified creation workflow with fewer steps from setup to save. Improvements include:

    • New application selection experience that makes choosing the right application type before you begin easier.
    • Streamlined creation flow with fewer clicks to build and save an application
    • Inline policy creation for building Access policies directly within the application creation flow
    • Preview state to understand how your policies enforce user access before saving
    New Access application builder

    For more information, refer to self-hosted applications.

  1. Control where your Containers run with regional and jurisdictional placement

    Containers

    You can now specify placement constraints to control where your Containers run.

    ConstraintValuesUse case
    regionsENAM, WNAM, EEUR, WEURGeographic placement
    jurisdictioneu, fedrampCompliance boundaries

    Use regions to limit placement to specific geographic areas. Use jurisdiction to restrict containers to compliance boundaries — eu maps to European regions (EEUR, WEUR) and fedramp maps to North American regions (ENAM, WNAM).

    Refer to Containers architecture for more details on placement.

  1. Last seen timestamp for Cloudflare One Client devices is more consistent

    Digital Experience Monitoring

    The last seen timestamp for Cloudflare One Client devices is now more consistent across the dashboard. IT teams will see more consistent information about the most recent client event between a device and Cloudflare's network.

  1. New TenantID and Firewall for AI fields in Logpush datasets

    Logs

    Cloudflare has added new fields to multiple Logpush datasets:

    TenantID field

    The following Gateway and Zero Trust datasets now include a TenantID field:

    Firewall for AI fields

    The following datasets now include Firewall for AI fields:

    • Firewall Events:

      • FirewallForAIInjectionScore: The score indicating the likelihood of a prompt injection attack in the request.
      • FirewallForAIPIICategories: List of PII categories detected in the request.
      • FirewallForAITokenCount: The number of tokens in the request.
      • FirewallForAIUnsafeTopicCategories: List of unsafe topic categories detected in the request.

    • HTTP Requests:

      • FirewallForAIInjectionScore: The score indicating the likelihood of a prompt injection attack in the request.
      • FirewallForAIPIICategories: List of PII categories detected in the request.
      • FirewallForAITokenCount: The number of tokens in the request.
      • FirewallForAIUnsafeTopicCategories: List of unsafe topic categories detected in the request.

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

  1. Privacy Proxy metrics now available via GraphQL Analytics API

    Privacy Proxy

    Privacy Proxy metrics are now queryable through Cloudflare's GraphQL Analytics API, the new default method for accessing Privacy Proxy observability data. All metrics are available through a single endpoint:

    Terminal window
    curl https://api.cloudflare.com/client/v4/graphql \
      --header "Authorization: Bearer <API_TOKEN>" \
      --header "Content-Type: application/json" \
      --data '{
        "query": "{ viewer { accounts(filter: { accountTag: $accountTag }) { privacyProxyRequestMetricsAdaptiveGroups(filter: { date_geq: $startDate, date_leq: $endDate }, limit: 10000, orderBy: [date_ASC]) { count dimensions { date } } } } }",
        "variables": {
          "accountTag": "<YOUR_ACCOUNT_TAG>",
          "startDate": "2026-04-04",
          "endDate": "2026-04-06"
        }
      }'

    Available nodes

    Four GraphQL nodes are now live, providing aggregate metrics across all key dimensions of your Privacy Proxy deployment:

    • privacyProxyRequestMetricsAdaptiveGroups — Request volume, error rates, status codes, and proxy status breakdowns.
    • privacyProxyIngressConnMetricsAdaptiveGroups — Client-to-proxy connection counts, bytes transferred, and latency percentiles.
    • privacyProxyEgressConnMetricsAdaptiveGroups — Proxy-to-origin connection counts, bytes transferred, and latency percentiles.
    • privacyProxyAuthMetricsAdaptiveGroups — Authentication attempt counts by method and result.

    All nodes support filtering by time, data center (coloCode), and endpoint, with additional node-specific dimensions such as transport protocol and authentication method.

    What this means for existing OpenTelemetry users

    OpenTelemetry-based metrics export remains available. The GraphQL Analytics API is now the recommended default method — a plug-and-play method that requires no collector infrastructure, saving engineering overhead.

    Learn more

  1. WAF Release - 2026-04-15

    WAF

    This week's release introduces a new detection for a critical Remote Code Execution (RCE) vulnerability in Mesop (CVE-2026-33057), alongside protections for high-impact vulnerabilities in Cisco Secure Firewall Management Center (CVE-2026-20079) and FortiClient EMS (CVE-2026-21643). Additionally, this release includes an update to our existing React Server DoS coverage to address recently identified resource exhaustion vectors (CVE-2026-23869).

    Key Findings

    • Cisco Secure FMC (CVE-2026-20079): A vulnerability in the web-based management interface of Cisco Secure Firewall Management Center (FMC) that allows an unauthenticated, remote attacker to execute arbitrary commands or bypass security filters.

    • FortiClient EMS (CVE-2026-21643): A critical vulnerability in the FortiClient EMS permitting unauthorized access or administrative configuration manipulation via crafted HTTP requests.

    • Mesop (CVE-2026-33057): A vulnerability in the Mesop Python-based UI framework where unauthenticated attackers can execute arbitrary code by sending specially crafted, Base64-encoded payloads in the request body.

    Impact

    Successful exploitation of these vulnerabilities could allow unauthenticated attackers to execute arbitrary code, gain administrative control over network management infrastructure, or trigger server-side resource exhaustion. Administrators are strongly encouraged to apply official vendor updates.

    RulesetRule IDLegacy Rule IDDescriptionPrevious ActionNew ActionComments
    Cloudflare Managed Ruleset N/ACisco Secure FMC - RCE via upgradeReadinessCall - CVE:CVE-2026-20079LogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/AFortiClient EMS - Pre-Auth SQL Injection - CVE:CVE-2026-21643LogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/AMesop - Remote Code Execution - Base64 Payload - CVE:CVE-2026-33057LogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/AReact Server - DOS - CVE:CVE-2026-23864 - 1 - BetaLogBlockThis rule has been merged into the original rule "React Server - DOS - CVE:CVE-2026-23864 - 1" (ID: )
    Cloudflare Managed Ruleset N/AXSS, HTML Injection - Link Tag - URI (beta)N/ADisabledThis is a new detection.
    Cloudflare Managed Ruleset N/AXSS, HTML Injection - Embed Tag - URI (beta)N/ADisabledThis is a new detection.

  1. WAF Release - Scheduled changes for 2026-04-20

    WAF
    Announcement DateRelease DateRelease BehaviorLegacy Rule IDRule IDDescriptionComments
    2026-04-152026-04-20LogN/A Command Injection - Generic 8 - uri - BetaThis is a new detection.
    2026-04-152026-04-20DisabledN/A Command Injection - Generic 8 - body - Beta

    This is a new detection. This rule will be merged into the original rule "Command Injection - Generic 8" (ID: )

    2026-04-152026-04-20LogN/A MySQL - SQLi - Executable Comment - Beta

    This is a new detection. This rule will be merged into the original rule "MySQL - SQLi - Executable Comment" (ID: )

    2026-04-152026-04-20LogN/A MySQL - SQLi - Executable Comment - HeadersThis is a new detection.
    2026-04-152026-04-20LogN/A This is a new detection.
    2026-04-152026-04-20LogN/A MySQL - SQLi - Executable Comment - URIThis is a new detection.
    2026-04-152026-04-20LogN/A Magento 2 - Unrestricted file upload - 2This is a new detection.
    2026-04-152026-04-20LogN/A Apache ActiveMQ - Remote Code Execution - CVE:CVE-2026-34197This is a new detection.
    2026-04-152026-04-20LogN/A SQLi - Probing - uri - BetaThis is a new detection.
    2026-04-152026-04-20LogN/A SQLi - Probing - header - BetaThis is a new detection.
    2026-04-152026-04-20DisabledN/A SQLi - Probing - body - Beta

    This is a new detection. This rule will be merged into the original rule "SQLi - Probing" (ID: )

    2026-04-152026-04-20LogN/A SQLi - Sleep Function - Beta

    This is a new detection. This rule will be merged into the original rule "SQLi - Sleep Function" (ID: )

    2026-04-152026-04-20LogN/A SQLi - Sleep Function - HeadersThis is a new detection.
    2026-04-152026-04-20LogN/A SQLi - Sleep Function - URIThis is a new detection.
    2026-04-152026-04-20LogN/A XSS, HTML Injection - Embed Tag - Headers (beta)This is a new detection.
    2026-04-152026-04-20LogN/A

    XSS, HTML Injection - IFrame Tag - Src and Srcdoc Attributes - Headers (beta)

    		This is a new detection.
    2026-04-152026-04-20LogN/A XSS, HTML Injection - Link Tag - Headers (beta)This is a new detection.

  1. DLP account-level settings

    Data Loss Prevention

    Account-level DLP settings are now available in Cloudflare One. You can now configure advanced DLP settings at the account level, including OCR, AI context analysis, and payload masking. This provides consistent enforcement across all DLP profiles and simplifies configuration management.

    Key changes:

    • Consistent enforcement: Settings configured at the account level apply to all DLP profiles
    • Simplified migration: Settings enabled on any profile are automatically migrated to account level
    • Deprecation notice: Profile-level advanced settings will be deprecated in a future release

    Migration details:

    During the migration period, if a setting is enabled on any profile, it will automatically be enabled at the account level. This means profiles that previously had a setting disabled may now have it enabled if another profile in the account had it enabled.

    Settings are evaluated using OR logic - a setting is enabled if it is turned on at either the account level or the profile level. However, profile-level settings cannot be enabled when the account-level setting is off.

    For more details, refer to the DLP advanced settings documentation.

  1. Manage Browser Rendering sessions with Wrangler CLI

    Browser Run

    Browser Rendering now supports wrangler browser commands, letting you create, manage, and view browser sessions directly from your terminal, streamlining your workflow. Since Wrangler handles authentication, you do not need to pass API tokens in your commands.

    The following commands are available:

    CommandDescription
    wrangler browser createCreate a new browser session
    wrangler browser closeClose a session
    wrangler browser listList active sessions
    wrangler browser viewView a live browser session

    The create command spins up a browser instance on Cloudflare's network and returns a session URL. Once created, you can connect to the session using any CDP-compatible client like Puppeteer, Playwright, or MCP clients to automate browsing, scrape content, or debug remotely.

    Terminal window
    wrangler browser create

    Use --keepAlive to set the session keep-alive duration (60-600 seconds):

    Terminal window
    wrangler browser create --keepAlive 300

    The view command auto-selects when only one session exists, or prompts for selection when multiple sessions are available.

    All commands support --json for structured output, and because these are CLI commands, you can incorporate them into scripts to automate session management.

    For full usage details, refer to the Wrangler commands documentation.

  1. Introducing Cloudflare Mesh

    Cloudflare One

    Cloudflare Mesh is now available (blog post ↗). Mesh connects your services and devices with post-quantum encrypted networking, allowing you to route traffic privately between servers, laptops, and phones over TCP, UDP, and ICMP.

    Cloudflare Mesh network map showing nodes and devices connected through Cloudflare

    What Cloudflare Mesh does

    • Assigns a private Mesh IP to every enrolled device and node.
    • Enables any participant to reach any other participant by IP — including client-to-client, without deploying any infrastructure.
    • Supports CIDR routes for subnet routing through Mesh nodes.
    • Supports high availability with active-passive replicas for nodes with routes.
    • All traffic flows through Cloudflare, so Gateway network policies, device posture checks, and access rules apply to every connection.

    What changed

    • WARP Connector is now Cloudflare Mesh. Existing WARP Connectors are now called mesh nodes. All existing deployments continue to work — no migration required.
    • Peer-to-peer connectivity is now called Mesh connectivity and is part of the Cloudflare Mesh documentation.
    • Mesh node limit increased from 10 to 50 per account.
    • New dashboard experience ↗ at Networking > Mesh with an interactive network map, node management, route configuration, diagnostics, and a setup wizard.

    Get started

    Refer to the Cloudflare Mesh documentation to set up your first Mesh network.

  1. Improved OAuth experience for consent and management

    Cloudflare Fundamentals

    OAuth allows third-party applications to access your Cloudflare account on your behalf — like when Wrangler deploys Workers or when monitoring tools read your analytics. You now have granular control over which accounts these applications can access, plus the ability to revoke access anytime.

    What's new

    Choose which accounts to authorize

    When authorizing an OAuth application, you can now select specific accounts instead of granting access to all your accounts:

    • Account-by-account selection — Choose exactly which accounts the application can access
    • "All accounts" option — Still available for trusted tools like Wrangler This gives you precise control who can access your data.

    The OAuth consent screen now shows:

    • What the application can access — Explicit list of permissions being requested
    • Who created the application — Application owner and contact information
    • Which accounts you're authorizing — Checkboxes for account selection

    Revoke access anytime

    Manage authorized OAuth applications from your profile:

    • See all connected apps — View every OAuth application with access to your accounts
    • Review permissions and scope — Check what each application can do and which accounts it can access
    • Revoke instantly — Remove access with one click when you no longer need it To manage your OAuth applications, navigate to Profile > Access Management > Connected Applications ↗.

    Why this matters

    These updates give you:

    • Granular control — Authorize apps per-account instead of all-or-nothing
    • Transparency — Know exactly what you're authorizing before you consent
    • Security — Limit blast radius by restricting access to only necessary accounts
    • Easy cleanup — Revoke access when applications are no longer needed

    Learn more

    Read more about these improvements in our blog post: Improving the OAuth consent experience ↗.

  1. Logpush to BigQuery — Cloudflare dashboard support

    Logpush Logs

    You can now configure Logpush jobs to Google BigQuery directly from the Cloudflare dashboard, in addition to the existing API-based setup.

    Previously, setting up a BigQuery Logpush destination required using the Logpush API. Now you can create and manage BigQuery Logpush jobs from the Logpush page in the Cloudflare dashboard by selecting Google BigQuery as the destination and entering your Google Cloud project ID, dataset ID, table ID, and service account credentials.

    For more information, refer to Enable Logpush to Google BigQuery.

  1. Generate citations on Cloudflare Radar

    Radar

    Radar shareable widgets now include a generate citation action, making it easier to reference Cloudflare Radar ↗ data in research papers and other publications.

    Screenshot of the generate citation icon in the widget action bar

    Select the citation icon to open a modal with five supported citation styles:

    • BibTeX
    • APA
    • MLA
    • Chicago
    • RIS
    Screenshot of the citation modal with format options

    Explore the feature on any shareable widget at Cloudflare Radar ↗.

  1. Email obfuscation decode script is now non-render-blocking

    WAF

    The decode script injected by Email Address Obfuscation now loads with the defer attribute. This means the script no longer blocks page rendering. It downloads in parallel with HTML parsing and executes after the document is fully parsed, before the DOMContentLoaded event.

    This improves page loading performance, contributing to better Core Web Vitals, for all zones with Email Address Obfuscation on. No action is required.

    If you have custom JavaScript that depends on email addresses being decoded at a specific point during page load, note that the decode script now executes after HTML parsing completes rather than inline during parsing.

  1. VPC Networks and Cloudflare Mesh support now in public beta

    Workers VPC

    VPC Network bindings now give your Workers access to any service in your private network without pre-registering individual hosts or ports. This complements existing VPC Service bindings, which scope each binding to a specific host and port.

    You can bind to a Cloudflare Tunnel by tunnel_id to reach any service on the network where that tunnel is running, or bind to your Cloudflare Mesh network using cf1:network to reach any Mesh node, client device, or subnet route in your account:

    JSONC
    {
      "vpc_networks": [
        {
          "binding": "MESH",
          "network_id": "cf1:network",
          "remote": true
        }
      ]
    }

    At runtime, fetch() routes through the network to reach the service at the IP and port you specify:

    JavaScript
    const response = await env.MESH.fetch("http://10.0.1.50:8080/api/data");

    For configuration options and examples, refer to VPC Networks and Connect Workers to Cloudflare Mesh.

  1. Containers and Sandboxes are now generally available

    Containers

    Cloudflare Containers and Sandboxes are now generally available.

    Containers let you run more workloads on the Workers platform, including resource-intensive applications, different languages, and CLI tools that need full Linux environments.

    Since the initial launch of Containers, there have been significant improvements to Containers' performance, stability, and feature set. Some highlights include:

    The Sandbox SDK provides isolated environments for running untrusted code securely, with a simple TypeScript API for executing commands, managing files, and exposing services. This makes it easier to secure and manage your agents at scale. Some additions since launch include:

    For more information, refer to Containers and Sandbox SDK documentation.

Search all changelog entries