CLOUDFLARE

Cloudflare Gateway now classifies MCP traffic by protocol headers instead of hostname heuristics, ships a shadow-MCP dashboard, and lets admins block any MCP connection that does not arrive through an approved portal. The 2026-07-28 stateless spec is what made it possible.

Cloudflare mitigated 935 network-layer attacks above 1 Tbps in H1 2026, a +519% quarter-over-quarter jump, while DNS floods grew from 25.7% to 40.0% of network-layer attacks. Here is what the numbers say about how attacks are changing and what it means for anyone running public infrastructure.

Cloudflare's Web Integrity team published the framework behind its agent traffic posture: continuous behavioral trust instead of point-in-time bot scoring, Precursor telemetry from 206 million evaluation events a day across 73,438 zones, and a verified-bot taxonomy where agents earn access by declaring themselves honestly.

Cloudflare's Agents Week finale frames agents as a new kind of web visitor with four primitives: readable, discoverable, callable, payable. Here is what that architecture means for developers building and monetizing agent-facing services.

Cloudflare shipped Radar Researcher, a natural-language agent that answers questions about global internet traffic with real interactive charts. The architecture - MCP code mode, chart specs that never let the model touch raw numbers, and a three-model fallback chain - is the interesting part for developers.

Cloudflare is merging Workers AI and AI Gateway into one control plane: unified /ai/ REST API, auto-created default gateways, AI Gateway credits spendable on Workers AI, and model-first routing that picks the provider for you. Here is what changes and what stays.

Cloudflare AI Gateway now attaches a verified user identity to every request and learns a behavioral baseline per account, flagging 2x-p95 session spikes against an org-wide p99 ceiling. Here is how the anomaly math works and why per-account baselines beat global thresholds.

Cloudflare shipped Kitesurf, an agent-first browser that runs entirely on Workers: Rust and WebAssembly rendering, per-page isolates, CDP compatibility, and 3-7x less memory and CPU than Chromium for common agent tasks. Free in beta in Browser Run.

On August 5 Cloudflare published the Agent Access Model: a reference architecture where credentials are short-lived and task-scoped, enforcement lives in the harness and network instead of the prompt, and a Trust Ratchet only narrows an agent's capabilities. The cleanest spec yet for least privilege at agent speed.

On August 5 Cloudflare open sourced Cloudflare OS, the agent workspace it has run internally since May: capability-based Gatekeepers instead of ambient MCP access, apps as private per-user instances, and approvals that simulate outcomes so agents never stall. A concrete blueprint for the company-wide agent platform.

On August 4 Cloudflare launched the Agent Development Lifecycle: agent traces with session replay, @cloudflare/ci for CI/CD as Workflows, and local OpenTelemetry. A software factory is no longer just an idea, it is a platform product.

Cloudflare launched a single endpoint that returns account usage and cost per product in a FOCUS-aligned shape. For teams whose agents provision infrastructure, the dashboard is no longer the only way to see what a month costs.

Cloudflare's new CI SDK runs pipelines as Workflows: TypeScript instead of YAML, cached sandbox steps, artifact-push triggers, and a healing agent that fixes failed builds. Here is how it works and what it means for platforms.

Day three of Agents Week brought Cloudflare Wallets: Account Wallets for humans and Virtual Wallets for agents, x402 stablecoin micropayments for APIs and content, and human-readable agent identity at handles like research.example.cloudflare.pay.

Cloudflare's Agents Week opens with @cloudflare/computer, an open-source agent runtime where an SQLite-backed workspace gives every agent a shared filesystem and lets the model pick between fast isolates and full Linux containers per task. The bet: containers for under 10% of agent work.

Cloudflare published the serving playbook behind Workers AI running Moonshot Kimi K2.6 and Zhipu GLM 5.2: FP8 KV caches double Kimi's resident context to 1.37M tokens, INT4 weights shrink GLM 5.2's checkpoint 40%, and a page-tagging integrity check protects the shared cache at under 1% overhead. The numbers show what actually matters when open frontier models run on GPU fleets.

Cloudflare announced inbound TCP connections and gRPC support for Workers and Containers as part of Agents Week: a connect() handler on Spectrum, full-duplex gRPC from Containers, and automatic gRPC to gRPC-web translation so Workers can serve gRPC APIs without a container. Private beta today.

Cloudflare's JavaScript-native RPC on Workers now works across languages: TypeScript Workers can call methods on Python Workers and vice versa, with live objects, functions, and streams crossing the boundary. Pyodide's FFI handles type conversion, so no schemas, no protobuf, and no serialization code are needed. Available now.

Cloudflare moved cdnjs, the open-source CDN behind ~12% of the web, entirely onto Workers, Workflows, R2, and Queues. The migration raised two platform limits for everyone. Here is what changed and why it matters.

Cloudflare Research introduces Meerkat, a distributed consensus service using QuePaxa that eliminates leader elections and timeouts across their 330+ global data centers.