Cloudflare

AI Gateway gained a unified REST endpoint, Workers VPC extended reach to WAN on-ramps, and the Agents SDK shipped durable chat recovery.

AI Gateway now routes any model through a single API. Requests to OpenAI, Anthropic, Google, or Workers AI-hosted models all go through api.cloudflare.com using one auth token.¹ Logging, caching, rate limiting, and guardrails apply automatically; provider API keys are no longer required for third-party models.

Workers VPC bindings can now reach the full private network. A cf1:network VPC binding gives Workers access to Cloudflare Mesh nodes, Tunnel-routed subnets, and WAN on-ramps — GRE, IPsec, and CNI — through a single fetch() call.²

The Agents SDK added resilience for long-running AI sessions. @cloudflare/ai-chat keeps server turns running when a browser disconnects or refreshes; @cloudflare/think gains durable programmatic submissions with idempotent retries and cancellation; @cloudflare/voice adds a lazy-connect enabled flag for capability-gated voice agents.³

Granular permissions landed for Tunnel and Mesh. Administrators can now scope read or write access to individual Tunnel instances and Mesh nodes without granting account-wide private-networking control.⁴

Cloudflare Access replaced OTP as the default identity provider. New Zero Trust accounts use Cloudflare account credentials by default; existing accounts can add Cloudflare as an IdP and lock authentication to account members only.⁵

R2 SQL gained cross-table query support. JOINs (INNER, LEFT, RIGHT, FULL OUTER, CROSS), subqueries, CTEs, and self-joins now work across Iceberg tables stored in R2.⁶

Wrangler 4.94.0 auto-detects AI coding agents and offers to install Cloudflare skill files; local dev tunnels print a QR code alongside the tunnel URL for quick mobile access.⁷