Claude Code Just Removed the 200-Subagent Cap. That Ceiling Was Doing Work You Never Wrote.
v2.1.224 lifts the 200-subagent-per-session spawn cap and lets sessions run on your own machines. Two limits you were relying on without knowing it just became your problem.
NeuroX AI · August 9, 2026
Claude Code v2.1.224 shipped on August 7 with a one-line changelog entry worth more than its length: "Removed the 200-subagent-per-session spawn cap; long-running sessions no longer refuse new agents." Concurrency and depth limits still apply. The lifetime ceiling doesn't.
That cap was a backstop, and most teams were leaning on it without ever deciding to. A runaway loop in a 14-hour session used to end with a refusal at agent 201. Now it ends when something you built says stop — a token budget, a wall clock, a kill switch. If you can't name which of those fires first in your own harness, you don't have one.
The same release adds claude self-hosted-runner, which turns your machines or containers into the execution target for web, mobile, and desktop sessions on Team and Enterprise plans. Isolation moves onto your hardware. So does the blast radius.
Read those two together with the fix one version earlier — 2.1.223 closed a Bash permission bypass where a crafted command could hide parts of itself from permission checks. Higher spawn ceiling, execution on your own boxes, permission checks that had a real hole in them last week. The capability arrives in a point release. The containment is still an engineering project.