// AI Platform Drift
Cloudflare Agents SDK adds persistent browser with session state
Cloudflare developer changelog · published 2026-10-13 14:16 UTC
WHAT CHANGEDCloudflare Agents SDK v0.28.0 introduces browserTool, which provides a Browser Run browser that persists tabs, cookies, and login sessions across agent turns. The browser uses Chrome DevTools Protocol, has a 10-minute idle timeout, and requires new bindings (BROWSER, LOADER) plus Lifecycle and registry setup in Durable Objects. Sessions restart fresh if they expire or crash, with restarted: true reported to the tool.
WHY IT MATTERSAgents can now maintain browser state across multiple interactions without re-authenticating or losing navigation context. This enables multi-step workflows like logging into a service on turn one and performing actions on turn three, but session loss after the 10-minute timeout will break workflows that depend on preserved state.
WHAT TO DOIf you build agents that interact with authenticated web services or multi-page workflows, upgrade to Agents SDK v0.28.0 or later, add the BROWSER and LOADER bindings to your wrangler.toml, and implement the Browser and Lifecycle setup shown in the changelog. Test your agent's behavior when restarted: true occurs to handle session expiration gracefully.
Model-reported confidence 85% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Agents - New persistent browser tool in the Agents SDK, with tabs and logins that last between turns +https://developers.cloudflare.com/changelog/post/2026-10-13-persistent-browser/ +Tue, 13 Oct 2026 00:00:00 GMT + +The Cloudflare Agents SDK now provides a browserTool that gives your agent a Browser Run browser it can return to on later turns. Your agent can open a website, inspect a page, and come back to it with its tabs, cookies, and login session intact while the browser session remains alive. +When you give browserTool to your agent, the model writes code that drives the browser through the Chrome DevTools Protocol (CDP). Screenshots return as images that an image-capable model can inspect and your UI can display. +To use browserTool, make sure you have Agents SDK v0.28.0 ↗︎ or greater installed. Create a Browser, register it with your object's Lifecycle, and add the tool to a Pi Durable extension registry before opening the harness: +import { Browser, browserRun } from "agents/browser"; +import { browserTool } from "agents/browser/pi"; + +export class MyAgent extends DurableObject { +// ... + +browser = new Browser({ provider: browserRun(this.env.BROWSER) }); + +harness = new PiHarness({ +harness: async ({ storage, context }) => { +this.registry.install({ +name: "browser", +tools: [ +browserTool({ +ctx: this.ctx, +browser: this.browser, +loader: this.env.LOADER, +}), +], +}); + +// ... + +return Harness.open( +storage, +{ models, registry: this.registry }, +context, +); +}, +}); + +lifecycle = Lifecycle.install(this).use(this.browser).use(this.harness); +}import { Browser, browserRun } from "agents/browser"; +import { browserTool } from "agents/browser/pi"; + +export class MyAgent extends DurableObject<Env> { +// ... + +browser = new Browser({ provider: browserRun(this.env.BROWSER) }); + +harness = new PiHarness({ +harness: async ({ storage, context }) => { +this.registry.install({ +name: "browser", +tools: [ +browserTool({ +ctx: this.ctx, +browser: this.browser, +loader: this.env.LOADER, +}), +], +}); + +// ... + +return Harness.open( +storage, +{ models, registry: this.registry }, +context, +); +}, +}); + +lifecycle = Lifecycle.install(this).use(this.browser).use(this.harness); +} +Each Pi conversation gets its own active tab by default. Cookies and logins remain shared within the browser. +The browser stays alive between turns, including when the Durable Object hibernates. Its default idle timeout is 10 minutes. If the session expires or crashes, the tool creates a fresh browser and reports restarted: true. The old tabs and login state are gone. +You can also use the persistent browser with the AI SDK and TanStack AI adapters, or connect another harness through the public Browser and CDP APIs. +Refer to persistent browser tools for the complete Pi Durable example, required bindings, and behavior when a tool call is interrupted.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.5 |
|---|---|
| triage reasoning | New persistent browser capability requires SDK upgrade, new code patterns, and deployment configuration. |
| signals | new feature addition: persistent browser tool in Agents SDK · new SDK capability: tabs and login state persist across turns · minimum version requirement: Agents SDK v0.28.0 or greater · new API surface: browserTool, Browser, browserRun imports · new integration pattern: Lifecycle, PiHarness, registry setup · behavioral specification: 10-minute idle timeout, session restart behavior · deployment requirement: new bindings and configuration needed |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |