Run long agent tasks on Cloudflare without losing progress

Cloudflare has confirmed Agents SDK v0.17.0 with detached background sub-agent runs, durable progress milestones, and a single runTurn entry point. Confidence level: confirmed. The update matters for teams building agents that import data, research, generate files, or recover after deploys without dropping the user-visible task.

What changed

Cloudflare published the Agents SDK v0.17.0 changelog on June 26, 2026. The release lets runAgentTool dispatch a child agent in detached mode, return a run handle immediately, and keep that run owned by a durable backbone instead of the calling turn.

The same update adds progress reporting, durable milestones, cancellation, bounded budgets, recovery fixes, a shared React chat core, and runTurn(options) for wait, submit, and stream modes.

Key takeaways

• Background sub-agent runs now have a durable owner instead of depending on the spawning turn.
• Progress snapshots and named milestones make long work visible without forcing the user into a blocking chat turn.
• cancelAgentTool(runId) and maxBudgetMs help stop abandoned work from holding resources indefinitely.
• GitHub release notes corroborate the agents@0.17.0 package release and the detached sub-agent changes.
• Experimental server actions and channels are present, but Cloudflare says their APIs may change.

Availability and access

Builders can install the current packages with the package-manager commands listed in Cloudflare's changelog, including agents@latest, @cloudflare/think@latest, and @cloudflare/ai-chat@latest. The GitHub release page lists agents@0.17.0 dated June 26.

This is a developer SDK release, not a dashboard-only switch. Teams should update in a branch, run chat recovery tests, and verify Durable Object behavior under deploys, evictions, reconnects, cancellations, and long idle periods.

Practical LinkLoot angle

This update is useful when agent work is longer than a normal chat turn. A support agent can start a data import, a research agent can continue gathering sources, or a build agent can generate assets while the parent agent remains responsive.

For teams comparing agent infrastructure, pair this with LinkLoot's guide to AI agent tools. The decision point is whether you need durable background execution inside Workers, or whether a queue, workflow engine, or external worker is still the cleaner fit.

What to verify before you act

• Confirm your app uses SDK versions that include agents@0.17.0 and the matching @cloudflare/think or @cloudflare/ai-chat package.
• Add explicit maxBudgetMs, cancellation, and stale-run cleanup behavior for detached work.
• Test deploy, reconnect, Durable Object eviction, stream-stall, and interrupted tool-call recovery.
• Decide which progress signals should remain live-only and which milestones should be persisted.
• Treat experimental server actions and channels as preview surfaces until Cloudflare stabilizes those APIs.

Source check

Confirmed by: Cloudflare's official changelog states the June 26, 2026 Agents SDK v0.17.0 release, detached background sub-agent runs, progress milestones, runTurn, recovery fixes, and installation commands.

Independent context: the cloudflare/agents GitHub releases page lists agents@0.17.0 and matching package releases from June 26, with release notes for detached runs and progress signaling. Cloudflare's sub-agents documentation explains the runtime model behind child agents, isolated storage, RPC stubs, lifecycle controls, and routing.