Anthropic introduced dynamic workflows for Claude Code on May 28, 2026. The feature lets Claude write orchestration scripts and coordinate tens to hundreds of parallel subagents in one session.

The strongest fit is large engineering work: codebase-wide bug hunts, security audits, framework migrations, and independent adversarial review before results reach the user. The tradeoff is usage: Anthropic warns dynamic workflows consume meaningfully more tokens than normal Claude Code sessions.

Field|Current evidence
Primary source|Anthropic: Introducing dynamic workflows in Claude Code
Source date|2026-05-28
Update scope|orchestration scripts, parallel subagents, checkpoints, and high-token workflows
Verification note|Official source only; no search-result scraping, no ranking guarantee, no uncited claims

The important detail is that Claude Code can generate an orchestration script and distribute work across many subagents. That is different from a single long prompt because it changes how large tasks are decomposed, checked, and merged back into a final answer.

Teams should reserve dynamic workflows for tasks with clear partitions: migration inventories, large bug hunts, security sweeps, or independent review passes. Using the feature for small edits can waste tokens and create more review work than it saves.

The decision point is whether the task truly benefits from parallel investigation. If the work requires one coherent design judgement, a normal agent session may be safer; if it requires broad search across a codebase, subagents can improve coverage.

Limits and open questions: Anthropic's source warns about higher token use, and it does not guarantee that every subagent result is correct. Published updates should keep cost, review burden, and merge quality visible. Source handling note: KyenAI records the publisher, publication date, and source URL on the page, then keeps the update date tied to evidence-backed edits rather than automatic refreshes. When source material is thin, the system keeps interpretation narrow and waits for stronger documentation. Editorial review compares the new claim against the article summary, fact table, internal links, and listed source before allowing another optimization pass. Search outcomes are measured after publication rather than assumed at writing time.

Anthropic's Claude Code dynamic workflows can generate orchestration scripts, fan work out to subagents, and checkpoint long-running engineering tasks.

Introducing dynamic workflows in Claude Code

Claude Code Dynamic Workflows Coordinate Parallel Subagents

JetBrains' January 28 post describes the ACP Agent Registry as a directory for AI coding agents inside JetBrains IDEs and Zed. The registry builds on Agent Client Protocol so supporting agents can work across editors through one integration pattern.

The practical value is choice rather than another single-agent surface. Developers can install agents such as Gemini CLI, GitHub Copilot, OpenCode, Qwen Code, or other ACP-compatible tools, then switch based on task, pricing, governance, or team preference.

Field|Current evidence
Primary source|JetBrains: ACP Agent Registry Is Live: Find and Connect AI Coding Agents in Your JetBrains IDE
Source date|2026-01-28
Update scope|Agent Client Protocol, IDE agent discovery, one-click installation, and multi-agent choice
Verification note|Official source only; no search-result scraping, no ranking guarantee, no uncited claims

The registry is an ecosystem signal more than a single product feature. ACP makes agent interoperability possible; the registry makes it discoverable enough for normal IDE users to try multiple agents without hand-editing configuration first.

Developer-experience teams should watch ACP because it can reduce lock-in and let teams compare agents inside the IDE they already use. The governance work shifts to deciding which agents are approved, how credentials are handled, and how agent output is reviewed.

This update is useful for teams that want optionality across coding agents. If a company mandates one vendor, the registry may be less urgent, but it still matters as a sign that IDEs are becoming agent marketplaces.

Limits and open questions: the registry is a beta-style ecosystem step, and each agent can still require its own subscription, authentication, and safety model. The article should not imply uniform quality or support across listed agents. Source handling note: KyenAI records the publisher, publication date, and source URL on the page, then keeps the update date tied to evidence-backed edits rather than automatic refreshes. When source material is thin, the system keeps interpretation narrow and waits for stronger documentation. Editorial review compares the new claim against the article summary, fact table, internal links, and listed source before allowing another optimization pass. Search outcomes are measured after publication rather than assumed at writing time.

JetBrains and Zed launched an ACP Agent Registry so developers can discover and install compatible AI coding agents directly inside supported IDEs.

Agent Workflows

Claude Code Dynamic Workflows Coordinate Parallel Subagents

JetBrains ACP Agent Registry Opens IDE Access to Multiple Coding Agents