Skip to content

Changelog

New updates and improvements at Cloudflare.

All products
hero image
  1. Resource Tagging is now in public beta and rolling out to all Cloudflare accounts over the coming days. You can attach custom key-value metadata to your Cloudflare resources and query across your entire account to find what you need.

    What's included

    • Broad resource type support — Tag zones, custom hostnames, Cloudflare Tunnels, Workers, D1 databases, R2 buckets, KV namespaces, Durable Object namespaces, Queues, Stream videos, Images, Access applications, Gateway rules, AI Gateways, and more. Refer to the full list of supported resource types.
    • Powerful filtering — Query tagged resources using AND/OR logic, negation, and key-only matching. Combine up to 20 filters per query to build precise resource views.
    • Account and zone-level endpoints — Full CRUD operations across both scopes.
    • Token-based authentication — Tagging supports Account Owned Tokens that persist independently of individual users, so your automation keeps running through credential rotations and team changes.
    • Flexible role support — Super Administrators, Workers Admins, and Tag Admins can all manage tags.

    API-first by design

    The API is the primary interface for Resource Tagging and the recommended path for all workflows — scripting tag assignments, building CI/CD pipelines, or integrating with your infrastructure-as-code toolchain.

    Dashboard UI

    You can also view and manage tagged resources directly in the Cloudflare dashboard. Navigate to Manage Account > Resource Tagging to see all tagged resources across your account, filter by resource name or tag, and add or edit tags inline.

    Tagged Resources dashboard

    What's coming next

    In future releases, expect support for additional resource types across the Cloudflare platform, tag-based access control policies for scoping user permissions to tagged resources, billing and usage attribution by tag for breaking down costs by team, project, or environment, and Terraform provider support for managing tags declaratively.

    Current limitations

    • PUT replaces all tags on a resource (no partial update). Use the GET, merge, PUT workflow to modify individual tags safely.
    • DELETE removes all tags from a resource. To remove a single tag, PUT the remaining tags back.
    • Querying tags for a resource that has never been tagged returns 500 instead of 404. This is a known beta limitation.

    To get started, refer to the Resource Tagging documentation.

  1. We have introduced a unified investigation workspace within Brand Protection to help analysts manage complex brand portfolios. Instead of jumping between individual queries, you can now consolidate your workflow into a single, cohesive view.

    What's new

    • You can now elect multiple saved queries from your dashboard to generate a consolidated "Combined Matches" view. This allows you to triage results from different brand queries in one unified table
    • You can open query extended views in distinct tabs within the Brand Protection dashboard. This enables you to maintain multiple investigation contexts simultaneously and switch between them without losing your place.
    • You can reset your workspace using the new "Clear Selection" action, making it easier to pivot between different investigation sets.

    Key benefits

    • Eliminate fragmented workflows by viewing all matches across different query buckets in a single table, reducing the need to click through dozens of individual query pages
    • Correlate related campaigns by seeing similar domains or infrastructure patterns that appear across multiple saved queries

    Learn more in our Brand Protection documentation.

  1. This week's release focuses on new improvements to enhance coverage.

    Key Findings

    • Existing rule enhancements have been deployed to improve detection resilience against broad classes of web attacks and strengthen behavioral coverage.

    Continuous Rule Improvements

    We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.

    RulesetRule IDLegacy Rule IDDescriptionPrevious ActionNew ActionComments
    Cloudflare Managed Ruleset N/APostgreSQL - SQLi - COPY - BetaLogBlock

    This is a new detection. This rule is merged into the original rule "PostgreSQL - SQLi - COPY - Body (ID: ). The rule previously known as "PostgreSQL - SQLi - COPY" is now renamed to "PostgreSQL - SQLi - COPY - Body".

    Cloudflare Managed Ruleset N/APostgreSQL - SQLi - COPY - HeadersLogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/APostgreSQL - SQLi - COPY - URILogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - AND/OR MAKE_SET/ELT - BetaLogBlock

    This is a new detection. This rule is merged into the original rule "SQLi - AND/OR MAKE_SET/ELT - Body" (ID: ). The rule previously known as "SQLi - AND/OR MAKE_SET/ELT" is now renamed to "SQLi - AND/OR MAKE_SET/ELT - Body".

    Cloudflare Managed Ruleset N/ASQLi - AND/OR MAKE_SET/ELT - HeadersLogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - AND/OR MAKE_SET/ELT - URILogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - Common Patterns - BetaLogBlock

    This is a new detection. This rule is merged into the original rule "SQLi - Common Patterns - Body" (ID: ). The rule previously known as "SQLi - Common Patterns" is now renamed to "SQLi - Common Patterns - Body".

    Cloudflare Managed Ruleset N/ASQLi - Common Patterns - HeadersLogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - Common Patterns - URILogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - Equation - BetaLogBlock

    This is a new detection. This rule is merged into the original rule "SQLi - Equation - Body" (ID: ). The rule previously known as "SQLi - Equation" is now renamed to "SQLi - Equation - Body".

    Cloudflare Managed Ruleset N/ASQLi - Equation - HeadersLogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - Equation - URILogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - AND/OR Digit Operator Digit - BetaLogBlock

    This is a new detection. This rule is merged into the original rule "SQLi - AND/OR Digit Operator Digit - Body" (ID: ). The rule previously known as "SQLi - AND/OR Digit Operator Digit" is now renamed to "SQLi - AND/OR Digit Operator Digit - Body".

    Cloudflare Managed Ruleset N/ASQLi - AND/OR Digit Operator Digit - HeadersLogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - AND/OR Digit Operator Digit - URILogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - Benchmark Function - BetaLogBlock

    This is a new detection. This rule is merged into the original rule "SQLi - Benchmark Function - Body" (ID: ). The rule previously known as "SQLi - Benchmark Function" is now renamed to "SQLi - Benchmark Function - Body".

    Cloudflare Managed Ruleset N/ASQLi - Benchmark Function - HeadersLogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - Benchmark Function - URILogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - Comparison - BetaLogBlock

    This is a new detection. This rule is merged into the original rule "SQLi - Comparison - Body" (ID: ). The rule previously known as "SQLi - Comparison" is now renamed to "SQLi - Comparison - Body".

    Cloudflare Managed Ruleset N/ASQLi - Comparison - HeadersLogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - Comparison - URILogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - String Concatenation - Body - BetaLogBlockThis is a new detection. This rule is merged into the original rule "SQLi - String Concatenation - Headers" (ID: ).The rule previously known as "SQLi - String Concatenation - Headers" is now renamed to "SQLi - String Concatenation - Body".
    Cloudflare Managed Ruleset N/ASQLi - String Concatenation - HeadersLogBlockThis is a new detection.(Former Id was )
    Cloudflare Managed Ruleset N/ASQLi - String Concatenation - URILogBlockThis is a new detection. (Former Id was )
    Cloudflare Managed Ruleset N/ASQLi - SELECT Expression - BetaLogBlock

    This is a new detection. This rule is merged into the original rule "SQLi - SELECT Expression - Body" (ID: ). The rule previously known as "SQLi - SELECT Expression" is now renamed to "SQLi - SELECT Expression - Body".

    Cloudflare Managed Ruleset N/ASQLi - SELECT Expression - HeadersLogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - SELECT Expression - URILogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - ORD and ASCII - BetaLogBlock

    This is a new detection. This rule is merged into the original rule "SQLi - ORD and ASCII- Body" (ID: ). The rule previously known as "SQLi - ORD and ASCII" is now renamed to "SQLi - ORD and ASCII- Body".

    Cloudflare Managed Ruleset N/ASQLi - ORD and ASCII - URILogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - ORD and ASCII - HeadersLogBlockThis is a new detection.
    Cloudflare Managed Ruleset N/ASQLi - Destructive OperationsLogBlockThis is a new detection.
  1. Announcement DateRelease DateRelease BehaviorLegacy Rule IDRule IDDescriptionComments
    2026-04-272026-05-04DisabledN/A Command Injection - Generic 9 - Body Vector - Beta

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

    2026-04-272026-05-04DisabledN/A Command Injection - Generic 9 - Header Vector - Beta

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

    2026-04-272026-05-04DisabledN/A Command Injection - Generic 9 - URI Vector - Beta

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

    2026-04-272026-05-04DisabledN/A Command Injection - Sleep - Beta

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

    2026-04-272026-05-04DisabledN/A Command Injection - Sleep - Headers

    This is a new detection.

    2026-04-272026-05-04DisabledN/A Command Injection - Sleep - URI

    This is a new detection.

    2026-04-272026-05-04DisabledN/A Fortinet FortiSandbox - Command Injection - CVE:CVE-2026-39808

    This is a new detection.

    2026-04-272026-05-04LogN/A SmarterMail - Remote Code Execution - CVE:CVE-2026-24423

    This is a new detection.

    2026-04-272026-05-04DisabledN/A SQLi - DROP - 2 - URI

    This is a new detection.

    2026-04-272026-05-04DisabledN/A SQLi - DROP - 2 - Headers

    This is a new detection.

    2026-04-272026-05-04DisabledN/A SQLi - DROP - 2 - Beta

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

    2026-04-272026-05-04DisabledN/A PHP Object Injection - 2 - URI

    This is a new detection.

    2026-04-272026-05-04DisabledN/A PHP Object Injection - 2 - Headers

    This is a new detection.

    2026-04-272026-05-04DisabledN/A PHP Object Injection - 2 - Body - Beta

    This is a new detection. This rule will be merged into the original rule "PHP Object Injection - 2" (ID: )

    2026-04-272026-05-04DisabledN/A Remote Code Execution - Common Bash Bypass - Body - Beta

    This is a new detection. This rule will be merged into the original rule "Remote Code Execution - Common Bash Bypass" (ID: )

    2026-04-272026-05-04DisabledN/A Remote Code Execution - Common Bash Bypass - URI

    This is a new detection.

    2026-04-272026-05-04DisabledN/A Remote Code Execution - Common Bash Bypass - Headers

    This is a new detection.

    2026-04-212026-05-04LogN/A XSS, HTML Injection - Object Tag - Body (beta)This is a new detection.
    2026-04-212026-05-04LogN/A XSS, HTML Injection - Object Tag - Headers (beta)This is a new detection.
    2026-04-212026-05-04LogN/A XSS, HTML Injection - Object Tag - URI (beta)This is a new detection.
  1. Zero Trust Network Session Logs are now generated for all traffic proxied through Cloudflare Gateway, regardless of on-ramp type. This includes traffic from proxy endpoints (PAC files) and Browser Isolation egress — on-ramps that previously did not generate session logs.

    Customers who already consume the zero_trust_network_sessions dataset via Logpush or Log Explorer may see increased log volume if they use these on-ramps.

    For field definitions, refer to Zero Trust Network Session Logs. For traffic analysis, refer to Network session analytics.

  1. Terraform Provider v5.19.0 introduces 14 new resources spanning AI Gateway, Pipelines, R2 Data Catalog, User Groups, Vulnerability Scanner, Workers Observability, and Zero Trust capabilities. This release significantly improves the v4 to v5 migration experience with automatic state upgraders for 26 resources, working seamlessly with the new tf-migrate CLI tool to automate resource renames, attribute updates, and moved block generation. Together, these enhancements reduce manual migration effort and minimize risk when upgrading from v4 to v5.

    Note: cmd/migrate is deprecated in favor of tf-migrate and will be removed in a future release (#7062)

    New Resources

    • cloudflare_ai_gateway: Manage AI Gateway instances
    • cloudflare_certificate_authorities_hostname_associations: Manage mTLS certificate hostname associations
    • cloudflare_custom_page_asset: Manage custom page assets
    • cloudflare_pipeline: Manage Cloudflare Pipelines
    • cloudflare_r2_data_catalog: Manage R2 Data Catalog
    • cloudflare_user_group: Manage user groups
    • cloudflare_user_group_members: Manage user group memberships
    • cloudflare_vulnerability_scanner_credential: Manage vulnerability scanner credentials
    • cloudflare_vulnerability_scanner_credential_set: Manage vulnerability scanner credential sets
    • cloudflare_vulnerability_scanner_target_environment: Manage vulnerability scanner target environments
    • cloudflare_workers_observability_destination: Manage Workers Observability destinations
    • cloudflare_zero_trust_device_ip_profile: Manage Zero Trust device IP profiles
    • cloudflare_zero_trust_device_subnet: Manage Zero Trust device subnets
    • cloudflare_zero_trust_dlp_settings: Manage Zero Trust DLP settings

    Features

    V4 to V5 Migration State Upgraders

    State upgraders added for seamless migration from v4 to v5 for the following resources:

    • account
    • account_member
    • account_token
    • authenticated_origin_pulls
    • authenticated_origin_pulls_hostname_certificate
    • byo_ip_prefix
    • custom_hostname
    • custom_ssl
    • leaked_credential_check
    • leaked_credential_check_rule
    • logpush_ownership_challenge
    • mtls_certificate
    • observatory_scheduled_test
    • pages_domain
    • regional_tiered_cache
    • turnstile_widget
    • workers_custom_domain
    • zero_trust_device_custom_profile
    • zero_trust_device_default_profile
    • zero_trust_device_posture_integration
    • zero_trust_gateway_certificate
    • zero_trust_gateway_settings
    • zero_trust_organization
    • zero_trust_tunnel_cloudflared_virtual_network
    • zone_setting

    Other Features

    • ruleset: Add content_converter and redirects_for_ai_training support to configuration rules
    • zero_trust_gateway_logging: Make importable

    Bug Fixes

    Migration & State Management

    • account_member: Add UseStateForUnknown to status field to prevent drift
    • authenticated_origin_pulls_settings: Fix no prior schema and no-op upgrade
    • certificate_pack: Initialize empty lists instead of null in state upgrader to prevent drift
    • migrations: Handle ambiguous schema_version state for v4/v5 coexistence
    • zero_trust_access_policy: Fix nil pointer panic in state upgrader; set PriorSchema nil for v4 state upgrade

    Resource-Specific Fixes

    • ai_search_instance: Restore original defaults for cache and cache_threshold; conflict resolution
    • apijson: Return empty object from MarshalForPatch when no fields are serializable
    • dlp_predefined_profile: Eliminate perpetual entries and enabled_entries drift
    • dns_record: Avoid unnecessary drift for ipv4_only and ipv6_only attributes; remove private_routing default value
    • drift: Preserve prior state values for optional fields not returned by API
    • healthcheck: Use buildHealthcheckPlanChecks helper for correct plan checks per migration source; update assertions
    • leaked_credential_check_rule: Handle empty ID from v4 provider state migration
    • list_item: Remove context
    • logpush_job: Update model for migration
    • ruleset: Fix migration; add redirects_for_ai_training to SourceV4ActionParametersModel; fix duplicate model attribute
    • worker: Add UseStateForUnknown() plan modifiers and update tests for observability.traces
    • workers_custom_domain: Handle HTTP 200 no content header; update assertions
    • workers_script: Fix model drift
    • zero_trust_access_identity_provider: Fix boolean drifts
    • zero_trust_device_managed_networks: Upgrade resource state
    • zero_trust_gateway_policy: Make filters Computed+Optional to prevent drift
    • zero_trust_gateway_settings: Fix breaking changes; implement sweeper to reset account to clean defaults
    • zone_setting: Migration test improvements and fixes

    Documentation

    • healthcheck: Update port description to clarify defaults
    • Add application-scoped access policy migration guidance
    • Update zone_settings_override migration guide for tf-migrate v2 workflow

    For more information

  1. We're excited to announce tf-migrate, a purpose-built CLI tool that simplifies migrating from Cloudflare Terraform Provider v4 to v5.

    v5 is stable and ready for production

    Terraform Provider v5 is stable and actively receiving updates. We encourage all users to migrate to v5 to take advantage of ongoing enhancements and new capabilities.

    Cloudflare uses tf-migrate to migrate our own infrastructure — the same tool we're providing to the community — ensuring the best possible migration experience.

    What tf-migrate does

    tf-migrate automates the tedious and error-prone parts of the v4 to v5 migration process:

    • Resource type renames – Automatically updates cloudflare_recordcloudflare_dns_record, cloudflare_access_applicationcloudflare_zero_trust_access_application, and 40+ other renamed resources
    • Attribute transformations – Updates field names (e.g., valuecontent for DNS records) and restructures nested blocks
    • Moved block generation – Creates Terraform 1.8+ moved blocks to prevent resource replacements and ensure zero-downtime migrations
    • Cross-file reference updates – Automatically finds and updates all references to renamed resources across your entire configuration
    • Dry-run mode – Preview all changes before applying them to ensure safety

    Combined with the automatic state upgraders introduced in v5.19+, tf-migrate eliminates the manual work and risk that previously made v5 migrations challenging. Tf-migrate operates directly on the config, and the built-in state upgraders handle the rest.

    Supported resources

    Tf-migrate currently supports the most common Terraform resources our customers use. We are actively working to expand coverage, with the most commonly used resources prioritized first.

    For the complete list of supported resources and their migration status, refer to the v5 Stabilization Tracker. This list is updated regularly as additional resources are stabilized and migration support is added.

    Resources not yet supported by tf-migrate will need to be migrated manually using the version 5 upgrade guide. The upgrade guide provides step-by-step instructions for handling resource renames, attribute changes, and state migrations.

    Get started

    We have been releasing Betas over the past month and a half while testing this tool. See the full changelog of those Betas here: tf-migrate releases.

  1. Independent MFA in Cloudflare Access now supports two additional organization-level controls:

    • Restrict authenticators by AAGUID — Limit enrollment to a specific set of WebAuthn authenticators using their AAGUID. This is useful for organizations that require FIPS-validated security keys or company-issued hardware. AAGUIDs are managed through a new List type.
    • AMR matching — Skip the independent MFA prompt when the identity provider has already performed an equivalent MFA. Access reads the amr claim defined in RFC 8176 and matches supported values such as hwk, otp, and fpt to the authenticator types allowed on the application or policy. This prevents users from having to complete MFA twice when their identity provider already enforces it.

    To get started, refer to Independent MFA.

  1. Audit Logs v2 now supports organization-level audit logs. Org Admins can retrieve audit events for actions performed at the organization level via the Audit Logs v2 API.

    To retrieve organization-level audit logs, use the following endpoint:

    Terminal window
    GET https://api.cloudflare.com/client/v4/organizations/{organization_id}/logs/audit

    This release covers user-initiated actions performed through organization-level APIs. Audit logs for system-initiated actions, a dashboard UI, and Logpush support for organizations will be added in future releases.

    For more information, refer to the Audit Logs documentation.

  1. v6.10.0

    In this release, you'll see a number of breaking changes. This is primarily due to changes in OpenAPI definitions, which our libraries are based off of, and codegen updates that we rely on to read those OpenAPI definitions and produce our SDK libraries.

    Please ensure you read through the list of changes below before moving to this version - this will help you understand any down or upstream issues it may cause to your environments.

    Breaking Changes

    See the v6.10.0 Migration Guide for before/after code examples and actions needed for each change.

    Abuse Reports - Registrar WHOIS Report Field Removals

    Several fields have been removed from AbuseReportNewParamsBodyAbuseReportsRegistrarWhoisReportRegWhoRequest:

    • RegWhoGoodFaithAffirmation
    • RegWhoLawfulProcessingAgreement
    • RegWhoLegalBasis
    • RegWhoRequestType
    • RegWhoRequestedDataElements

    AI Search - Instance Params Restructured

    The InstanceNewParams and InstanceUpdateParams types have been significantly restructured. Many fields have been moved or removed:

    • InstanceNewParams.TokenID, Type, CreatedFromAISearchWizard, WorkerDomain removed
    • InstanceUpdateParams — most configuration fields removed (including IndexMethod, IndexingOptions, MaxNumResults, Metadata, Paused, PublicEndpointParams, Reranking, RerankingModel, RetrievalOptions, RewriteModel, RewriteQuery, ScoreThreshold, SourceParams, Summarization, SummarizationModel, SystemPromptAISearch, SystemPromptIndexSummarization, SystemPromptRewriteQuery, TokenID, CreatedFromAISearchWizard, WorkerDomain)
    • InstanceSearchParams.Messages field removed along with InstanceSearchParamsMessage and InstanceSearchParamsMessagesRole types

    AI Search - InstanceItem Service Removed

    The InstanceItemService type has been removed. The items sub-resource at client.AISearch.Instances.Items no longer exists in the non-namespace path. Use client.AISearch.Namespaces.Instances.Items instead.

    AI Search - Token Types Removed

    The following types have been removed from the ai_search package:

    • TokenDeleteResponse
    • TokenListParams (and associated TokenListParamsOrderBy, TokenListParamsOrderByDirection)

    Email Security - Investigate Move Return Type Change

    The Investigate.Move.New() method now returns a raw slice instead of a paginated wrapper:

    • New() returns *[]InvestigateMoveNewResponse instead of *pagination.SinglePage[InvestigateMoveNewResponse]
    • NewAutoPaging() method removed

    Hyperdrive - Config Params Restructured

    The ConfigEditParams type lost its MTLS and Name fields. The HyperdriveMTLSParam type lost MTLS and Host fields. The Host field on origin config changed from param.Field[string] to a plain string.

    IAM - UserGroupMember Params and Return Types Changed

    The UserGroupMemberNewParams struct has been restructured and the New() method now returns a paginated response:

    • UserGroupMemberNewParams.Body renamed to UserGroupMemberNewParams.Members
    • UserGroupMemberNewParamsBody renamed to UserGroupMemberNewParamsMember
    • UserGroupMemberUpdateParams.Body renamed to UserGroupMemberUpdateParams.Members
    • UserGroupMemberUpdateParamsBody renamed to UserGroupMemberUpdateParamsMember
    • UserGroups.Members.New() returns *pagination.SinglePage[UserGroupMemberNewResponse] instead of *UserGroupMemberNewResponse

    IAM - UserGroup List Direction Type Changed

    The UserGroupListParams.Direction field changed from param.Field[string] to param.Field[UserGroupListParamsDirection] (typed enum with asc/desc values).

    Pipelines - Delete Methods Now Return Typed Responses

    Several delete methods across Pipelines now return typed responses instead of bare error:

    • Pipelines.DeleteV1() returns (*PipelineDeleteV1Response, error) instead of error
    • Pipelines.Sinks.Delete() returns (*SinkDeleteResponse, error) instead of error
    • Pipelines.Streams.Delete() returns (*StreamDeleteResponse, error) instead of error

    Queues - Message Response Types Removed

    The following response envelope types have been removed:

    • MessageBulkPushResponseSuccess
    • MessagePushResponseSuccess
    • MessageAckResponse fields RetryCount and Warnings removed

    Secrets Store - Pagination Wrapper Removal and Type Changes

    Methods now return direct types instead of SinglePage wrappers, and several internal types have been removed. Associated AutoPaging methods have also been removed:

    • Stores.New() returns *StoreNewResponse instead of *pagination.SinglePage[StoreNewResponse]
    • Stores.NewAutoPaging() method removed
    • Stores.Secrets.BulkDelete() returns *StoreSecretBulkDeleteResponse instead of *pagination.SinglePage[StoreSecretBulkDeleteResponse]
    • Stores.Secrets.BulkDeleteAutoPaging() method removed
    • Removed types: StoreDeleteResponse, StoreDeleteResponseEnvelopeResultInfo, StoreSecretDeleteResponse, StoreSecretDeleteResponseStatus, StoreSecretBulkDeleteResponse (old shape), StoreSecretBulkDeleteResponseStatus, StoreSecretDeleteResponseEnvelopeResultInfo
    • StoreNewParams restructured (old StoreNewParamsBody removed)
    • StoreSecretBulkDeleteParams restructured

    Stream - AudioTracks Return Type Change

    The AudioTracks.Get() method now returns a dedicated response type instead of a paginated list. The GetAutoPaging() method has been removed:

    • Get() returns *AudioTrackGetResponse instead of *pagination.SinglePage[Audio]
    • GetAutoPaging() method removed

    Stream - Clip Type Removal and Return Type Change

    The Clip.New() method now returns the shared Video type. The following types have been entirely removed:

    • Clip, ClipPlayback, ClipStatus, ClipWatermark

    Stream - Copy and Clip Params Field Removals

    • ClipNewParams.MaxDurationSeconds, ThumbnailTimestampPct, Watermark removed
    • CopyNewParams.ThumbnailTimestampPct, Watermark removed

    Stream - Download and Webhook Changes

    • DownloadNewResponseStatus type removed
    • WebhookUpdateResponse and WebhookGetResponse changed from interface{} type aliases to full struct types

    Zero Trust - Access AI Control MCP Portal Union Types Removed

    The following union interface types have been removed:

    • AccessAIControlMcpPortalListResponseServersUpdatedPromptsUnion
    • AccessAIControlMcpPortalListResponseServersUpdatedToolsUnion
    • AccessAIControlMcpPortalReadResponseServersUpdatedPromptsUnion
    • AccessAIControlMcpPortalReadResponseServersUpdatedToolsUnion

    Features

    Vulnerability Scanner (client.VulnerabilityScanner)

    NEW SERVICE: Full vulnerability scanning management

    • CredentialSets - CRUD for credential sets (New, Update, List, Delete, Edit, Get)
    • Credentials - Manage credentials within sets (New, Update, List, Delete, Edit, Get)
    • Scans - Create and manage vulnerability scans (New, List, Get)
    • TargetEnvironments - Manage scan target environments (New, Update, List, Delete, Edit, Get)

    AI Search - Namespaces (client.AISearch.Namespaces)

    NEW SERVICE: Namespace-scoped AI Search management

    • New(), Update(), List(), Delete(), ChatCompletions(), Read(), Search()
    • Instances - Namespace-scoped instances (New, Update, List, Delete, ChatCompletions, Read, Search, Stats)
    • Jobs - Instance job management (New, Update, List, Get, Logs)
    • Items - Instance item management (List, Delete, Chunks, NewOrUpdate, Download, Get, Logs, Sync, Upload)

    Browser Rendering - Devtools (client.BrowserRendering.Devtools)

    NEW SERVICE: DevTools protocol browser control

    • Session - List and get devtools sessions
    • Browser - Browser lifecycle management (New, Delete, Connect, Launch, Protocol, Version)
    • Page - Get page by target ID
    • Targets - Manage browser targets (New, List, Activate, Get)

    Registrar (client.Registrar)

    NEW: Domain check and search endpoints

    • Check() - POST /accounts/{account_id}/registrar/domain-check
    • Search() - GET /accounts/{account_id}/registrar/domain-search

    NEW: Registration management (client.Registrar.Registrations)

    • New(), List(), Edit(), Get()
    • RegistrationStatus.Get() - Get registration workflow status
    • UpdateStatus.Get() - Get update workflow status

    Cache - Origin Cloud Regions (client.Cache.OriginCloudRegions)

    NEW SERVICE: Manage origin cloud region configurations

    • New(), List(), Delete(), BulkDelete(), BulkEdit(), Edit(), Get(), SupportedRegions()

    Zero Trust - DLP Settings (client.ZeroTrust.DLP.Settings)

    NEW SERVICE: DLP settings management

    • Update(), Delete(), Edit(), Get()

    Radar

    • AgentReadiness.Summary() - Agent readiness summary by dimension
    • AI.MarkdownForAgents.Summary() - Markdown-for-agents summary
    • AI.MarkdownForAgents.Timeseries() - Markdown-for-agents timeseries

    IAM (client.IAM)

    • UserGroups.Members.Get() - Get details of a specific member in a user group
    • UserGroups.Members.NewAutoPaging() - Auto-paging variant for adding members
    • UserGroups.NewParams.Policies changed from required to optional

    Bot Management

    • ContentBotsProtection field added to BotFightModeConfiguration and SubscriptionConfiguration (block/disabled)

    Deprecations

    None in this release.

    Get started

  1. Custom Dashboards are now available to all Cloudflare customers. Build personalized views that highlight the metrics most critical to your infrastructure and security posture, moving beyond standard product dashboards.

    This update significantly expands the data available for visualization. Build charts based on any of the 100+ datasets available via the Cloudflare GraphQL API, covering everything from WAF events and Workers metrics to Load Balancing and Zero Trust logs.

    Log Explorer integration

    For Log Explorer customers, you can now turn raw log queries directly into dashboard charts. When you identify a specific pattern or spike while investigating logs, save that query as a visualization to monitor those signals in real-time without leaving the dashboard.

    Key benefits

    • Unified visibility: Consolidate signals from different Cloudflare products (for example, HTTP Traffic and R2 Storage) into a single view.
    • Flexible monitoring: Create charts that focus on specific status codes, ASN regions, or security actions that matter to your business.
    • Expanded limits: Log Explorer customers can create up to 100 dashboards (up from 25 for standard customers).
    Custom Dashboards home page showing dashboard list and chart previews

    To get started, refer to the Custom Dashboards documentation.

  1. R2 Data Catalog, a managed Apache Iceberg catalog built into R2, now removes unreferenced data files during automatic snapshot expiration. This improvement reduces storage costs and eliminates the need to run manual maintenance jobs to reclaim space from deleted data.

    Previously, snapshot expiration only cleaned up Iceberg metadata files such as manifests and manifest lists. Data files that were no longer referenced by active snapshots remained in R2 storage until you manually ran remove_orphan_files or expire_snapshots through an engine like Spark. This required extra operational overhead and left stale data files consuming storage.

    Snapshot expiration now handles both metadata and data file cleanup automatically. When a snapshot is expired, any data files that are no longer referenced by retained snapshots are removed from R2 storage.

    Terminal window
    # Enable catalog-level snapshot expiration
    npx wrangler r2 bucket catalog snapshot-expiration enable my-bucket \
    --older-than-days 7 \
    --retain-last 10

    To learn more about snapshot expiration and other automatic maintenance operations, refer to the table maintenance documentation.

  1. A new Network Overview page in the Cloudflare dashboard gives you a single starting point for network security and connectivity products.

    From the Network Overview page, you can:

    • Connect resources with Cloudflare Tunnel - Create tunnels to connect your infrastructure to Cloudflare without exposing it to the public Internet.
    • Monitor traffic with Network Flow - Get real-time visibility into traffic volume from your routers.
    • Configure Address Maps - Map dedicated static IPs or BYOIP prefixes to specific hostnames.
    • Explore Magic Transit and Cloudflare WAN - Set up DDoS protection for your networks and connectivity for your branch offices and data centers.

    To find it, go to Networking in the dashboard sidebar.

    If you already use Magic Transit, Cloudflare WAN, or other Cloudflare network services products, your existing experience is unchanged.

    Network Overview page in the Cloudflare dashboard
  1. Workflows now provides additional context inside step.do() callbacks and supports returning ReadableStream to handle larger step outputs.

    Step context properties

    The step.do() callback receives a context object with new properties alongside attempt:

    • step.name — The name passed to step.do()
    • step.count — How many times a step with that name has been invoked in this instance (1-indexed)
      • Useful when running the same step in a loop.
    • config — The resolved step configuration, including timeout and retries with defaults applied
    TypeScript
    type ResolvedStepConfig = {
    retries: {
    limit: number;
    delay: WorkflowDelayDuration | number;
    backoff?: "constant" | "linear" | "exponential";
    };
    timeout: WorkflowTimeoutDuration | number;
    };
    type WorkflowStepContext = {
    step: {
    name: string;
    count: number;
    };
    attempt: number;
    config: ResolvedStepConfig;
    };

    ReadableStream support in step.do()

    Steps can now return a ReadableStream directly. Although non-stream step outputs are limited to 1 MiB, streamed outputs support much larger payloads.

    TypeScript
    const largePayload = await step.do("fetch-large-file", async () => {
    const object = await env.MY_BUCKET.get("large-file.bin");
    return object.body;
    });

    Note that streamed outputs are still considered part of the Workflow instance storage limit.

  1. The Container logs page now displays related Worker and Durable Object logs alongside container logs. This co-locates all relevant log events for a container application in one place, making it easier to trace requests and debug issues.

    Container logs page showing Worker and Durable Object logs alongside container logs

    You can filter to a single source when you need to isolate Container, Worker, or Durable Object output.

    For information on configuring container logging, refer to How do Container logs work?.

  1. Pay-as-you-go customers can now monitor usage-based costs and configure spend alerts through two new features: the Billable Usage dashboard and Budget alerts.

    Billable Usage dashboard

    The Billable Usage dashboard provides daily visibility into usage-based costs across your Cloudflare account. The data comes from the same system that generates your monthly invoice, so the figures match your bill.

    The dashboard displays:

    • A bar chart showing daily usage charges for your billing period
    • A sortable table breaking down usage by product, including total usage, billable usage, and cumulative costs
    • Ability to view previous billing periods

    Usage data aligns to your billing cycle, not the calendar month. The total usage cost shown at the end of a completed billing period matches the usage overage charges on your corresponding invoice.

    To access the dashboard, go to Manage Account > Billing > Billable Usage.

    Screenshot of the Billable Usage dashboard in the Cloudflare dashboard

    Budget alerts

    Budget alerts allow you to set dollar-based thresholds for your account-level usage spend. You receive an email notification when your projected monthly spend reaches your configured threshold, giving you proactive visibility into your bill before month-end.

    To configure a budget alert:

    1. Go to Manage Account > Billing > Billable Usage.
    2. Select Set Budget Alert.
    3. Enter a budget threshold amount greater than $0.
    4. Select Create.

    Alternatively, configure alerts via Notifications > Add > Budget Alert.

    Create Budget Alert modal in the Cloudflare dashboard

    You can create multiple budget alerts at different dollar amounts. The notifications system automatically deduplicates alerts if multiple thresholds trigger at the same time. Budget alerts are calculated daily based on your usage trends and fire once per billing cycle when your projected spend first crosses your threshold.

    Both features are available to Pay-as-you-go accounts with usage-based products (Workers, R2, Images, etc.). Enterprise contract accounts are not supported.

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

  1. When a Cloudflare Worker intercepts a visitor request, it can dispatch additional outbound fetch calls called subrequests. By default, each subrequest generates its own log entry in Logpush, resulting in multiple log lines per visitor request. With subrequest merging enabled, subrequest data is embedded as a nested array field on the parent log record instead.

    What's new

    • New subrequest_merging field on Logpush jobs — Set "merge_subrequests": true when creating or updating an http_requests Logpush job to enable the feature.
    • New Subrequests log field — When subrequest merging is enabled, a Subrequests field (array\<object\>) is added to each parent request log record. Each element in the array contains the standard http_requests fields for that subrequest.

    Limitations

    • Applies to the http_requests (zone-scoped) dataset only.
    • A maximum of 50 subrequests are merged per parent request. Subrequests beyond this limit are passed through unmodified as individual log entries.
    • Subrequests must complete within 5 minutes of the visitor request. Subrequests that exceed this window are passed through unmodified.
    • Subrequests that do not qualify appear as separate log entries — no data is lost.
    • Subrequest merging is being gradually rolled out and is not yet available on all zones. Contact your account team for concerns or to ensure it is enabled for your zone.
    • For more information, refer to Subrequests.
  1. This week's release introduces a new detection for a Remote Code Execution (RCE) vulnerability in Apache ActiveMQ (CVE-2026-34197) and an updated signature for Magento 2 - Unrestricted File Upload. Alongside these detections, we are continuing our work on rule refinements to provide deeper security insights for our customers.

    Key Findings

    • Apache ActiveMQ (CVE-2026-34197): A vulnerability in Apache ActiveMQ allows an unauthenticated, remote attacker to execute arbitrary code. This flaw occurs during the processing of specially crafted network packets, leading to potential full system compromise.

    • Magento 2 - Unrestricted File Upload - 2: This is a follow-up enhancement to our existing protections for Magento and Adobe Commerce.

    Impact

    Successful exploitation of these vulnerabilities could allow unauthenticated attackers to execute arbitrary code or gain full administrative control over affected servers. We strongly recommend applying official vendor patches for Apache ActiveMQ and Magento to address the underlying vulnerabilities.

    Continuous Rule Improvements

    We are continuously refining our managed rules to provide more resilient protection and deeper insights into attack patterns. To ensure an optimal security posture, we recommend consistently monitoring the Security Events dashboard and adjusting rule actions as these enhancements are deployed.

    RulesetRule IDLegacy Rule IDDescriptionPrevious ActionNew ActionComments
    Cloudflare Managed Ruleset N/ACommand Injection - Generic 8 - uriLogBlockThis is a new detection. Previous description was "Command Injection - Generic 8 - uri - Beta"
    Cloudflare Managed Ruleset N/ACommand Injection - Generic 8 - body - BetaDisabledDisabled

    This is a new detection. This rule is merged into the original rule "Command Injection - Generic 8 - body" (ID: ). The rule previously known as "Command Injection - Generic 8" is now renamed to "Command Injection - Generic 8 - body".

    Cloudflare Managed Ruleset N/AMySQL - SQLi - Executable Comment - BetaLogBlock

    This is a new detection. This rule is merged into the original rule "MySQL - SQLi - Executable Comment - Body" (ID: ) The rule previously known as "MySQL - SQLi - Executable Comment" is now renamed to "MySQL - SQLi - Executable Comment - Body".

    Cloudflare Managed Ruleset N/AMySQL - SQLi - Executable Comment - HeadersLogBlock

    This is a new detection.

    Cloudflare Managed Ruleset N/AMySQL - SQLi - Executable Comment - URILogBlock

    This is a new detection.

    Cloudflare Managed Ruleset N/AMagento 2 - Unrestricted file upload - 2LogBlock

    This is a new detection.

    Cloudflare Managed Ruleset N/AApache ActiveMQ - Remote Code Execution - CVE:CVE-2026-34197LogBlock

    This is a new detection.

    Cloudflare Managed Ruleset N/ASQLi - Sleep Function - BetaLogBlock

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

    Cloudflare Managed Ruleset N/ASQLi - Sleep Function - HeadersLogBlock

    This is a new detection.

    Cloudflare Managed Ruleset N/ASQLi - Sleep Function - URILogBlock

    This is a new detection.

    Cloudflare Managed Ruleset N/ASQLi - Probing - uriLogBlock

    This is a new detection.

    Cloudflare Managed Ruleset N/ASQLi - Probing - headerLogBlock

    This is a new detection.

    Cloudflare Managed Ruleset N/ASQLi - Probing - bodyDisabledDisabled

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

    Cloudflare Managed Ruleset N/ASQLi - Probing 2 DisabledDisabled

    This rule had duplicate detection logic and has been deprecated.

    Cloudflare Managed Ruleset N/ASQLi - UNION in MSSQL - BodyDisabledDisabled

    This rule has been renamed to differentiate from "SQLi - UNION in MSSQL" (ID: ) and contains updated rule logic.

    Cloudflare Managed Ruleset N/ASQLi - UNION - 3DisabledDisabled

    This rule had duplicate detection logic and has been deprecated.

    Cloudflare Managed Ruleset N/AXSS, HTML Injection - Embed Tag - URIDisabledDisabled

    This is a new detection.

    Cloudflare Managed Ruleset N/AXSS, HTML Injection - Embed Tag - HeadersLogBlock

    This is a new detection.

    Cloudflare Managed Ruleset N/AXSS, HTML Injection - IFrame Tag - Src and Srcdoc Attributes - HeadersLogDisabled

    This is a new detection.

    Cloudflare Managed Ruleset N/AXSS, HTML Injection - Link Tag - HeadersLogDisabled

    This is a new detection.

    Cloudflare Managed Ruleset N/AXSS, HTML Injection - Link Tag - URIDisabledDisabled

    This is a new detection.

  1. Binary frames received on a WebSocket are now delivered to the message event as Blob objects by default. This matches the WebSocket specification and standard browser behavior. Previously, binary frames were always delivered as ArrayBuffer. The binaryType property on WebSocket controls the delivery type on a per-WebSocket basis.

    This change has been active for Workers with compatibility dates on or after 2026-03-17, via the websocket_standard_binary_type compatibility flag. We should have documented this change when it shipped but didn't. We're sorry for the trouble that caused. If your Worker handles binary WebSocket messages and assumes event.data is an ArrayBuffer, the frames will arrive as Blob instead, and a naive instanceof ArrayBuffer check will silently drop every frame.

    To opt back into ArrayBuffer delivery, assign binaryType before calling accept(). This works regardless of the compatibility flag:

    JavaScript
    const resp = await fetch("https://example.com", {
    headers: { Upgrade: "websocket" },
    });
    const ws = resp.webSocket;
    // Opt back into ArrayBuffer delivery for this WebSocket.
    ws.binaryType = "arraybuffer";
    ws.accept();
    ws.addEventListener("message", (event) => {
    if (typeof event.data === "string") {
    // Text frame.
    } else {
    // event.data is an ArrayBuffer because we set binaryType above.
    }
    });

    If you are not ready to migrate and want to keep ArrayBuffer as the default for all WebSockets in your Worker, add the no_websocket_standard_binary_type flag to your Wrangler configuration file.

    This change has no effect on the Durable Object hibernatable WebSocket webSocketMessage handler, which continues to receive binary data as ArrayBuffer.

    For more information, refer to WebSockets binary messages.

  1. The new Network session analytics dashboard is now available in Cloudflare One. This dashboard provides visibility into your network traffic patterns, helping you understand how traffic flows through your Cloudflare One infrastructure.

    Cloudflare One Network Session Analytics

    What you can do with Network session analytics

    • Analyze geographic distribution: View a world map showing where your network traffic originates, with a list of top locations by session count.
    • Monitor key metrics: Track session count, total bytes transferred, and unique users.
    • Identify connection issues: Analyze connection close reasons to troubleshoot network problems.
    • Review protocol usage: See which network protocols (TCP, UDP, ICMP) are most used.

    Dashboard features

    • Summary metrics: Session count, bytes total, and unique users
    • Traffic by location: World map visualization and location list with top traffic sources
    • Top protocols: Breakdown of TCP, UDP, ICMP, and ICMPv6 traffic
    • Connection close reasons: Insights into why sessions terminated (client closed, origin closed, timeouts, errors)

    How to access

    1. Log in to Cloudflare One.
    2. Go to Zero Trust > Insights > Dashboards.
    3. Select Network session analytics.

    For more information, refer to the Network session analytics documentation.

  1. Logpush has traditionally been great at delivering Cloudflare logs to a variety of destinations in JSON format. While JSON is flexible and easily readable, it can be inefficient to store and query at scale.

    With this release, you can now send your logs directly to Pipelines to ingest, transform, and store your logs in R2 as Parquet files or Apache Iceberg tables managed by R2 Data Catalog. This makes the data footprint more compact and more efficient at querying your logs instantly with R2 SQL or any other query engine that supports Apache Iceberg or Parquet.

    Transform logs before storage

    Pipelines SQL runs on each log record in-flight, so you can reshape your data before it is written. For example, you can drop noisy fields, redact sensitive values, or derive new columns:

    INSERT INTO http_logs_sink
    SELECT
    ClientIP,
    EdgeResponseStatus,
    to_timestamp_micros(EdgeStartTimestamp) AS event_time,
    upper(ClientRequestMethod) AS method,
    sha256(ClientIP) AS hashed_ip
    FROM http_logs_stream
    WHERE EdgeResponseStatus >= 400;

    Pipelines SQL supports string functions, regex, hashing, JSON extraction, timestamp conversion, conditional expressions, and more. For the full list, refer to the Pipelines SQL reference.

    Get started

    To configure Pipelines as a Logpush destination, refer to Enable Cloudflare Pipelines.

  1. R2 SQL is Cloudflare's serverless, distributed, analytics query engine for querying Apache Iceberg tables stored in R2 Data Catalog.

    R2 SQL now supports functions for querying JSON data stored in Apache Iceberg tables, an easier way to parse query plans with EXPLAIN FORMAT JSON, and querying tables without partition keys stored in R2 Data Catalog.

    JSON functions extract and manipulate JSON values directly in SQL without client-side processing:

    SELECT
    json_get_str(doc, 'name') AS name,
    json_get_int(doc, 'user', 'profile', 'level') AS level,
    json_get_bool(doc, 'active') AS is_active
    FROM my_namespace.sales_data
    WHERE json_contains(doc, 'email')

    For a full list of available functions, refer to JSON functions.

    EXPLAIN FORMAT JSON returns query execution plans as structured JSON for programmatic analysis and observability integrations:

    Terminal window
    npx wrangler r2 sql query "${WAREHOUSE}" "EXPLAIN FORMAT JSON SELECT * FROM logpush.requests LIMIT 10;"
    ┌──────────────────────────────────────┐
    plan
    ├──────────────────────────────────────┤
    {
    "name": "CoalescePartitionsExec",
    "output_partitions": 1,
    "rows": 10,
    "size_approx": "310B",
    "children": [
    {
    "name": "DataSourceExec",
    "output_partitions": 4,
    "rows": 28951,
    "size_approx": "900.0KB",
    "table": "logpush.requests",
    "files": 7,
    "bytes": 900019,
    "projection": [
    "__ingest_ts",
    "CPUTimeMs",
    "DispatchNamespace",
    "Entrypoint",
    "Event",
    "EventTimestampMs",
    "EventType",
    "Exceptions",
    "Logs",
    "Outcome",
    "ScriptName",
    "ScriptTags",
    "ScriptVersion",
    "WallTimeMs"
    ],
    "limit": 10
    }
    ]
    }
    └──────────────────────────────────────┘

    For more details, refer to EXPLAIN.

    Unpartitioned Iceberg tables can now be queried directly, which is useful for smaller datasets or data without natural time dimensions. For tables with more than 1000 files, partitioning is still recommended for better performance.

    Refer to Limitations and best practices for the latest guidance on using R2 SQL.

  1. Archive and audit security action items

    Introducing enhanced archiving capabilities for security action items within the Security Overview dashboard. This update allows security teams to maintain a cleaner workspace by removing resolved, accepted, or irrelevant items from their active list while maintaining a clear paper trail for compliance.


    Why this matters

    Managing a high volume of security insights can be overwhelming. Previously, users lacked a structured way to dismiss items without losing the context of why they were ignored.

    With these new archiving options—False Positive, Accept Risk, and Other—you can now suppress items indefinitely with required rationale text for risk-based decisions. This ensures that your team remains focused on critical, actionable vulnerabilities while preserving institutional knowledge for audits.

    Key features

    • Structured Archiving: Choose from specific categories to define why an action item is being moved.
    • Required Rationale: For "Accept Risk" and "Other" categories, users must provide documentation, ensuring accountability for security decisions.
    • Audit Log Transparency: New API endpoints allow you to programmatically retrieve the history of status changes and rationale for any insight at the account or zone level.
    • Reversible Actions: Any archived item can be moved back to the active list at any time if the security context changes.

    Example: Retrieve audit logs via API

    To review the history and rationale of a specific archived issue at the account level, you can use the following API command:

    Terminal window
    curl "[https://api.cloudflare.com/client/v4/accounts/](https://api.cloudflare.com/client/v4/accounts/){account_id}/insights/{insight_id}/audit-log" \
    -H "Authorization: Bearer <API_TOKEN>" \
    -H "Content-Type: application/json"
  1. @cf/moonshotai/kimi-k2.6 is now available on Workers AI, in partnership with Moonshot AI for Day 0 support. Kimi K2.6 is a native multimodal agentic model from Moonshot AI that advances practical capabilities in long-horizon coding, coding-driven design, proactive autonomous execution, and swarm-based task orchestration.

    Built on a Mixture-of-Experts architecture with 1T total parameters and 32B active per token, Kimi K2.6 delivers frontier-scale intelligence with efficient inference. It scores competitively against GPT-5.4 and Claude Opus 4.6 on agentic and coding benchmarks, including BrowseComp (83.2), SWE-Bench Verified (80.2), and Terminal-Bench 2.0 (66.7).

    Key capabilities

    • 262.1k token context window for retaining full conversation history, tool definitions, and codebases across long-running agent sessions
    • Long-horizon coding with significant improvements on complex, end-to-end coding tasks across languages including Rust, Go, and Python
    • Coding-driven design that transforms simple prompts and visual inputs into production-ready interfaces and full-stack workflows
    • Agent swarm orchestration scaling horizontally to 300 sub-agents executing 4,000 coordinated steps for complex autonomous tasks
    • Vision inputs for processing images alongside text
    • Thinking mode with configurable reasoning depth
    • Multi-turn tool calling for building agents that invoke tools across multiple conversation turns

    Differences from Kimi K2.5

    If you are migrating from Kimi K2.5, note the following API changes:

    • K2.6 uses chat_template_kwargs.thinking to control reasoning, replacing chat_template_kwargs.enable_thinking
    • K2.6 returns reasoning content in the reasoning field, replacing reasoning_content

    Get started

    Use Kimi K2.6 through the Workers AI binding (env.AI.run()), the REST API at /ai/run, or the OpenAI-compatible endpoint at /v1/chat/completions. You can also use AI Gateway with any of these endpoints.

    For more information, refer to the Kimi K2.6 model page and pricing.

  1. MCP server portals display a homepage when users visit the portal domain in a browser.

    MCP server portal homepage showing connection status and setup instructions

    The homepage shows:

    • The portal name and organization branding
    • The MCP endpoint URL with a copy button
    • Per-client connection instructions for Claude Desktop, Workers AI Playground, OpenCode, Windsurf, and other MCP clients

    Authenticated users see their email address and a Sign out button. Selecting Sign out revokes all portal-level OAuth grants, deletes upstream server OAuth states, and redirects through Cloudflare Access logout. A confirmation page shows a summary of the revoked sessions.

    For more information, refer to MCP server portals.