Orchestrate subagents at scale with dynamic workflows changedworkflows
Nearest release: v2.1.250, published under an hour before 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+1added
Lines−1removed
From line
167
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 167, old and new numbered
/
from line 167
167167| Bypass permissions | Claude Code doesn't prompt you. The run starts immediately |
168168| `claude -p`, Agent SDK | Claude Code doesn't prompt you |
169169
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.
170In `claude -p` and the Agent SDK, the workflow runs only when something else allows the Workflow tool call.
171171
172172In 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.
173173
No line in this hunk matches that.