How Claude Code crossed from one agent per session to fleet-scale orchestration, one capability layer at a time.
2.1.50 isolation
Declarative `isolation: worktree` in agent definitions (plus paired WorktreeCreate/WorktreeRemove hooks) lets subagents run in isolated git worktrees automatically — the key new fan-out orchestration primitive in 2.1.50. The rest is predominantly memory-leak hardening.
2.1.71 autonomy
Cron scheduling tools for recurring prompts within a session — the first changelog-stated primitive that lets an agent schedule recurring work itself, which directly extends multi-agent/long-running orchestration surface (paired with the new `/loop` command for the user-facing recurrence form).
2.1.111 fan-out
`/ultrareview` ships cloud-based parallel multi-agent code review — the only new primitive in this release that is itself an agent-orchestration mechanism, directly mirroring the fan-out pattern this test instruments.
2.1.139 autonomy
Agent view (`claude agents`, Research Preview) is the marquee primitive: a single list of every Claude Code session — running, blocked on you, or done — which is exactly the cross-session fan-out monitoring surface a multi-agent orchestration test needs. Real feature release (agent view, `/goal`, two new hook fields, plugin details, subagent identity headers), but the bulk of the changelog (~40 of ~50 bullets) is bugfix hardening.
2.1.154 fan-out keystone
Dynamic workflows (`/workflows`): you can now ask Claude to create a workflow and it orchestrates work across tens to hundreds of background agents, turning single-session prompting into fan-out, multi-agent orchestration of large/complex tasks — this is the primitive the whole 2.1.154 test is instrumenting.
2.1.160 fan-out
Almost entirely hardening: 2.1.160 is a bugfix/safety release. The closest thing to a new primitive is the dynamic-workflow trigger keyword being renamed from `workflow` to `ultracode` — relevant to orchestration because it changes how the fan-out/dynamic-workflow feature is invoked and de-conflicts the common word "workflow" from triggering a run. This is a rename of an existing trigger, not a net-new capability. No genuinely new tools, hooks, or settings were added; the new behaviors are safety prompts and friction reductions on existing primitives.
2.1.169 control-plane
Hardening-heavy release: ~25 fixes/improvements vs. 3 genuine new primitives (plus 2 new surfaces bundled into fixes). The standout primitive for agent orchestration is `disableBundledSkills` / `CLAUDE_CODE_DISABLE_BUNDLED_SKILLS`, which lets an orchestrator strip the model's default skill/workflow/command surface down to a controlled set — a targeted control-plane lever for deterministic multi-agent fan-out. Output is changelog-derived, not runtime-tested.