What shipped in Cloudflare Workers
5 releases, newest first.
Durable Objects defer code updates by default
On October 30, 2026, Cloudflare Durable Objects began deferring code updates by default. An active Durable Object can keep running its current code for up to 5 minutes (300 seconds) while it waits to hibernate, so in-flight work can finish. WebSocket connections that use the Hibernation API remain connected when an object adopts new code after hibernating. code_update_strategy in the Wrangler durable_objects config can set mode to deferred or immediate and max_delay in seconds, from 0 to 86400. Omitting max_delay uses 300 seconds. A single deployment can pass --durable-objects-code-update-mode immediate or deferred to wrangler versions deploy. A deferred update is best effort and does not guarantee that every operation finishes. The object can still reset before max_delay, for example during a Cloudflare runtime update.
Source for Durable Objects defer code updates by default (opens in a new tab)Browser Run uses Chrome 152
On October 30, 2026, Cloudflare Browser Run started running Chrome 152 by default, with no code change required. The default User-Agent for Quick Actions now reports Chrome 152 instead of Chrome 119. A custom userAgent parameter still overrides it. Quick Actions requests look more like a regular Chrome browser. Pages that return large response headers now load correctly. Browser Run removed distrusted root certificates from its trust store. The /links endpoint returns absolute URLs, and links-only crawls follow relative links. /markdown and crawl Markdown output keep code block languages. Quick Actions that time out return a consistent error, and outbound Workers that throw an exception return an HTTP error to the browser.
Source for Browser Run uses Chrome 152 (opens in a new tab)Agents SDK skills are workspace files
On October 29, 2026, Agent Skills in the Cloudflare Agents SDK became files. A folder with a SKILL.md under /workspace/.agents/skills/ in an agent's Computer Workspace is available on the next turn, with no build or deploy, and the agent can write its own skills. Skills can also load from an R2 bucket or from code, and Think lists every source again before each turn. Every SKILL.md is checked against the Agent Skills specification. A skill that breaks a rule still loads, with a logged warning. Skill scripts are Workspace files, and the model runs them with the Workspace exec tool. The same activate_skill and read_skill_resource tools work in Think, Pi Durable, and the AI SDK. When a skill changes mid-conversation, Think sends the new catalog as a reminder instead of rebuilding the cached system prompt. This is a breaking change for code that uses agents/skills directly. The agents:skills Vite import, agents/skills/compile, SkillRegistry, and Think's skillWorkspace are removed, and runner() moved to agents/skills/runner. Install Agents SDK v0.32.0 and Think v0.23.0 or later.
Source for Agents SDK skills are workspace files (opens in a new tab)Agents SDK browser previews without public URLs
On October 28, 2026, Cloudflare Agents SDK 0.31.0 or later let an agent's persistent browser open internal hostnames such as preview.internal. Requests to those hostnames go to the agent instead of the public Internet, so the model can check a dev server in its sandbox, a folder in its workspace, or another Worker without exposing that server publicly. Each host's fetch function runs in the Durable Object and can use its bindings, or the host can send requests to another Worker through a service binding. A target schema lets the model choose what the host serves, such as a port, through browser.assignHost(). The checked target lasts across turns, browser restarts, and redeploys. Built-in browser-tool adapters cover Pi Durable, the AI SDK, and TanStack AI. Another harness can implement a tool with browser.session(). browserTool now runs the model's code in its own Dynamic Worker and no longer needs a CodemodeRuntime export.
Source for Agents SDK browser previews without public URLs (opens in a new tab)Cloudflare Computer can resume and wait for approval
On October 26, 2026, @cloudflare/computer 0.7.0 can resume agent code after a deploy or crash and pause for an external action such as approving a tool call. Set onInterrupt to "replay" on WorkerJavaScriptBackend so interrupted JavaScript runs again from the beginning and reuses recorded results for completed calls. A call whose result was not recorded before the interruption may run again. A custom module function can call ctx.interrupt() to pause until the app supplies a decision. Time spent waiting does not count toward the timeout, and the wait survives deploys. Pending calls are listed with workspace.runtime.pending() and resolved with respond().
Source for Cloudflare Computer can resume and wait for approval (opens in a new tab)
Updated