Orchestrate subagents at scale with dynamic workflows changedworkflows
Nearest release: v2.1.311, published an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 26 Oct 2026 20:56 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 26 Oct 2026 21:07 UTC.
Upstream edited
Recorded here
Lines+6added
Lines−5removed
From line
329
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits51to this page, all time
The whole hunk
from line 329, old and new numbered
/
from line 329
329329
330330The workflow runtime executes the script in an isolated environment, separate from your conversation. Intermediate results stay in script variables instead of landing in Claude's context.
331331
332Every run writes its script to a file under your session's directory in `~/.claude/projects/`. Claude receives the path when the run starts, so you can ask for it. You can open that file to read the orchestration Claude wrote, diff it against a previous run's script, or edit it and ask Claude to relaunch from the edited version.
332Unless Claude starts a run from a script file's path, Claude Code writes the run's script to a file under your session's directory in `~/.claude/projects/`. Claude receives the script's path when the run starts, so you can ask for it. You can open that file to read the orchestration Claude wrote, diff it against a previous run's script, or edit it and ask Claude to relaunch from the edited version.
333333
334334Claude can start a workflow only from a script file the session is already allowed to read. To run a script kept outside your working directory, add its directory with [`/add-dir`](https://code.claude.com/docs/en/permissions#working-directories) or a [Read allow rule](https://code.claude.com/docs/en/permissions.md#read-and-edit) first.
335335
from line 383
383383
384384#### Resume after you leave the session
385385
386You can resume a run within the same Claude Code session. What happens to a running workflow when you leave the session depends on how you leave:
386If you background your session or exit Claude Code while a workflow run is in progress, the run doesn't continue on its own. The run continues only when Claude relaunches it with a `Workflow` call, which [replays the run from its saved results](#which-agents-run-again).
387387
388* If you [background the session](https://code.claude.com/docs/en/agent-view.md#what-carries-over-when-you-background), Claude Code replays the run the same way in the background session and continues it.
389* If you exit Claude Code while a workflow is running and [agent view is on](https://code.claude.com/docs/en/agent-view.md#from-inside-a-session), the exit dialog offers `Move to background and exit`, which carries the run over the same way. If you choose `Exit and stop tasks` instead, or the option isn't offered, the run stops with the session. Claude Code keeps the run's saved results under that session's directory in `~/.claude/projects/`, so a session you resume with `claude --resume` can replay them when you ask Claude to relaunch the workflow. In a session you start fresh, Claude has no earlier run to relaunch and starts the workflow over as a new run.
388* **You backgrounded the session or chose [`Move to background and exit`](https://code.claude.com/docs/en/agent-view#from-inside-a-session)**: if the run hasn't continued when you check the [background session](https://code.claude.com/docs/en/agent-view.md#what-carries-over-when-you-background), ask Claude there to relaunch the workflow. Depending on your [permission mode](#approve-the-plan-before-it-runs), Claude Code asks you to approve the relaunch first. If the session shows under `Needs input` in agent view, [attach to it](https://code.claude.com/docs/en/agent-view.md#attach-to-a-session) to answer the approval prompt.
389* **The relaunch in the background session failed with `nothing to resume`**: ask Claude to start the workflow over as a new run. If Claude started the run from the path of a script file outside `~/.claude/projects/`, such as one in your working directory, Claude can't relaunch it in the background session.
390* **You chose `Exit and stop tasks`, or weren't offered `Move to background and exit`**: the run stopped with the session, and Claude Code keeps the run's saved results under that session's directory in `~/.claude/projects/`. Resume the session with `claude --resume` in your shell, then ask Claude to relaunch the workflow. In a fresh session, Claude has no earlier run to relaunch and starts the workflow over.
390391
391392In a [cloud session](https://code.claude.com/docs/en/claude-code-on-the-web.md), Claude Code also saves the run's results with the session's conversation history, which survives when the session's VM is reclaimed. When you [reopen such a session](https://code.claude.com/docs/en/claude-code-on-the-web.md#environment-expired) and ask Claude to relaunch the workflow, completed agents still return their saved results.
392393
No line in this hunk matches that.