AI Search can now summarize your files while it indexes them. For each text document that produces at least three chunks, AI Search uses a large language model (LLM) to generate a summary, topics, and keywords:
The summary and keywords are stored in the item's context metadata. A context value you already set is kept.
The topics are added to the context header of the file's chunks to help retrieval.
Turn on file summaries in the dashboard, or set indexing_options.file_summary to true when you create or update an instance. File summaries are off by default, and changing the setting triggers a full reindex.
indexing_options is replaced as a whole on every update. Include the current value of every option, or the options you leave out return to their defaults.
The LLM costs are billed to your account. File summaries are not part of the AI Search ingestion allotment. AI Search uses a Workers AI model suited to summarization and calls it through your instance's AI Gateway, or the default gateway if none is set, and the calls are billed as Workers AI usage. Each new or modified file is summarized once, so costs grow with the amount of content you index.
Cloudflare CLI (cf) 1.0.0-rc.1 is a release candidate for cf 1.0. cf has been in beta since late September. This is the release we recommend you try on your own projects, and we want your feedback before 1.0.
To install or update to the latest release:
npm install --global cf@latest
yarn global add cf@latest
pnpm add --global cf@latest
bun add --global cf@latest
What is stable
We expect the following features to remain stable to cf 1.0:
The cloudflare.config.ts configuration format.
The Build Output format that cf build writes and cf deploy reads.
The commands that create, develop, build, and deploy projects, including cf init, cf dev, cf build, cf deploy, cf previews deploy, and cf workers versions create.
The large majority of commands generated from the Cloudflare API and used in the beta.
A small number of less commonly used API commands may still change before 1.0. cf generates these commands from the Cloudflare API schema, so their call path may still change before 1.0.
Upgrade from a beta
This release moves Build Output to version 1, in .cloudflare/output/v1/. cf deploy will automatically create a new build on first run in this location.
The release candidate also moves to caret (^) version ranges for its dependencies, requiring:
@cloudflare/vite-plugin 2.0.0-rc.0 or later, for projects that build with Vite.
Wrangler 4.163.0 or later, for legacy projects that build with Wrangler.
1.0.0-rc.1 renames a few generated API commands without aliases. For example, cf workers secrets bulk is now cf workers secrets bulk-edit. For the full list, refer to the release notes ↗︎.
If you last updated early in the beta, these earlier changes may also affect you:
Prompts, progress, and status messages are written to stderr. Stdout holds only command output, so scripts that read messages from stdout must read stderr instead.
Commands generated from camelCase or snake_case API names use kebab-case. For example, cf accounts billing getCredits is now cf accounts billing get-credits.
cf previews deploy takes the Preview name as --preview-name instead of a positional argument.
Commands run with --local store state in the project's .cloudflare/state directory.
cf no longer saves your account choice between runs. Set accountId in cloudflare.config.ts or CLOUDFLARE_ACCOUNT_ID to skip the prompt.
Streaming tail consumers move to experimental.streamingTailConsumers in cloudflare.config.ts.
Destructive commands run without a terminal exit with an error unless you pass --force.
cf supports the latest versions of the Node.js LTS releases and the latest active release of Node.js.
Stream live logs
cf observability tail streams live logs and other observability events as newline-delimited JSON. Select a Worker with --worker, a zone and its subdomains with --zone, or every event in the account with --all. Narrow the results with --filters, as inline JSON or from a file:
Worker events require Workers Logs to be turned on for the Worker. For filter shapes and examples, run cf observability tail --help.
What changed during the beta
Deploy
Deploy a directory of static assets with cf deploy ./dist. cf skips the build step and creates an assets-only Worker.
cf deploy --no-provision fails when a binding has no resource ID, instead of creating a new resource.
cf deploy --force deploys when the Worker was last deployed through the API, or when its remote configuration conflicts with your local Build Output.
Redeploying no longer removes secrets that you added outside cloudflare.config.ts.
Stack traces from deployed Workers show project paths such as src/index.ts.
Python Workers with vendored packages deploy correctly.
cf deploy applies SSH settings for Containers managed by Durable Objects.
cf deploy --dry-run shows the project setup changes it would make, without making them.
Set CLOUDFLARE_DEPENDENCIES_INSTRUMENTATION=false to stop uploading package dependency metadata with each deployment.
Develop
cf init creates new Worker projects with Vite+, including checks, formatting, and tests that run in the Workers runtime.
cf dev and cf build run the Vite or Vite+ executable installed in your project, including dependencies hoisted in a workspace.
cf dev passes arguments such as --port and --host to your framework's development server.
cf dev --profile <name> passes the selected authentication profile to your development server.
cf dev, cf build, and cf deploy offer to run cf migrate when they find a Wrangler configuration file.
On Windows, Ctrl+C exits cleanly when your framework runs through npm, Wrangler and Vite start without spawn EFTYPE errors, and cf d1 migrations create rejects names that Windows cannot store.
cf init approves the build scripts that pnpm 11 and later block by default, so installation succeeds.
Sign in and accounts
Pass --temporary-account to create a short-lived account without signing in. cf prints a URL you can use to claim the account.
cf auth login summarizes the scopes you granted, and cf auth scopes lists them by product.
cf auth whoami, also available as cf whoami, prints a short summary in a terminal and full JSON for scripts and agents.
cf auth login now uses the system keyring where available.
Long-running commands, such as cf observability tail, refresh an expired OAuth login instead of failing.
cf auth whoami reports the status of scoped API tokens correctly.
Every command accepts --dry-run to preview what it would do and it redacts sensitive fields in request previews.
cf checks --body input before it asks you to sign in or confirm, and rejects array bodies larger than the API allows instead of splitting them across several requests.
More request fields are available as flags, including JSON objects and maps, arrays of objects, and file uploads. For example, cf pages deployments create --worker-js @./_worker.js and cf ai to-markdown --files @first.html @second.pdf.
Error outputs have been improved with additional messages the API returns, such as the names of missing parameters.
cf workers commands accept --worker to select a Worker.
--zone finds zones by name in accounts with many zones.
cf tunnels quick-start --allowed-mail limits a temporary tunnel to the email addresses and domains you allow.
Scripts and agents
cf --version prints only the version number.
Shell completions and cf tools list every flag a command accepts.
cf cli search has reranked cf deploy and other key commands to improve their ranking for static site and Pages deployment searches.
You can now give each Cloudflare One Appliance in a high availability (HA) site its own default gateway on a static WAN. Before this change, both appliances in an HA pair shared the same WAN gateway. Now each appliance can connect to its own Internet circuit, such as a different ISP for each appliance, with its own static IP and gateway.
In the dashboard, when you configure a static WAN on an HA site, enter the secondary appliance's gateway in the new Secondary gateway address field, next to Primary gateway address.
In the API, set static_addressing.secondary_gateway_address when you create or update a WAN. To remove the value with a PATCH request, set it to null.
The field is optional. If you leave it blank, the secondary appliance uses the primary gateway address, which matches how HA sites worked before. You can only use this field on sites in HA mode.
Cloudflare Images lets you optimize images for web delivery while storing only the original, high-resolution version. With Images, you can dynamically serve compressed and resized versions in the most efficient format for the requesting browser.
Starting today, Images accepts TIFF as an input format.
In publishing and e-commerce, TIFF is widely deployed as a master format for product photography, high-resolution scans, print assets, and archival collections. TIFF is a mature format, but it has limited support in modern browsers and tends to produce larger files than formats optimized for web delivery.
You can dynamically transcode original TIFF files to formats such as WebP or AVIF. These formats offer more efficient compression, which can reduce file sizes and improve page load performance. You can also resize each output without converting or modifying your original image.
For multi-page TIFF files, Images decodes only the first page. For supported formats and limits, refer to Limits and formats.
You can now develop and test Artifacts locally. Create repos, import Git repositories over HTTPS, issue repo tokens, and clone or push with Git on your machine before deploying to Cloudflare's global network. Local repos are separate from your deployed repos, so you can test changes without affecting production data.
Local repos also emit the same Artifacts events as production when a repo is created, imported, forked, or deleted, or when a repo token is created or revoked. This lets you test the Workflows that react to them before you deploy.
To use local repos when you run your Worker locally, add an Artifacts binding to your Wrangler configuration file:
{ "$schema": "./node_modules/wrangler/config-schema.json", "name": "artifacts-worker", "main": "src/index.ts", // Set this to today's date "compatibility_date": "2026-11-17", "artifacts": [ { "binding": "ARTIFACTS", "namespace": "default" } ]}
name = "artifacts-worker"main = "src/index.ts"# Set this to today's datecompatibility_date = "2026-11-17"[[artifacts]]binding = "ARTIFACTS"namespace = "default"
Run npx wrangler dev, then use the binding the same way you would in production:
const created = await env.ARTIFACTS.create("starter-repo");return Response.json({ remote: created.remote, token: created.token,});
const created = await env.ARTIFACTS.create("starter-repo");return Response.json({ remote: created.remote, token: created.token,});
The returned remote points to your local dev session, so you can use it with a standard Git client to clone and push.
Local development requires the latest version of Wrangler and Git 2.32 or later on your PATH.
When you develop with npx wrangler dev, the Cloudflare Vite plugin, or the Workers Vitest integration, Artifacts bindings use the local simulator by default. To use your deployed repos instead, set remote = true on the binding.
Cloudflare One now includes Periodic Beaconing Traffic as a risk behavior. It analyzes Gateway HTTP traffic for regular check-ins to the same destination.
Cloudflare flags a user after more than 30 contacts to the same destination in six hours. Contacts must be evenly spaced, from 10 seconds to about 12 minutes apart. Few other users in your organization contact that destination.
Detection uses traffic behavior only. It does not use threat intelligence, categories, or reputation. Malware can check in with a command-and-control (C2) server this way, but legitimate software also checks in regularly. Treat each event as a lead to investigate, not proof that a destination is C2.
By default, the behavior is off and its risk level is Info. To turn it on, go to Risk score > Risk behaviors. Cloudflare reports a continuing beacon once. Events usually arrive 3 to 6 hours after the six-hour window closes.
Periodic Beaconing Traffic is available on Enterprise plans.
You can now test Browser Run Quick Actions locally. Under npx wrangler dev, the browser binding's .quickAction() method runs against a Chrome instance on your machine. Before, .quickAction() worked only in remote mode, and local calls failed with The RPC receiver does not implement the method "quickAction".
The cloudflare_ai_search_instance resource has a new namespace argument. It defaults to default, so existing configurations keep managing the same instances.
When you upgrade to v5.29.0, review these changes:
The cloudflare_ai_search_instance import ID now includes the namespace: <account_id>/<namespace>/<id>. For instances in the default namespace, use <account_id>/default/<id>.
The cloudflare_ai_search_instance and cloudflare_ai_search_instances data sources require namespace. Set namespace = "default" for instances in the default namespace.
cloudflare_ai_search_instances returns the instances in one namespace. The filter.namespace argument of cloudflare_ai_search_instance is removed.
You can now set spending limits for Workers and Durable Objects to help control unexpected usage costs, or receive email alerts while your applications keep running. Support for more products is coming soon.
Use these controls alongside AI Gateway spend limits to manage compute and AI inference costs across your application. AI Gateway supports per-user and per-model budgets for Workers AI and other AI providers, applied to requests routed through your gateway.
Workers and Durable Objects limits apply across your account for the current subscription billing period. Each product has its own spending controls.
Set your limits and alerts
In the Cloudflare dashboard ↗︎, select your account and go to Billing > Spend limits. Choose a spending limit, notification email, and alert thresholds for Workers or Durable Objects.
For example, configure a $10 Workers spending limit with email alerts at $5 and $9. To receive alerts while your applications keep running, turn off Block usage.
See when a limit takes effect
The overview shows each product's recorded spend, alert thresholds, and pause status. Email alerts notify you without stopping usage. When a spending limit takes effect, Cloudflare blocks the product's supported operations.
To resume usage, raise the limit above current spend, turn it off, or remove it. Usage also resumes when the next billing period starts.
Usage reporting and blocking take time, so recorded spend can exceed a limit. Read about what counts toward a limit.
Choose alerts, limits, or both
For example, set a $50 spending limit for Workers and a $20 email alert for Durable Objects:
flowchart LR
A["Durable Objects reaches $20"] --> B["Email alert sent"]
B --> C["Usage continues"]
D["Workers reaches $50"] --> E["Spending limit takes effect"]
E --> F["New Worker invocations blocked"]
The amount is in US cents: 5000 means $50. To set a spending limit for Durable Objects, use --product-id durable_objects and update the name. Limits count usage already recorded in the current billing period.
You can also give this prompt to your coding agent. It will ask which product you want to manage and what spending limit to set, then use the CLI to configure it.
Use spending limits alongside budget alerts
The budget alerts introduced earlier this year notify you about account-wide usage costs without stopping usage. You can keep using them alongside the new product-specific spending limits and email alerts for Workers and Durable Objects.
To configure account-wide alerts, go to Billing > Billable Usage or follow the budget alerts guide.
Read the spending limits and alerts guide to learn how spending limits work and manage limits and alerts through the dashboard or cf CLI.
AI Search can now use a D1 database as a data source. AI Search runs a read-only query that you provide and indexes each returned row as a separate document. Scheduled syncs keep the index current as rows are added, changed, or removed.
Create D1-backed instances from the dashboard, the REST API, or the Workers binding.
Kitesurf ↗︎, Cloudflare's browser engine for AI agents, is now open source on GitHub ↗︎ under the Apache 2.0 license. You can inspect the source, run it locally, and deploy your own instance to your Cloudflare account.
Kitesurf runs entirely on Cloudflare Workers. It parses HTML, applies CSS, executes page JavaScript, and renders screenshots without a browser container. It supports the Chrome DevTools Protocol (CDP), so you can connect clients such as Puppeteer.
Kitesurf is still experimental and under heavy development. The team continues to improve web standards support, rendering fidelity, and performance.
Run locally or deploy to your account
Developers can run Kitesurf locally with Wrangler. After following the build requirements and setup instructions ↗︎, run pnpm run dev. This builds the engine and starts wrangler dev.
To run your own instance on Cloudflare, follow the deployment instructions ↗︎. Protect your deployment with Cloudflare Access or another authentication layer. Kitesurf does not provide built-in authentication.
Contribute and follow progress
Contributions and pull requests are welcome. The team remains focused on compatibility, reliability, and performance, with limited review capacity. Keep changes focused and follow the contribution guidelines ↗︎, including opening an issue and getting vouched by a maintainer before submitting a pull request.
You can now export a D1 database that contains virtual tables, such as full-text search tables using SQLite's FTS5 module ↗︎ or spatial index tables using the R*Tree module. Previously, export failed for any database containing virtual tables.
To include virtual tables in the dump, set dump_options.compatibility to sqlite3_cli_only on the D1 export API. The same option is available as the --compatibility flag on wrangler d1 export.
RealtimeKit auth tokens now support custom validity windows, and you can revoke a single token. When your backend adds a participant to a meeting, it gets back an auth token that the participant's app uses to join.
Previously, every token was valid for 100 days from the moment it was issued. Now you can choose when a token starts and stops working, for example only during a scheduled class or interview, so a shared link stops working once the session is over. Pass not_before and expires_on in the token object when you add a participant:
Both fields are optional, so existing integrations keep getting 100-day tokens.
You can also revoke a single token without setting the whole meeting to INACTIVE. If the participant is in the meeting, RealtimeKit removes them. A revoked token can take up to 60 seconds to stop working everywhere, so delete the participant instead if you need to block them immediately.
RealtimeKit rejects expired, not yet valid, and revoked tokens before the participant enters the meeting, so you are not billed for them.
You can now add noise cancellation to RealtimeKit web apps with the new @cloudflare/realtimekit-noise-cancellation package. RealtimeKit is a high-level SDK for adding real-time audio and video components, such as video meetings, to your web or mobile app.
import { RealtimeKitNoiseCancellation } from "@cloudflare/realtimekit-noise-cancellation";// Enables automatically when the mic is available, without delaying join.void RealtimeKitNoiseCancellation.init({ meeting }).catch(console.warn);
How it works
Filters background noise in the participant's browser, before their audio is sent to the meeting.
Turns on automatically after init(), as soon as the participant's microphone is on.
Keeps running through mute, unmute, and reconnects, and cleans up when the participant leaves.
Never unmutes the microphone.
Noise cancellation works in React, Angular, and JavaScript apps on Chrome, Edge, Firefox, and Safari, including mobile browsers. The RealtimeKit iOS and Android SDKs do not yet support it.
Learn more
Noise Cancellation: setup for React, Angular, and JavaScript, plus the full API
Noise cancellation example ↗︎: RealtimeKit's default meeting UI with noise cancellation turned on, also available in Angular and HTML in the same repository
Starting from version 2026.11.0, Cloudflare Tunnel extends the URL normalization introduced in 2026.10.0. Normalization now handles semicolon-delimited path parameters before matching ingress rules. This improves security for tunnels with rules that require Cloudflare Access validation. The URL path sent to your origin stays the same.
Starting 2027-02-08, new cloudflared releases will turn on URL normalization by default. This replaces the previously announced date of 2027-01-25, giving you time to test the updated behavior. Upgrade to version 2026.11.0 or later and test your path-based routing before that date, including rules that match paths containing semicolons. Configurations without rules requiring Access validation are unaffected.
This setting is currently off by default. To turn it on, run:
cloudflared tunnel --disable-path-normalization=false run <TUNNEL_NAME_OR_UUID>
Alternatively, set TUNNEL_DISABLE_PATH_NORMALIZATION=false on each cloudflared replica and restart it.
You can then use AI Security for Apps fields in custom rules managed with the cloudflare_ruleset resource, keeping your detection settings, topics, and mitigation rules in the same configuration.
Payload logging now supports WAF custom rules. Enterprise customers can configure an account-level public key, or a zone-level public key that takes precedence, to encrypt matched payloads for supported managed rules and custom rules.
This release does not add payload logging support for rate limiting rules.
@cf/google/embeddinggemma-2 is now available on Workers AI. EmbeddingGemma 2 is an open multimodal embedding model from Google DeepMind. It maps text (including code), images, video, and audio into a single 768-dimensional vector space, so you can search a mixed collection of products, documents, and media with one text query.
Key capabilities:
Multimodal: Embed text, images, video, audio, or any combination of them in one input. Every embedding shares the same vector space.
Multilingual and code: Understands more than 100 languages and improves code retrieval over the original EmbeddingGemma.
Flexible dimensions: Set dimensions to 128, 256, or 512 to return shorter vectors and reduce storage, with a small cost to quality.
Long context: An 8,192 token context window, shared across all content in an input.
Task prefixes: Add short instructions such as task: search result | query: ... to tune embeddings for search, classification, clustering, or similarity.
Send text with input. Send images, video, and audio as base64 data URIs in messages:
@cf/thinkingmachines/inkling-2-small is now available on Workers AI. Inkling 2 Small is the second generation of Inkling models from Thinking Machines Lab, and the first frontier open model from a US lab on Workers AI.
Inkling 2 Small is more capable than the previous generation. It is a multimodal Mixture-of-Experts model with 594B total parameters and 18B active parameters. Thinking Machines trained it much faster than previous models because of improvements to their pre-training and infrastructure.
Inkling 2 Small works well for:
Agentic coding: Plan, write, and edit code across multi-step tasks.
Vision understanding: Interpret images sent alongside text in the same request.
General agentic knowledge work: Research, analyze, and act on information with tools.
Key capabilities:
Vision: Accepts text and image inputs.
Reasoning: Reasoning is on by default at high effort. Set reasoning_effort to max, medium, low, or minimal to change the effort, or to none to turn reasoning off.
Function calling: Build agents that invoke tools and APIs across multiple conversation turns.
Long context: A full 1,048,576 token context window.
Inkling 2 Small requires the Workers Paid plan or prepaid AI Gateway credits. The default rate limit is 20 requests per minute with standard Workers AI billing and 50 requests per minute with prepaid AI Gateway credits. For details, refer to limits.
GitHub secret scanning automatically detects Cloudflare Access service token secrets exposed in public repositories and reports them to Cloudflare. Access then disables the affected token and emails account administrators.
Other secret scanning tools can identify Access service tokens using their consistent Client Secret format: cfast_, followed by 40 alphanumeric characters and an eight-character hexadecimal checksum. For tools that support custom detection rules, use this regular expression to find possible secrets:
cfast_[A-Za-z0-9]{40}[a-f0-9]{8}
This pattern applies to Client Secrets created on or after August 26, 2026, not legacy 64-character hexadecimal secrets. Matching the pattern does not validate the checksum or confirm that the secret is active. For details, refer to Client Secret format.
Recover a leaked service token
Before you can re-enable a leaked token, you must rotate its secret.
Leaked secrets do not support a rotation grace period. When you rotate one, the previous secret is discarded immediately. Update your services with the new secret, then re-enable the token.
For API rotations, omit previous_client_secret_expires_at. A future expiration returns 400. Attempting to re-enable the token before rotation returns 409.
The Web Assets > Operations page now includes metric-focused views for traffic, errors, latency, response size, and security. Each view surfaces the relevant metrics and supports server-side sorting, making it easier to prioritize operations in large inventories.
Refer to Endpoint Management for more information about managing and analyzing operations.
Cloudflare has reduced the number of round trips needed to connect to a Durable Object when a location lookup follows a forwarding record to another data center.
When an object's destination isn't cached in Cloudflare's network, the first data center contacted may have a forwarding record pointing to another data center.
Previously, the first data center acquired a connection to the object at the destination and proxied it back to the caller. The caller then established its own direct connection to the object.
Now, the first data center returns the destination directly, without first acquiring a connection to the object. The caller then establishes a direct connection, avoiding the intermediate connection and duplicate acquisition.
Skipping this intermediate connection can reduce p99 connection latency for these relocation-related requests. Actual results depend on your workload and traffic patterns.
No code or configuration changes are required to benefit from this improvement.
Customers on a Workers Paid plan can now create up to 100 Hyperdrive configurations, up from 25, and configure up to 1,500 origin database connections per configuration, up from 100.
Configuration limit
The configuration limit is the maximum number of Hyperdrive configurations you can create per account. Workers Paid customers can now create up to 100 configurations, allowing more workloads to take advantage of connection pooling and query caching across different databases.
Origin connection limit
The origin connection limit is the maximum number of database connections that Hyperdrive can make to your origin database per configuration. Workers Paid customers can now configure up to 1,500 origin connections, increasing the connection pool size available for workloads that need more concurrent database access. You can configure this value via the dashboard, Wrangler, or the REST API.
We recommend setting the origin connection limit lower than your origin database's connection limit.
You can now add a collaborative whiteboard to RealtimeKit meetings with the Whiteboard plugin, which Cloudflare hosts and runs for you. RealtimeKit provides SDKs for running live audio and video meetings in your app. Many companies use it today to run online education and interview platforms, where participants often need a shared whiteboard to work through ideas together.
You add the Whiteboard plugin with the same plugins API you use for your own plugins. Load it in an iframe, with the participant's auth token after # in the URL:
const WHITEBOARD_URL = "https://whiteboard-v2.plugins.realtime.cloudflare.com/";function createWhiteboard(authToken: string): HTMLIFrameElement { const iframe = document.createElement("iframe"); iframe.style.width = "100%"; iframe.style.height = "100%"; iframe.style.border = "none"; // Lets participants copy and paste on the board. iframe.allow = "clipboard-read; clipboard-write"; // The plugin does not need your page's address. iframe.referrerPolicy = "no-referrer"; iframe.src = `${WHITEBOARD_URL}#authToken=${encodeURIComponent(authToken)}`; return iframe;}const whiteboardElement = createWhiteboard("<auth_token>");
Then pass whiteboardElement as the plugin's component when you initialize the SDK. The Whiteboard plugin guide has the registration code for web, Android, iOS, and React Native.
You can also build your own plugins and render them alongside the meeting UI. A whiteboard you build yourself needs a server that sends every stroke to every participant, saves the board between sessions, and checks who can open it. With the Whiteboard plugin, Cloudflare runs all of that for you.
How it works
Participants draw shapes, arrows, freehand strokes, and text on one shared board, and see each other's cursors and names.