Cloudflare

Cloudflare developer platform and API changelog updates

Cloudflare API Changelog Monitoring

Cloudflare changes can impact edge behavior, DNS workflows, security automation, and API-driven infrastructure management. This Cloudflare API Changelog Monitoring page gives teams one place to review new platform updates and assess operational risk quickly.

Effective Cloudflare API Changelog Monitoring gives infrastructure teams earlier visibility into changes that might influence deployment flows, zone automation, or security controls. The result is a tighter response loop when something needs testing, rollout planning, or internal communication.

The benefit of Cloudflare API Changelog Monitoring is simple: your team gets a repeatable way to watch changes, evaluate risk, and act before small upstream updates turn into customer-facing bugs. Cloudflare developer platform and API changelog updates

Cloudflare API down?

Cloudflare API down? Soon we will add direct API status monitoring alongside Cloudflare API Changelog Monitoring. For now, go to the official API status page on the Cloudflare website. In the future, we plan to detect potential outages even before the public status page is updated.

Recent changes

Showing the last 10 changes from this feed.

04-16-2026

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

New AI Search instances created after today will work differently. New instances come with built-in storage and a vector index, so you can upload a file, have it indexed immediately, and search it right away. Additionally new Workers Bindings are now available to use with AI Search. The new namespace binding lets you create and manage instances at runtime, and cross-instance search API lets you query across multiple instances in one call. Built-in storage and vector index All new instances now comes with built-in storage which allows you to upload files directly to it using the Items API or the dashboard. No R2 buckets to set up, no external data sources to connect first. const instance = env.AI_SEARCH.get("my-instance"); // upload and wait for indexing to completeconst item = await instance.items.uploadAndPoll("faq.md", content); // search immediately after indexingconst results = await instance.search({ messages: [{ role: "user", content: "onboarding guide" }],}); Namespace binding The new ai_search_namespaces binding replaces the previous env.AI.autorag() API provided through the AI binding. It gives your Worker access to all instances within a namespace and lets you create, update, and delete instances at runtime without redeploying. // wrangler.jsonc{ "ai_search_namespaces": [ { "binding": "AI_SEARCH", "namespace": "default", }, ],} // create an instance at runtimeconst instance = await env.AI_SEARCH.create({ id: "my-instance",}); For migration details, refer to Workers binding migration. For more on namespaces, refer to Namespaces. Cross-instance search Within the new AI Search binding, you now have access to a Search and Chat API on the namespace level. Pass an array of instance IDs and get one ranked list of results back. const results = await env.AI_SEARCH.search({ messages: [{ role: "user", content: "What is Cloudflare?" }], ai_search_options: { instance_ids: ["product-docs", "customer-abc123"], },}); Refer to Namespace-level search for details.

Source

04-16-2026

AI Search - AI Search now has hybrid search and relevance boosting

AI Search now supports hybrid search and relevance boosting, giving you more control over how results are found and ranked. Hybrid search Hybrid search combines vector (semantic) search with BM25 keyword search in a single query. Vector search finds chunks with similar meaning, even when the exact words differ. Keyword search matches chunks that contain your query terms exactly. When you enable hybrid search, both run in parallel and the results are fused into a single ranked list. You can configure the tokenizer (porter for natural language, trigram for code), keyword match mode (and for precision, or for recall), and fusion method (rrf or max) per instance: const instance = await env.AI_SEARCH.create({ id: "my-instance", index_method: { vector: true, keyword: true }, fusion_method: "rrf", indexing_options: { keyword_tokenizer: "porter" }, retrieval_options: { keyword_match_mode: "and" },}); Refer to Search modes for an overview and Hybrid search for configuration details. Relevance boosting Relevance boosting lets you nudge search rankings based on document metadata. For example, you can prioritize recent documents by boosting on timestamp, or surface high-priority content by boosting on a custom metadata field like priority. Configure up to 3 boost fields per instance or override them per request: const results = await env.AI_SEARCH.get("my-instance").search({ messages: [{ role: "user", content: "deployment guide" }], ai_search_options: { retrieval: { boost_by: [ { field: "timestamp", direction: "desc" }, { field: "priority", direction: "desc" }, ], }, },}); Refer to Relevance boosting for configuration details.

Source

04-16-2026

