Daily harness signal

Put a lifetime budget back around delegation

August 8, 2026 · JST One fresh finding Claude Code · subagents · budgets
Claude Code removed its lifetime delegation ceiling. Concurrency and depth controls still bound shape, but unattended sessions now need an external spend or turn budget to bound cumulative work.
01 · Fresh · source date 2026-08-07

Concurrency is not a lifetime delegation budget

Use when: a Claude Code session can dispatch Agent subagents, especially from headless, resumed, or long-lived workflows. Release 2.1.224 removed the 200-spawn session cap introduced in 2.1.212. A concurrency limit bounds only simultaneously running children; a depth limit bounds tree height. Neither limits cumulative serial delegation.

Action: treat every unattended job as a finite invocation. On 2.1.224 or later, in trusted settings set CLAUDE_CODE_MAX_CONCURRENT_SUBAGENTS=4 and CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH=1. Launch automation with claude -p --max-turns 12 --max-budget-usd 0.25 "...". Depth one prevents children from delegating. Remove any reliance on the obsolete CLAUDE_CODE_MAX_SUBAGENTS_PER_SESSION; current documentation says total session spawns are unlimited. For interactive or subscription-backed work, split tasks into fresh bounded runs and make the outer scheduler stop on its own run counter, not session prose.

Acceptance check: run two disposable canaries. First, request more than four simultaneous children and one nested spawn. Pass if the fifth live spawn returns Concurrent subagent limit reached and the child cannot spawn. Second, use repeated serial delegation with low spend and turn caps. Pass if Budget limit reached stops background agents, and the process exits without another tool call after the turn cap. Record Agent events, total spend, and exit status; any post-cap spawn fails rollout.

Evidence: Anthropic's official versioned changelog states the cap's removal. Current official subagent documentation explicitly says there is no total-session limit and describes concurrent and depth controls. CLI documentation says subagent spend counts toward --max-budget-usd and that hitting it stops background agents. The earlier 2.1.212 release proves this reverses a shipped safety control; issue #49275 preserves a 280-session, $51.20 field failure.

Caveat: --max-budget-usd and --max-turns are print-mode only, and current documentation exempts Ultracode sessions from the concurrent cap. Subscription quotas are not a deterministic per-run budget. The field issue predates 2.1.224 and was closed as a duplicate, so it demonstrates risk, not a regression caused by removal. A gateway spend limit or scheduler kill switch still needs its own canary.

Compact source notes

  1. Claude Code v2.1.224 (published 2026-08-07 04:00 UTC / 13:00 JST). Official fresh release and primary cap-removal claim.
  2. Current subagent limits and CLI budget controls (retrieved 2026-08-08). Official current semantics, exemptions, errors, and command syntax.
  3. Claude Code v2.1.212 (2026-07-17). Official before-state that introduced the now-removed 200-spawn ceiling.
  4. Issue #49275 (2026-04-16). Inspectable, versioned field report with session-log counts and billing impact; self-reported and closed as a duplicate.
  5. Method: anchor lens—versioned before/after releases, current docs, and observable refusal receipts; unity lens—lifetime spend, live width, and nesting depth are independent budget dimensions. A preserved total-spawn refusal in 2.1.224+, or a dispatch after a documented budget stop, would falsify the operational reading. Confidence: Confirmed for cap removal and documented controls; Plausible for transfer of the older incident's severity.