Subagent spawning is now limited only by a single concurrency cap, configurable via CLAUDE_CODE_MAX_CONCURRENT_SUBAGENTS
What
Subagent spawning previously refused once a subagent hit both a fixed lifetime total and a fixed concurrent-run cap. Now only the concurrent-run limit remains, defaulting to 20 and overridable with the CLAUDE_CODE_MAX_CONCURRENT_SUBAGENTS environment variable. When the cap is reached, a new subagent launch is refused with a message telling the user to raise CLAUDE_CODE_MAX_CONCURRENT_SUBAGENTS, and the refusal is recorded as a subagent_concurrency_cap event.
Why Dropping the separate lifetime-total cap means subagents are no longer blocked just because many have run in sequence over a long session; only how many are running at once matters now, and that limit can be tuned per environment.
tengu_amber_kestrel Not enough to sayNothing 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.275: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.275. It isn't a statement about your account. What a flag value here can and cannot tell you