If you build agents on Cloudflare Workers, you've probably hit this wall: a fix or a feature you want lives in a newer Agents SDK, but bumping to it drags in AI SDK 7, and Vercel's 6→7 jump is a breaking-change migration you didn't plan for this sprint. So you skip the update and fall behind. On July 23, Cloudflare removed that trap.

The Agents SDK packages now support both AI SDK v6 and v7. Four of them — agents, @cloudflare/ai-chat, @cloudflare/codemode, and @cloudflare/think — widened their peer range to ai@^6 || ^7 and @ai-sdk/react@^3 || ^4. That's not a headline feature. It's something more useful for a solo team: two release clocks that no longer have to tick together.

What actually changed#

Before, the Cloudflare packages pinned a single AI SDK major, so their release cadence and Vercel's were coupled — update one, inherit the other. Now they float across both majors. Cloudflare is explicit that existing v6 apps do not need to migrate, and that you can adopt v7 without changing the Cloudflare Agents APIs you already call. The @cloudflare/think harness carries the weight here: it normalizes streaming, tool-completion events, and telemetry across both SDK versions, which is why a working v6 integration keeps working after you bump the Cloudflare packages.

The one rule: pair matching majors#

The peer range is permissive, and that's the only place you can hurt yourself. Match the majors:

Crossing them — ai@^6 with @ai-sdk/react@^4 — satisfies the range on paper and breaks at runtime. So the two clean package.json shapes are:

// Path A — stay on v6, just take the Cloudflare updates
{
  "dependencies": {
    "agents": "^0.19.0",
    "ai": "^6",
    "@ai-sdk/react": "^3"
  }
}

// Path B — move to v7 on your own schedule
{
  "dependencies": {
    "agents": "^0.19.0",
    "ai": "^7",
    "@ai-sdk/react": "^4"
  }
}

Bump @cloudflare/ai-chat, @cloudflare/codemode, and @cloudflare/think alongside agents to the same release; leave ai and @ai-sdk/react exactly where they are for Path A.

Which path to take#

For most teams the answer is Path A, today. If you have a shipping v6 app, take the Cloudflare updates now — including the background sub-agents and unified turn entry point from v0.17 and everything since — and leave AI SDK 7 for when you actually want its changes. There's no longer a reason to couple the two.

The value here isn't v7. It's that "I want the platform fix" and "I'm ready for the model-SDK's breaking changes" are finally two separate decisions instead of one.

Take Path B when v7's changes are worth a scheduled migration on their own merits — and note that the work you're signing up for is the Vercel AI SDK 6→7 migration, not a Cloudflare one. Your Durable Object agents, your routing, your harness config all stay put.

The broader signal is a maturity one. A platform SDK that pins you to one version of a fast-moving dependency is a platform that makes you choose between security and stability. One that floats across majors — and does the normalization work in its own harness so you don't — is a platform you can build a company on without dreading the next npm update. If you're still weighing Cloudflare against the other agent runtimes, this is a point in its column.