What happened
Cloudflare’s agents@0.29.0 release adds compatibility with Pi 1.3. The release notes say the Pi web search, web fetch, browser, and skills tools now return output, and change the Pi peer-dependency range to ~1.3.0. For builders using the Pi harness through the Agents SDK, this is the compatibility update that keeps those tool integrations aligned with the newer Pi version.
The release also changes several parts of the SDK’s model layer. createAI now accepts { accountId, apiToken } instead of a binding, allowing use of a gateway in another account or execution outside a Worker. It adds transcription through @cf/deepgram/nova-3. Cloudflare also says createAI no longer uses AI Gateway’s deprecated Universal Endpoint: model IDs, including catalog IDs such as anthropic/claude-opus-4.8, run on env.AI.run, while model objects use the provider-native path. The release adds byokAlias, fixes Pi AI catalog models and dynamic routes, and allows catalog IDs in agents/models/opencode.
For long-running responses, createAI can now resume a catalog or dynamic-route stream that drops mid-answer without losing or repeating output. The SDK’s Pi model integration also resolves Claude IDs from Pi AI 1.2’s gateway catalog using AI Gateway’s naming, including anthropic/claude-opus-4.8.
Other changes concern the runtime around an agent. Browser runs now create and close sessions through typed binding methods, acquire() and closeSession(), with an HTTP fallback in fully local development. Chat recovery now seals a turn after chatRecovery.maxInterruptedAttempts interrupted attempts, defaulting to five, so a turn that repeatedly exceeds Durable Object memory does not retry forever; maxOomRetries is deprecated. openPiSessionStore now uses Pi Durable’s Durable Object SQLite adapter, allowing several Pi stores in one object to share its operation queue.
Finally, Agent Skills can read and write a @cloudflare/computer Workspace for projection and skills.runner(). PiHarness.submit() and steer() now accept Pi Durable’s entry option, which lets an application label an input with its own transcript kind, such as app.approval, instead of treating it as pi.user input.
What the archive adds
This is a new fact on a known story. The earlier Field Note, New web_search tool in the Agents SDK, powered by the Cloudflare Web Search API, recorded the initial Agents SDK integration as distinct from Cloudflare’s AI Gateway web-search API. Version 0.29.0 does not announce a new search product; it updates the Pi-side tools, including web search, for Pi 1.3.
Trend signal
This supports Harness architecture outlives model choice. The release’s practical changes sit around the model call rather than in a newly announced model: catalog-ID routing, dropped-stream recovery, session storage, transcript labeling, browser lifecycle management, and tool compatibility. Those are harness responsibilities that remain relevant as model and provider choices change.
Why it matters
For a team already using the Cloudflare Agents SDK with Pi, the immediate implication is upgrade validation rather than a new capability evaluation. Pi 1.3 compatibility covers more than a version declaration: the release specifically names the web search, web fetch, browser, and skills tools, and changes their returned shape to output. Tool consumers should therefore test any assumptions about returned values after upgrading.
The surrounding changes matter to production deployments as well. Model routing has moved away from a deprecated endpoint, stream recovery is intended to avoid missing or duplicate answer content after a dropped route, and recovery behavior now has a defined stop condition for repeated memory-limit interruptions. Together, these notes show that operational behavior in the harness can change alongside a minor SDK version, even when an application’s prompt and model selection do not.
What happens next
- Teams using Pi tools will validate
outputhandling and Pi 1.3 peer compatibility in upgrades. (3 months, 75%). Watch for: follow-up fixes or migration guidance in Agents SDK release notes. - Cloudflare will continue moving model calls away from the deprecated Universal Endpoint toward the documented routing paths. (6 months, 70%). Watch for: removal notices or further
createAIrouting changes.
Limits and uncertainty
The release notes establish that these changes shipped, but do not provide benchmarks, migration examples, pricing changes, or a compatibility matrix for every Pi application. They do not quantify the effect of resumed streams, shared SQLite operation queues, or the new browser-session methods under production load. The notes also do not specify whether existing applications need source changes beyond complying with the Pi 1.3 peer range and handling the documented tool output behavior. Builders should treat the release as implementation-level evidence, not proof of reliability gains in their own workloads.
Skill to build now
Create a small upgrade test for each Pi tool your agent invokes. Run web search, web fetch, browser, and skills calls against the target dependency set; record the returned value shape; and verify downstream parsing, transcript handling, and error paths. If the application uses createAI, include a dropped-stream scenario and confirm that the client receives neither repeated nor missing content. This is a bounded regression suite that turns a release-note claim into evidence for the application’s own harness.
Reader takeaway
Agents SDK 0.29.0 is chiefly a compatibility and runtime-maintenance release. Its Pi 1.3 update affects web search and related tools, while its model-routing, recovery, session, and storage changes reinforce that agent reliability is shaped by the harness around the model call.
Open question
How much source-level migration is required for existing Pi applications that consume the affected tools, particularly where callers assume a previous return-value shape?