Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One change · api

migration changedmanaged-agents/migration

Nearest release: v2.1.307, published an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Recorded here
Lines+3added
Lines−3removed
From line 20 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits22to this page, all time

The whole hunk

from line 20, old and new numbered
/
lines
from line 20
2020 
2121| Before | After |
2222| ------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------- |
23| You maintain the conversation history array and pass it back on every turn. | The session stores history server-side. Send events, receive events. |
23| You maintain the conversation history array and pass it back on every turn. | The session stores history server-side. You send events and receive events. |
2424| You iterate `tool_use` content blocks, run each tool, and loop back with `tool_result` messages. | Pre-built tools run inside the sandbox automatically. You only handle custom tools through `agent.custom_tool_use` events. |
2525| You provision your own sandbox for running agent-generated code. | The session sandbox handles code execution, file operations, and bash. |
2626| You decide when the loop is done. | The session emits `session.status_idle` when the agent has nothing more to do. |
from line 509
509509 
510510## From the Claude Agent SDK
511511 
512If you built with the [Claude Agent SDK](https://code.claude.com/docs/en/agent-sdk/overview), you're already working with agents, tools, and sessions as concepts. The difference is where they run: the SDK runs in a process you operate, while Managed Agents runs in Anthropic's infrastructure. Most of the migration is mapping SDK configuration objects to their API-side equivalents.
512If you built with the [Claude Agent SDK](https://code.claude.com/docs/en/agent-sdk/overview), you're already working with agents, tools, and sessions as concepts. The difference is where they run: the SDK runs in a process you operate, whereas Managed Agents runs in Anthropic's infrastructure. Most of the migration is mapping SDK configuration objects to their API-side equivalents.
513513 
514514### What changes
515515 
from line 1241
12411241 
12421242## Migrating between model versions
12431243 
1244When a new Claude model is released, migrating a Claude Managed Agents integration is typically a one-field change: update `model` (csharp, go: `Model`) on your [agent definition](https://platform.claude.com/docs/en/managed-agents/agent-setup) and the change takes effect on the next session you create.
1244When a new Claude model is released, migrating a Claude Managed Agents integration is typically a one-field change: update `model` (csharp, go: `Model`) on your [agent definition](https://platform.claude.com/docs/en/managed-agents/agent-setup), and the change takes effect on the next session you create.
12451245 
12461246<CodeGroup defaultLanguage="CLI">
12471247 ```bash cURL
Feedback