Under the hoodTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SubagentsArea: what it touches
Internal ChangesKind: in v2.1.269,
What probably matters to youSection of the release
What
The code that launches subagents (used by the Agent tool, sometimes called Task, to spin up a separate Claude instance to work on a piece of a task) was rewritten with several new limits and rules:
a cap on how deeply subagents can be nested (spawning subagents that spawn further subagents), which can refuse a launch with "Subagent nesting limit reached"
a cap on how many subagents can run at once, which can be bypassed with a flag
in-process teammates are now forbidden from spawning further teammates or background agents
coordinator-spawned workers can override to inherit the coordinator's model instead of using a separate one
Why
These limits guard against runaway or excessive subagent spawning, keeping nested or concurrent agent work bounded and predictable.
Read from
Feature flag
tengu_amber_kestrelNot enough to say
Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.269: off
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree[Claude Code on the web] Fixed /model default in a cloud session leaving every later message failing in organizations that restrict which…
