Cloudflare AI Updates & Release Notes

Follow

209 updates curated from 1 source by the Releasebot Team. Last updated: Nov 18, 2026

Get this feed:
  • Nov 17, 2026
    • Date parsed from source:
      Nov 17, 2026
    • First seen by Releasebot:
      Nov 18, 2026
    • Modified by Releasebot:
      Nov 18, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    AI Search can generate file summaries during indexing

    Cloudflare AI Search now summarizes text files during indexing, adding summaries, topics, and keywords to help improve retrieval. File summaries are optional, off by default, and billed as Workers AI usage.

    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
  • Nov 13, 2026
    • Date parsed from source:
      Nov 13, 2026
    • First seen by Releasebot:
      Nov 13, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    Browser Run Quick Actions now work in local development

    Cloudflare AI now supports local testing of Browser Run Quick Actions with Wrangler dev and Chrome. The JSON action returns placeholder data, and Kitesurf is not yet supported in the local simulation.

    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
  • All of your release notes in one feed

    Join Releasebot and get updates from Cloudflare and hundreds of other software products.

    Create account
  • Nov 13, 2026
    • Date parsed from source:
      Nov 13, 2026
    • First seen by Releasebot:
      Nov 13, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    Manage AI Search instances in any namespace with Terraform

    Cloudflare AI Search now supports managing instances across namespaces with Terraform provider v5.29.0, including namespace-aware imports and data sources. Existing configurations default to the default namespace, while changing an instance’s namespace replaces it.

    Starting with Cloudflare Terraform provider ↗︎ v5.29.0, you can manage AI Search instances in any namespace, not only default.

    The cloudflare_ai_search_instance resource has a new namespace argument. It defaults to default, 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>/support
    

    The 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_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.
    • Changing namespace replaces the instance.
    Original source
  • Nov 12, 2026
    • Date parsed from source:
      Nov 12, 2026
    • First seen by Releasebot:
      Nov 13, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    Inkling 2 Small now available on Workers AI

    Cloudflare AI now offers Thinking Machines Lab’s Inkling 2 Small on Workers AI, bringing a multimodal model with vision, reasoning, tool calling and a 1-million-token context window for coding and agentic knowledge work.

    @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
  • Nov 12, 2026
    • Date parsed from source:
      Nov 12, 2026
    • First seen by Releasebot:
      Nov 12, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    AI Search supports D1 databases as a data source (beta)

    Cloudflare AI Search now supports D1 databases as data sources, indexing query results as documents and keeping them current with scheduled syncs. Create D1-backed instances from 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
  • Similar to Cloudflare AI with recent updates:

  • Nov 12, 2026
    • Date parsed from source:
      Nov 12, 2026
    • First seen by Releasebot:
      Nov 12, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    Kitesurf is now open source

    Cloudflare AI releases Kitesurf, an open-source browser engine for AI agents that runs on Cloudflare Workers. Developers can inspect the code, run it locally or deploy their own instance, with CDP support for tools like Puppeteer.

    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.

    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 12, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    EmbeddingGemma 2 now available on Workers AI

    Cloudflare AI now offers Google DeepMind’s EmbeddingGemma 2 on Workers AI, enabling shared-space search across text, code, images, video, and audio, with multilingual support and flexible embedding dimensions.

    @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",
          },
        ],
      ],
    });
    

    Pricing is $0.0017 per million input tokens.

    For more information, refer to the EmbeddingGemma 2 model page and pricing.

    Original source
  • Nov 9, 2026
    • Date parsed from source:
      Nov 9, 2026
    • First seen by Releasebot:
      Nov 11, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    Run the Codex agent loop on Cloudflare Workers

    Cloudflare AI adds an experimental Agents SDK example for running the Codex agent loop in a Durable Object, with conversations, files, and completed model and tool results preserved across restarts for recovery.

    Run the Codex agent loop in a Cloudflare Durable Object with this experimental Agents SDK example ↗︎. Conversations, files, and completed model and tool results persist across restarts, allowing the agent to recover after interruptions.

    The example adapts Codex’s Rust turn-processing code ↗︎ to WebAssembly and uses Agents SDK capabilities for storage and recovery.

    The harness combines Agents SDK capabilities for durable execution:

    • Tasks journals model calls and tool execution. Completed steps reuse their recorded results after a restart. Interrupted steps can run again.
    • Sessions stores conversation history and compacts the model context.
    • Streams stores ordered events for replay after reconnecting.
    • Workspace provides tools to read and write persistent files.

    For example, use OpenAI's GPT-6.1 Sol through AI Gateway. Configure the model with createAI and install the capabilities on a Durable Object:

    import { DurableObject } from "cloudflare:workers";
    import { Workspace } from "@cloudflare/computer";
    import { Lifecycle } from "agents/lifecycle";
    import { createAI } from "agents/models/ai-sdk";
    import { Sessions } from "agents/sessions";
    import { Streams } from "agents/streams";
    import { Tasks } from "agents/tasks";
    import { CodexHarness } from "./codex-harness";
    
    export class Coder extends DurableObject {
      tasks = new Tasks();
      streams = new Streams();
      sessions = new Sessions();
      workspace = new Workspace({ storage: this.ctx.storage });
    
      codex = new CodexHarness({
        tasks: this.tasks,
        streams: this.streams,
        sessions: this.sessions,
        workspace: this.workspace,
        model: createAI({ binding: this.env.AI, id: "default" })(
          "openai/gpt-6.1-sol",
        ),
      });
    
      lifecycle = Lifecycle.install(this)
        .use(this.tasks)
        .use(this.streams)
        .use(this.sessions)
        .use(this.codex);
    }
    

    To use this model, configure the default gateway with Unified Billing or a stored OpenAI API key.

    For setup, models, tools, and recovery behavior, refer to the Codex harness guide.

    Original source
  • Nov 9, 2026
    • Date parsed from source:
      Nov 9, 2026
    • First seen by Releasebot:
      Nov 11, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    Run Exo agents on Cloudflare

    Cloudflare AI now supports running Exo agents with Durable Objects coordinating conversations and Cloudflare Sandboxes providing Linux tools. Developers can define agents in Markdown and run them through Exo’s CLI or HTTP API using the Cloudflare adapter.

    You can now run Exo agents on Cloudflare, with Durable Objects coordinating conversations and Cloudflare Sandboxes running Linux tools. Define an agent in Markdown, then use Exo's CLI or HTTP API to run it.

    After deploying the Cloudflare adapter and configuring your Exo provider ↗︎, add an openai vault credential and save this definition as agent.md:

    ---
    harness: basic
    model:
      name: gpt-6.1-sol
    credential: openai
    ---
    
    Help the user with their task.
    

    Run the agent against your Cloudflare deployment with Exo's CLI:

    exo --provider cloudflare agent run --agent-file agent.md
    

    The Exo project maintains the Cloudflare adapter independently of Cloudflare. It does not require the Agents SDK.

    Follow the Exo guide for architecture, recovery behavior, and upstream setup instructions.

    Original source
  • Nov 9, 2026
    • Date parsed from source:
      Nov 9, 2026
    • First seen by Releasebot:
      Nov 11, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    Run the Nanocode agent harness in Cloudflare Durable Objects

    Cloudflare AI now supports running Nanocode coding agents in Durable Objects, with persistent session history and recovery after interruptions.

    You can now run Nanocode ↗︎ coding agents in Cloudflare Durable Objects, with persistent session history and recovery after interruptions.

    Nanocode's Rust engine runs as WebAssembly and implements Codex and Claude Code prompt and tool conventions. Its Cloudflare host saves turn progress and tool results in SQLite and uses alarms to resume pending work. The Nanocode project maintains the host independently of Cloudflare; it does not require the Agents SDK.

    Start with the reference Worker ↗︎ and follow Nanocode on Workers for setup, models, and recovery limits.

    Original source
  • Nov 6, 2026
    • Date parsed from source:
      Nov 6, 2026
    • First seen by Releasebot:
      Nov 7, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    Review provider key activity in AI Gateway

    Cloudflare AI Gateway adds provider-key usage tracking to help users review, rotate, and remove credentials, with alerts for keys inactive over 90 days.

    AI Gateway now shows usage activity for your stored provider keys. Use this information to review credentials for rotation or removal.

    In Provider Keys, keys are grouped by provider with masked previews, aliases, and last-used and last-updated dates. The Key security section highlights keys with recorded activity older than 90 days. You can review these keys and delete them after checking their dependencies.

    Usage tracking starts November 2026.

    For details on storing, rotating, and removing provider keys, refer to Bring your own keys.

    Original source
  • Nov 5, 2026
    • Date parsed from source:
      Nov 5, 2026
    • First seen by Releasebot:
      Nov 6, 2026
    • Modified by Releasebot:
      Nov 11, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    Planned model deprecations on Workers AI

    Cloudflare AI is updating the Workers AI model catalog and has moved the deprecation date for select models to November 20, 2026. Affected models will stop responding, with newer alternatives recommended for language, image, audio, and embedding workloads.

    We are refreshing the Workers AI model catalog to make room for new releases and updated models. Update your apps to remove references to the models listed below before November 20, 2026. We originally stated these models would be deprecated on November 15, 2026, and have moved the deprecation date to November 20, 2026.

    Starting November 20, 2026, these models will stop returning responses. Requests to them will fail with an HTTP 410 Gone error and error code 5028.

    We recommend moving to newer models for the best token efficiency and throughput. For pricing, refer to the Workers AI pricing page.

    Recommended LLM replacements

    • For frontier model needs: @cf/deepseek-ai/deepseek-v4.1-flash-1017 and @cf/zai-org/glm-5.3.
    • For smaller model needs: @cf/google/gemma-4-26b-a4b-it and @cf/qwen/qwen3.8-27b.

    Models deprecated on November 20, 2026

    LLMs

    • @cf/deepseek-ai/deepseek-r1-distill-qwen-32b
    • @cf/nvidia/nemotron-3-120b-a12b
    • @cf/deepseek-ai/deepseek-v4-pro-0813
    • @cf/deepseek-ai/deepseek-v4-flash-0731
    • @cf/qwen/qwq-32b
    • @cf/qwen/qwen3-30b-a3b-fp8
    • @cf/moonshotai/kimi-k2.6
    • @cf/moonshotai/kimi-k2.7-code
    • @cf/zai-org/glm-5.2
    • @cf/zai-org/glm-5.3-flash
    • @cf/meta-llama/llama-2-7b-chat-hf-lora
    • @cf/google/gemma-2b-it-lora
    • @cf/google/gemma-7b-it-lora
    • @cf/meta/llama-3.1-8b-instruct-fp8
    • @cf/meta/llama-3.2-1b-instruct
    • @cf/meta/llama-3.2-3b-instruct

    Other models

    Each deprecated model is followed by its suggested replacement.

    • @cf/myshell-ai/melotts → @cf/deepgram/aura-2-en
    • @cf/stabilityai/stable-diffusion-xl-base-1.0 → @cf/black-forest-labs/flux-2-klein-9b
    • @cf/runwayml/stable-diffusion-v1-5-inpainting → @cf/black-forest-labs/flux-2-klein-9b
    • @cf/bytedance/stable-diffusion-xl-lightning → @cf/black-forest-labs/flux-2-klein-9b
    • @cf/lykon/dreamshaper-8-lcm → @cf/black-forest-labs/flux-2-klein-9b
    • @cf/openai/whisper-tiny-en → @cf/deepgram/nova-3
    • @cf/llava-hf/llava-1.5-7b-hf → @cf/moondream/moondream3.1-9B-A2B
    • @cf/google/embeddinggemma-300m → @cf/google/embeddinggemma-2 (available soon)

    For the full list of available models, refer to the Workers AI model catalog.

    Original source
  • Nov 4, 2026
    • Date parsed from source:
      Nov 4, 2026
    • First seen by Releasebot:
      Nov 5, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    Route across a pool of models with model aliases

    Cloudflare AI Gateway now supports model aliases, letting applications call a configurable pool of models under one name. It can try models in order with fallback or use smart routing, while gateway-side changes avoid redeployment.

    AI Gateway now supports model aliases. A model alias is a pool of models that your application calls by one name, such as custom/support-fast. AI Gateway tries the models in the order you set and falls back to the next one if a request fails, or uses smart routing to choose a model for each request.

    Because your application only references the alias, you can swap models or change the routing algorithm on your gateway without redeploying. Create and manage aliases on your gateway's Routing page, alongside dynamic routes.

    To call an alias through the REST API, use its name as the model. For example, send this body to /accounts/{account_id}/ai/run:

    {
      "model": "custom/support-fast",
      "input": {
        "messages": [{"role": "user", "content": "Reply with a short greeting."}]
      }
    }
    

    Include the cf-aig-gateway-id header to select the gateway where you created the alias. Aliases are scoped to individual gateways.

    For setup instructions and routing options, refer to Model aliases.

    Original source
  • Nov 3, 2026
    • Date parsed from source:
      Nov 3, 2026
    • First seen by Releasebot:
      Nov 4, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    Agents SDK now supports Pi 1.5 with fewer storage writes and lower memory use

    Cloudflare AI releases Agents SDK v0.33.0 with Pi 1.5, cutting streaming storage writes and memory use while boosting multi-session throughput. It also adds session.watch() and session.continue(), plus turn limits and improved task and browser handling.

    Performance improvements

    • Far fewer storage writes while streaming. Pi stores streamed answers and tool output in batches, within a second of each update, instead of on every update. Over SQLite, this cuts storage transactions by about 27x for long answers and 5.7x for turns with parallel tools, and CPU by about a quarter.
    • Higher throughput across many sessions. Pi's scheduler no longer rechecks every conversation on each commit. In a SQLite benchmark with 2,048 sessions, one Pi harness went from 88 to 459 agent runs per second.
    • Less memory on large answers. Streaming a 500 KB tool call used to take about 20 seconds of CPU and a 100 MB heap. Pi now appends new text instead of copying it on every update.

    Streaming updates remain visible immediately, but are persisted in batches. With the default settings, a crash can lose up to about one second of streamed progress. Refer to Recovery to configure this interval.

    Session and tool updates

    • A view of each session. session.watch() replaces session.events(). It returns the newest transcript entries and the session's live state, such as the answer being streamed, running tools, and why the last run ended without an answer.
    • Continue without adding a message. The new session.continue() API starts a new run using the existing transcript, for example after a model error or when a run reaches its turn limit.
    • Turn limit. defaults.maxTurns caps the tool rounds a run can take in new sessions.
    • Tasks that keep crashing end. Pi now ends a task cut off by its restart limit instead of parking it. retry() and the parked status are removed.
    • Browser in Pi's code mode. Scripts in Pi's code mode can call browserTool and pass its screenshots to image(). browserTool also stops when the harness aborts its call.

    Continue an unanswered conversation

    For an existing session and submission operationId, check the result before offering a continuation. For example, after resolving a model error:

    const result = await session.wait(operationId);
    
    if (result.status === "unanswered" && result.reason === "model_error") {
      const receipt = await session.continue({ operationId: `${operationId}:continue`, });
      const continued = await session.wait(receipt.operationId);
      console.log(continued.status, continued.text);
    }
    

    This starts a new run without appending a user message. The session must be idle. If the transcript already ends in an answer, the operation returns unanswered with reason nothing_to_answer. Refer to Work with sessions.

    Upgrade

    Once a conversation runs on Pi 1.5, Pi 1.4 cannot read it. After upgrading, roll forward to fix deployment issues rather than rolling back to Pi 1.4.

    Update callers of session.events() to use session.watch(), and remove uses of retry() and the parked status. Refer to the Pi Durable 1.5.0 changelog ↗︎ for the full list of breaking changes.

    The Agents SDK v0.33.0 changelog ↗︎ has step-by-step upgrade instructions. Point your coding agent at them and upgrade today:

    Original source
  • Nov 3, 2026
    • Date parsed from source:
      Nov 3, 2026
    • First seen by Releasebot:
      Nov 4, 2026
    Cloudflare logo

    Cloudflare AI by Cloudflare

    New AI Gateways require authentication

    Cloudflare AI adds mandatory, non-removable authentication for new AI Gateways, enabled by default through the API. Existing gateways can keep authentication off or enable it, while requests must use a valid Cloudflare API token; Workers bindings remain pre-authenticated.

    AI Gateway authentication

    New AI Gateways now require authentication to prevent unauthorized requests. Once authentication is on, you cannot turn it off through the dashboard or API.

    When you create a new AI Gateway through the API, authentication is on by default. You can leave out the authentication field or set it to true. If you set it to false, the API returns HTTP 400.

    When you update an existing gateway, leaving out authentication keeps its current setting. If you try to turn off authentication after it is on, the API returns HTTP 400.

    Existing gateways with authentication turned off can continue without it. You can turn it on in your gateway settings or include authentication: true in a gateway update request:

    {
      "authentication": true
    }
    

    Before turning authentication on, configure HTTP clients to send a valid Cloudflare API token. Requests through Workers bindings remain pre-authenticated.

    For setup instructions and supported authorization headers, refer to AI Gateway authentication.

    Original source
Releasebot

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.