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
HomeDocsClaude Code CLI 27 Aug 2026
One change · claude-code

Orchestrate subagents at scale with dynamic workflows changedworkflows

Nearest release: v2.1.248, published under 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+9added
Lines−8removed
From line 152 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits47to this page, all time

The whole hunk

from line 152, old and new numbered
/
lines
from line 152
152152In the CLI, the per-run prompt shows the planned phases and these options:
153153 
154154* **Yes, run it**: start the run
155* **Yes, and don't ask again for `<name>` in `<path>`**: start, and skip this prompt for this workflow in this project from now on
155* **Yes, and don't ask again for `<name>` in `<path>`**: start, and skip this prompt for this workflow in this project from now on. Claude Code offers this option when you run a bundled, saved, or plugin workflow by name, not for a script Claude wrote for the current task.
156156* **View raw script**: read the script before deciding
157157* **No**: cancel
158158 
from line 160
160160 
161161Whether you see this prompt depends on your [permission mode](/docs/en/permission-modes):
162162 
163| Permission mode | When you're prompted |
164| :----------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------ |
165| Auto | First launch only. Any **Yes** records consent in your user settings, and later launches start without prompting. Skipped entirely when ultracode is on |
166| Manual, accept edits | Every run, unless you've selected **Yes, and don't ask again** for that workflow in this project |
167| Bypass permissions, `claude -p`, Agent SDK | Never. The run starts immediately |
163| Permission mode | When you're prompted |
164| :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------ |
165| Auto | First launch only. Any **Yes** records consent in your user settings, and later launches start without prompting. Skipped entirely when ultracode is on |
166| Manual, accept edits | Every run, unless you've selected **Yes, and don't ask again** for that workflow in this project |
167| Bypass permissions | Claude Code doesn't prompt you. The run starts immediately |
168| `claude -p`, Agent SDK | Claude Code doesn't prompt you |
168169 
170Outside bypass permission mode, in `claude -p` and the Agent SDK, Claude Code denies the workflow unless a permission rule allows the Workflow tool or your host approves it through `--permission-prompt-tool` or the SDK's `canUseTool` callback.
171 
169172In the Desktop app, an approval card shows the workflow name, the phase list, and a token-usage caution, with **Once**, **Always**, and **Deny** actions. The progress view appears in the Background tasks side pane.
170173 
171174Your permission mode controls only the launch prompt above. The subagents the workflow spawns always run in `acceptEdits` mode and inherit your [tool allowlist](/docs/en/settings-reference#permission-settings), regardless of your session's mode. File edits are auto-approved.
172175 
173176Shell commands, web fetches, and MCP tools that aren't in your allowlist can still prompt you mid-run. To avoid this on a long run, add the commands the agents need to your allowlist before starting.
174 
175In `claude -p` and the Agent SDK there is no one to prompt, so tool calls follow your configured permission rules without interactive confirmation.
176177 
177178### Save the workflow for reuse
178179 
Feedback