Artifacts - Artifacts now in beta: versioned filesystem with Git access

Artifacts is now in private beta. Artifacts is Git-compatible storage built for scale: create tens of millions of repos, fork from any remote, and hand off a URL to any Git client. It provides a versioned filesystem for storing and exchanging file trees across Workers, the REST API, and any Git client, running locally or within an agent. You can read the announcement blog to learn more about what Artifacts does, how it works, and how to create repositories for your agents to use. Artifacts has three API surfaces: Workers bindings (for creating and managing repositories) REST API (for creating and managing repos from any other compute platform) Git protocol (for interacting with repos) As an example: you can use the Workers binding to create a repo and read back its remote URL: # Create a thousand, a million or ten million repos: one for every agent, for every upstream branch, or every user.const created = await env.PROD_ARTIFACTS.create("agent-007");const remote = (await created.repo.info())?.remote; Or, use the REST API to create a repo inside a namespace from your agent(s) running on any platform: curl --request POST "https://artifacts.cloudflare.net/v1/api/namespaces/some-namespace/repos" --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" --header "Content-Type: application/json" --data '{"name":"agent-007"}' Any Git client that speaks smart HTTP can use the returned remote URL: # Agents know git.# Every repository can act as a git repo, allowing agents to interact with Artifacts the way they know best: using the git CLI.git clone https://x:${REPO_TOKEN}@artifacts.cloudflare.net/some-namespace/agent-007.git To learn more, refer to Get started, Workers binding, and Git protocol.

Source

04-15-2026

Workflows, Workers - Increased concurrency, creation rate, and queued instance limits for Workflows instances

Workflows limits have been raised to the following: LimitPreviousNewConcurrent instances (running in parallel)10,00050,000Instance creation rate (per account)100/second per account300/second per account, 100/second per workflowQueued instances per Workflow 11 million2 million These increases apply to all users on the Workers Paid plan. Refer to the Workflows limits documentation for more details. Footnotes Queued instances are instances that have been created or awoken and are waiting for a concurrency slot. ↩

Source

04-15-2026

Browser Run - Browser Rendering is now Browser Run

We are renaming Browser Rendering to Browser Run. The name Browser Rendering never fully captured what the product does. Browser Run lets you run full browser sessions on Cloudflare's global network, drive them with code or AI, record and replay sessions, crawl pages for content, debug in real time, and let humans intervene when your agent needs help. Along with the rename, we have increased limits for Workers Paid plans and redesigned the Browser Run dashboard. We have 4x-ed concurrency limits for Workers Paid plan users: Concurrent browsers per account: 30 → 120 per account New browser instances: 30 per minute → 1 per second REST API rate limits: recently increased from 3 to 10 requests per second Rate limits across the limits page are now expressed in per-second terms, matching how they are enforced. No action is needed to benefit from the higher limits. The redesigned dashboard now shows every request in a single Runs tab, not just browser sessions but also quick actions like screenshots, PDFs, markdown, and crawls. Filter by endpoint, view target URLs, status, and duration, and expand any row for more detail. We are also shipping several new features: Live View, Human in the Loop, and Session Recordings - See what your agent is doing in real time, let humans step in when automation hits a wall, and replay any session after it ends. WebMCP - Websites can expose structured tools for AI agents to discover and call directly, replacing slow screenshot-analyze-click loops. For the full story, read our Agents Week blog Browser Run: Give your agents a browser.

Source

04-15-2026

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

When browser automation fails or behaves unexpectedly, it can be hard to understand what happened. We are shipping three new features in Browser Run (formerly Browser Rendering) to help: Live View for real-time visibility Human in the Loop for human intervention Session Recordings for replaying sessions after they end Live View Live View lets you see what your agent is doing in real time. The page, DOM, console, and network requests are all visible for any active browser session. Access Live View from the Cloudflare dashboard, via the hosted UI at live.browser.run, or using native Chrome DevTools. Human in the Loop When your agent hits a snag like a login page or unexpected edge case, it can hand off to a human instead of failing. With Human in the Loop, a human steps into the live browser session through Live View, resolves the issue, and hands control back to the script. Today, you can step in by opening the Live View URL for any active session. Next, we are adding a handoff flow where the agent can signal that it needs help, notify a human to step in, then hand control back to the agent once the issue is resolved. Session Recordings Session Recordings records DOM state so you can replay any session after it ends. Enable recordings by passing recording: true when launching a browser. After the session closes, view the recording in the Cloudflare dashboard under Browser Run > Runs, or retrieve via API using the session ID. Next, we are adding the ability to inspect DOM state and console output at any point during the recording. To get started, refer to the documentation for Live View, Human in the Loop, and Session Recording.

