Developer Platform Updates & Release Notes
469 updates curated from 1 source by the Releasebot Team. Last updated: Nov 18, 2026
- Nov 18, 2026
- Date parsed from source:Nov 18, 2026
- First seen by Releasebot:Nov 18, 2026
Developer Platform by Cloudflare
Hyperdrive, Workers VPC - Custom CA and client certificates (mTLS) for Workers VPC
Developer Platform now supports custom certificate authorities and mutual TLS for VPC Services, enabling verified connections to private services and origins that require client certificates. Configure certificates with Wrangler, the API, or Terraform for HTTPS and TCP services, including PostgreSQL databases.
VPC Services can now verify private services that use certificates from your own certificate authority (CA), and authenticate to services that require mutual TLS (mTLS). Previously, Workers VPC only trusted publicly trusted CAs and Cloudflare Origin CA, so connecting to a private CA meant weakening verification with verify_ca or disabled, and origins that required client certificates were unreachable. Upload your CA certificate and client certificate, then reference them from the TLS settings of a VPC Service: npx wrangler cert upload certificate-authority --ca-cert ./ca.pem --name private-ca npx wrangler cert upload mtls-certificate --cert ./client.pem --key ./client-key.pem --name private-client npx wrangler vpc service create private-db \ --type tcp \ --tcp-port 5432 \ --app-protocol postgresql \ --hostname db.internal.example \ --tunnel-id <TUNNEL_ID> \ --certificate-authority <CA_CERTIFICATE_ID> \ --client-certificate <CLIENT_CERTIFICATE_ID> \ --cert-verification-mode verify_full You can use a custom CA, a client certificate, or both. The settings apply to HTTPS connections from http services and to TLS connections from tcp services, including PostgreSQL databases used with Hyperdrive, such as Amazon RDS instances that use the RDS CA bundle. You can configure custom CA and client certificates with Wrangler 4.164.0 or later, the API, or Terraform provider 5.29.0 or later. For details, refer to Custom CA and client certificates.
Original source - Nov 17, 2026
- Date parsed from source:Nov 17, 2026
- First seen by Releasebot:Nov 18, 2026
Developer Platform by Cloudflare
AI Search - AI Search can generate file summaries during indexing
Developer Platform adds optional AI Search file summaries during indexing, generating summaries, topics, and keywords to enrich context metadata and improve retrieval. The feature is off by default and incurs Workers AI usage charges.
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. For more information, refer to File summaries.
Original source All of your release notes in one feed
Join Releasebot and get updates from Cloudflare and hundreds of other software products.
- Nov 17, 2026
- Date parsed from source:Nov 17, 2026
- First seen by Releasebot:Nov 18, 2026
Developer Platform by Cloudflare
Workers, Cloudflare CLI - Cloudflare CLI (cf) 1.0 release candidate
Developer Platform releases a candidate for Cloudflare CLI 1.0, bringing live observability logs, improved deployment and development workflows, and clearer scripting support. The update also establishes stable configuration and build output formats while detailing migration changes for beta users.
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: npmyarnpnpmbun 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: cf observability tail --worker my-worker cf observability tail --worker my-worker --filters @filters.json 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. Set CLOUDFLARE_API_HEADERS to send custom headers with API requests. API commands 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. cf docs search finds Cloudflare documentation from the terminal. Send feedback To report a bug or tell us what is missing, open an issue in the cf repository ↗︎. For every change in each release, refer to the Cloudflare CLI release notes ↗︎.
Original source - Nov 17, 2026
- Date parsed from source:Nov 17, 2026
- First seen by Releasebot:Nov 18, 2026
Developer Platform by Cloudflare
Cloudflare Images - Optimize original TIFF files with Images
Developer Platform’s Cloudflare Images now accepts TIFF originals, converting them on demand to web-friendly formats such as WebP and AVIF. Users can also resize outputs while preserving originals, helping deliver image assets more efficiently.
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.
Original source - Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
- Modified by Releasebot:Nov 17, 2026
Developer Platform by Cloudflare
Artifacts, Workers - Artifacts now supports local development
Developer Platform now supports local development and testing for Artifacts, including creating and importing repositories, using Git, and testing repository events and workflows before deployment. Local repos stay separate from production, with Wrangler and supported development tools using the simulator by default.
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 date compatibility_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, setremote = trueon the binding.To learn more, refer to Local development.
Original source Similar to Developer Platform with recent updates:
- Cloudflare AI updates209 release notes · Latest Nov 17, 2026
- Claude Code updates492 release notes · Latest Nov 18, 2026
- Gemini updates473 release notes · Latest Nov 17, 2026
- Claude updates194 release notes · Latest Nov 17, 2026
- Claude Developer Platform updates189 release notes · Latest Nov 17, 2026
- ChatGPT updates252 release notes · Latest Nov 16, 2026
- Nov 13, 2026
- Date parsed from source:Nov 13, 2026
- First seen by Releasebot:Nov 14, 2026
Developer Platform by Cloudflare
Browser Run - Browser Run Quick Actions now work in local development
Developer Platform now supports testing Browser Run Quick Actions locally with Wrangler and a local Chrome instance. The JSON action returns schema-matched placeholder data, and Kitesurf browser support is not yet available.
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".Note
There are currently two limitations in the local simulation:
- The json action is emulated. It requires an AI model to extract data, and the model is not available locally, so the action returns placeholder data that matches your schema.
- The Kitesurf browser is not supported yet.
For details, refer to Test Quick Actions locally.
Original source - Nov 13, 2026
- Date parsed from source:Nov 13, 2026
- First seen by Releasebot:Nov 14, 2026
Developer Platform by Cloudflare
AI Search - Manage AI Search instances in any namespace with Terraform
Developer Platform’s Cloudflare Terraform provider now supports managing AI Search instances in any namespace, with namespace-aware imports and data sources. The update preserves the default namespace behavior while requiring explicit namespace settings for data sources.
Starting with Cloudflare Terraform provider ↗︎ v5.29.0, you can manage AI Search instances in any namespace, not only default.
The
cloudflare_ai_search_instanceresource has a newnamespaceargument. It defaults todefault, so existing configurations keep managing the same instances.resource "cloudflare_ai_search_namespace" "support" { account_id = var.account_id name = "support" } resource "cloudflare_ai_search_instance" "docs" { account_id = var.account_id id = "docs" namespace = cloudflare_ai_search_namespace.support.name }You can import existing instances and namespaces:
terraform import cloudflare_ai_search_instance.docs <account_id>/support/docs terraform import cloudflare_ai_search_namespace.support <account_id>/supportThe data sources read instances from the namespace you set:
data "cloudflare_ai_search_instance" "docs" { account_id = var.account_id namespace = "support" id = "docs" } data "cloudflare_ai_search_instances" "support" { account_id = var.account_id namespace = "support" }When you upgrade to v5.29.0, review these changes:
- The
cloudflare_ai_search_instanceimport ID now includes the namespace:<account_id>/<namespace>/<id>. For instances in the default namespace, use<account_id>/default/<id>. - The
cloudflare_ai_search_instanceandcloudflare_ai_search_instancesdata sources requirenamespace. Setnamespace = "default"for instances in the default namespace. cloudflare_ai_search_instancesreturns the instances in one namespace. Thefilter.namespaceargument ofcloudflare_ai_search_instanceis removed.- Changing namespace replaces the instance.
- Nov 13, 2026
- Date parsed from source:Nov 13, 2026
- First seen by Releasebot:Nov 14, 2026
Developer Platform by Cloudflare
Billing, Workers, Durable Objects - Set spending limits for Workers and Durable Objects
Developer Platform adds spending limits and email alerts for Workers and Durable Objects, helping customers control compute costs without necessarily interrupting usage. Controls are available in the Cloudflare dashboard and cf CLI, alongside AI Gateway budgets and account-wide budget alerts.
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"]Set a spending limit with the cf CLI
Install the cf CLI and select your account, then run this command to set a $50 spending limit for Workers usage in the current billing period:
cf billing spend-policies create \ --name 'Workers $50 spending limit' \ --product-id workers \ --enabled true \ --threshold-cents 5000 \ --action usage_blockThe 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.
Copy prompt
Prompt copied!
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.
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
Developer Platform by Cloudflare
AI Search, D1 - AI Search supports D1 databases as a data source (beta)
Developer Platform now lets AI Search use D1 databases as data sources, indexing query results as documents and keeping them current with scheduled syncs. Create D1-backed instances through the dashboard, REST API, or Workers binding.
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.
curl -X POST "https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/ai-search/namespaces/default/instances" \ -H "Authorization: Bearer <API_TOKEN>" \ -H "Content-Type: application/json" \ --data '{ "id": "help-center", "type": "d1", "source": "<D1_DATABASE_ID>", "token_id": "<SERVICE_TOKEN_ID>", "source_params": { "d1": { "query": "SELECT article_id AS id, title, content, category AS meta_category\nFROM articles\nWHERE published = 1" } } }'Learn more in D1 data source.
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
Developer Platform by Cloudflare
Browser Run - Kitesurf is now open source
Developer Platform releases Kitesurf, Cloudflare’s experimental browser engine for AI agents, as open source under Apache 2.0. It runs on Workers, supports the Chrome DevTools Protocol, and can be run locally or deployed to a Cloudflare account.
Cloudflare's browser engine for AI agents, Kitesurf ↗︎, 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 startswrangler 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.
Important
Kitesurf requires Cloudflare Dynamic Workers to create isolated Workers for pages. Dynamic Workers are part of the Workers Paid plan. A Workers Paid plan is required to run Kitesurf on Cloudflare. Local development uses
wrangler dev.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.
Visit kitesurf.dev ↗︎, the main Kitesurf website and playground. Track Web Platform Tests (WPT) progress ↗︎ and performance benchmarks ↗︎ as development continues.
For background and technical details, refer to the introductory blog post ↗︎ and the Kitesurf update ↗︎. To use Kitesurf through Browser Run, refer to the Kitesurf documentation.
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
Developer Platform by Cloudflare
D1 - Export D1 databases with virtual tables
Developer Platform now supports exporting D1 databases with virtual tables, including FTS5 full-text search and R*Tree spatial indexes. The SQLite CLI-only dump option is available through the export API and Wrangler, but the resulting dump cannot be imported back into D1.
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.
Import is not supported
This dump targets the SQLite CLI only. You cannot import it back into D1. Use the standard export for databases without virtual tables.
curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/d1/database/$DATABASE_ID/export" \ --request POST \ --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \ --json '{ "output_format": "polling", "dump_options": { "compatibility": "sqlite3_cli_only" } }'For more information, refer to Export a D1 database with virtual tables.
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
Developer Platform by Cloudflare
Realtime - Set custom validity windows for RealtimeKit auth tokens
Developer Platform’s RealtimeKit now lets you set custom start and expiration times for meeting participant tokens and revoke individual tokens, improving control over meeting access while preserving existing 100-day defaults.
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_beforeandexpires_onin the token object when you add a participant:Required API token permissions
At least one of the following token permissions is required:
- Realtime Admin
- Realtime
Add a participant
curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/realtime/kit/$APP_ID/meetings/$MEETING_ID/participants" \ --request POST \ --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \ --json '{ "name": "Mary Sue", "preset_name": "<preset_name>", "custom_participant_id": "<uuid_of_the_user_in_your_system>", "token": { "not_before": "2026-12-01T15:00:00Z", "expires_on": "2026-12-01T17:00:00Z" } }'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.
Learn more
- Token validity and refresh
- Revoke tokens
- Add participant API
- Refresh participant token API
- Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
Developer Platform by Cloudflare
Realtime - Add noise cancellation to web apps built on RealtimeKit
Developer Platform adds browser-based noise cancellation to RealtimeKit web apps through a new package, filtering background noise before it reaches meetings. It activates when the microphone is on and supports React, Angular, and JavaScript apps on Chrome, Edge, Firefox, and Safari, including mobile browsers.
You can now add noise cancellation to RealtimeKit web apps with the new
@cloudflare/realtimekit-noise-cancellationpackage. RealtimeKit is a high-level SDK for adding real-time audio and video components, such as video meetings, to your web or mobile app.Install the package:
npm i @cloudflare/realtimekit-noise-cancellation yarn add @cloudflare/realtimekit-noise-cancellation pnpm add @cloudflare/realtimekit-noise-cancellation bun add @cloudflare/realtimekit-noise-cancellationAfter you initialize the meeting, pass it to
init():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
- RealtimeKit release notes
- RealtimeKit quickstart
- Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
Developer Platform by Cloudflare
Workers AI - EmbeddingGemma 2 now available on Workers AI
Developer Platform adds Google DeepMind’s EmbeddingGemma 2 to Workers AI, enabling multilingual search across text, code, images, video, and audio in one shared vector space, with flexible embedding sizes and an 8,192-token context window.
@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:
const response = await env.AI.run("@cf/google/embeddinggemma-2", { messages: [ [ { role: "user", content: [ { type: "text", text: "Waterproof running shoes." }, { type: "image_url", image_url: { url: imageDataUri } }, ], }, ], [ { role: "user", content: "task: search result | query: waterproof shoes for trail running", }, ], ], }); const response = await env.AI.run("@cf/google/embeddinggemma-2", { messages: [ [ { role: "user", content: [ { type: "text", text: "Waterproof running shoes." }, { type: "image_url", image_url: { url: imageDataUri } }, ], }, ], [ { role: "user", content: "task: search result | query: waterproof shoes for trail running", }, ], ], });Pricing is $0.0017 per million input tokens.
For more information, refer to the EmbeddingGemma 2 model page and pricing.
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
Developer Platform by Cloudflare
Workers AI - Inkling 2 Small now available on Workers AI
Developer Platform adds Inkling 2 Small to Workers AI, bringing a frontier open multimodal model with image understanding, tool use, agentic coding, reasoning, and a million-token context window.
@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.
Use Inkling 2 Small through the Workers AI binding (env.AI.run()), the REST API, the OpenAI-compatible endpoint, or AI Gateway.
For more information, refer to the Inkling 2 Small model page and pricing.
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.