Claude Notes Let a Managed Agent Write a Workflow Run
The 9 October platform notes say a Managed Agent can write a workflow that runs many agents in phases, behind a beta header.
Direct answer
The Claude platform notes for 9 October 2026 say a Managed Agents agent can use dynamic workflows in beta. The agent writes a workflow, the server runs it in the background, and the session follows it through workflow_run events.
The Claude platform release notes dated 9 October 2026 say a Claude Managed Agents agent can use dynamic workflows, in beta, with the managed-agents-2026-04-01 beta header. The note describes the case of work with many pieces, such as reviewing hundreds of documents. In that case the agent can write a workflow. The note defines a workflow as a program that runs many agents in phases and combines their results. The server runs that program in the background as a workflow run.
To turn dynamic workflows on, the note says to set the agent's multiagent field to an object whose type is multiagent_20261001 and whose workflows field is an object whose type is enabled. Guidance for when to start a run goes in the agent's system prompt. Each run is followed through workflow_run events on the session's event stream. The note points to a section titled Workflow runs for the rest of the mechanics.
What this date does not change
The 9 October entry is one bullet. It does not print a price, a context-window size, or a list of models that are excluded. It does not say the feature is on without the beta header. The enablement object is written out in full, so a client that only sets a boolean would not match the shape on the page. The background run is a server-side workflow run, not a local shell loop described on this date.
FAQ
- Which header does the note require?
- It names the managed-agents-2026-04-01 beta header.
- Where does the note say the workflow runs?
- It says the server runs the workflow in the background as a workflow run.