Source

04-15-2026

Browser Run - Browser Run adds WebMCP support

Browser Run (formerly Browser Rendering) now supports WebMCP (Web Model Context Protocol), a new browser API from the Google Chrome team. The Internet was built for humans, so navigating as an AI agent today is unreliable. WebMCP lets websites expose structured tools for AI agents to discover and call directly. Instead of slow screenshot-analyze-click loops, agents can call website functions like searchFlights() or bookTicket() with typed parameters, making browser automation faster, more reliable, and less fragile. With WebMCP, you can: Discover website tools - Use navigator.modelContextTesting.listTools() to see available actions on any WebMCP-enabled site Execute tools directly - Call navigator.modelContextTesting.executeTool() with typed parameters Handle human-in-the-loop interactions - Some tools pause for user confirmation before completing sensitive actions WebMCP requires Chrome beta features. We have an experimental pool with browser instances running Chrome beta so you can test emerging browser features before they reach stable Chrome. To start a WebMCP session, add lab=true to your /devtools/browser request: curl -X POST "https://api.cloudflare.com/client/v4/accounts/{account_id}/browser-rendering/devtools/browser?lab=true&keep_alive=300000" \ -H "Authorization: Bearer {api_token}" Combined with the recently launched CDP endpoint, AI agents can also use WebMCP. Connect an MCP client to Browser Run via CDP, and your agent can discover and call website tools directly. Here's the same hotel booking demo, this time driven by an AI agent through OpenCode: For a step-by-step guide, refer to the WebMCP documentation.

Source

04-15-2026

Containers - Control where your Containers run with regional and jurisdictional placement

You can now specify placement constraints to control where your Containers run. ConstraintValuesUse caseregionsENAM, WNAM, EEUR, WEURGeographic placementjurisdictioneu, fedrampCompliance boundaries Use regions to limit placement to specific geographic areas. Use jurisdiction to restrict containers to compliance boundaries — eu maps to European regions (EEUR, WEUR) and fedramp maps to North American regions (ENAM, WNAM). Refer to Containers architecture for more details on placement.

Source

04-15-2026

Agents - Agent Lee adds Write Operations and Generative UI

Agent Lee adds Write Operations and Generative UI We are excited to announce two major capability upgrades for Agent Lee, the AI co-pilot built directly into the Cloudflare dashboard. Agent Lee is designed to understand your specific account configuration, and with this release, it moves from a passive advisor to an active assistant that can help you manage your infrastructure and visualize your data through natural language. Take action with Write Operations Agent Lee can now perform changes on your behalf across your Cloudflare account. Whether you need to update DNS records, modify SSL/TLS settings, or configure Workers routes, you can simply ask. To ensure security and accuracy, every write operation requires explicit user approval. Before any change is committed, Agent Lee will present a summary of the proposed action in plain language. No action is taken until you select Confirm, and this approval requirement is enforced at the infrastructure level to prevent unauthorized changes. Example requests: "Add an A record for blog.example.com pointing to 192.0.2.10." "Enable Always Use HTTPS on my zone." "Set the SSL mode for example.com to Full (strict)." Visualize data with Generative UI Understanding your traffic and security trends is now as easy as asking a question. Agent Lee now features Generative UI, allowing it to render inline charts and structured data visualizations directly within the chat interface using your actual account telemetry. Example requests: "Show me a chart of my traffic over the last 7 days." "What does my error rate look like for the past 24 hours?" "Graph my cache hit rate for example.com this week." Availability These features are currently available in Beta for all users on the Free plan. To get started, log in to the Cloudflare dashboard and select Ask AI in the upper right corner. To learn more about how to interact with your account using AI, refer to the Agent Lee documentation.

Source

04-15-2026

Digital Experience Monitoring - Last seen timestamp for Cloudflare One Client devices is more consistent

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

Source