Containers, tracing, and streaming move into the Workers dev loop

Unified Routing goes GA

The headline of the week is Unified Routing reaching general availability for Cloudflare WAN and Magic Transit. This reworks how Cloudflare One connects to the standard connectivity onramps, and it brings Automatic Return Routing, BGP, and custom client subnets into a single model. Cloudflare is recommending it for all new accounts, which is a signal the old path is on its way out — if you're standing up new WAN or Magic Transit connectivity now, start here rather than retrofitting later.

In the same vein, Cloudflare announced that cloudflared builds for 32-bit Windows and Intel macOS will be deprecated in 2027, with a matching notice on the Core Platform side. Windows 10's end of support and Apple's removal of Intel Mac support in macOS 27 make this a cleanup rather than a surprise, but anyone running cloudflared on those architectures has a migration window to plan.

Containers get first-class treatment in local dev

The Workers toolchain spent the week making experimental Durable Object-managed Containers feel like a real build target. Wrangler 4.134.0 and the Vite plugin 1.55.0 both added explicit named Container image selection, exposing local tags through ctx.container.images so you can pass a reference straight into ctx.container.start({ image }). Wrangler 4.132.0 and workers-utils 0.39.0 layered on per-image build_context and build_vars, plus application-wide Container observability, and deploy-helpers 0.12.0 rounded out preview bindings and flags.

The larger trajectory showed up at the end of the week: with experimental Build Output enabled, Wrangler, its shared container module, and the Vite plugin now build Dockerfile-backed images and emit container configs under .cloudflare/output/v0/containers. In parallel, Flagship bindings evaluate locally by default, keeping development offline and isolated from production flags unless you opt into remote: true.

Observability that follows the request

Tracing now crosses JavaScript RPC boundaries between Workers and Durable Objects — previously a trace stopped at the caller's RPC edge. Caller-side session spans, method calls, nested calls, and callbacks now all appear, with no SDK changes required beyond enabling tracing. On the runtime side, workerd enabled the Rust I/O backend by default and added an inbound UDP handler, alongside stream and pipe fixes.

Workflows got two quality-of-life wins: individual and batch instance deletion for reclaiming stored state, and event subscriptions via .subscribe() and the API, which streams workflow and step events to Workers and HTTP clients instead of forcing status polling. Model inference also gained an escape hatch with Workers AI's rejectIfBusy option, letting synchronous requests fail fast rather than queue when capacity is tight.

Agent plumbing and deploy speed on Vercel

Vercel's week leaned toward agent infrastructure and build ergonomics. mcp-handler added experimental WebMCP support, exposing MCP tools to in-browser agents with a single script tag and no separate OAuth flow, while the skills CLI can now install agent skills from a Notion database without a Git repo. On the throughput side, the Vercel CLI deploys static artifacts in under one second, and Turbo build machines became a per-deployment opt-in.

The AI SDK shipped a dense set of changes worth naming as a group: browser-direct WebRTC for Live sessions landed in both the React and core packages, the xai provider dropped Chat Completions entirely in favor of the Responses API, Gemini 3.8 Live gained thinking configuration, and evaluation work continued through the TypeSafe provider and Alibaba's reasoning preservation.

Elsewhere across the collection, dozens of smaller releases filled in the edges — Browser Run's new Inspect panel for session recordings, Hyperdrive for Python Workers, R2 Data Catalog maintenance visibility, self-serve Free account creation, v0 reading npm credentials from project env vars, Spend Management on Flexible Commitment plans, Vercel Sandbox as a Harbor eval environment, placement config for Previews, and Local Explorer KV bulk routes — plus a batch of auth and local-mode alignment fixes from Miniflare and Workers auth.