docs: correct subagent nesting default (reversed in 2.1.219) and stale Algorithm LATEST pointer - #1655
Open
elhoim wants to merge 2 commits into
Open
docs: correct subagent nesting default (reversed in 2.1.219) and stale Algorithm LATEST pointer#1655elhoim wants to merge 2 commits into
elhoim wants to merge 2 commits into
Conversation
The nesting default has moved twice in three releases: 5 until 2.1.217, 1 in 2.1.217, and 3 from 2.1.219. Guidance stating that subagents cannot spawn subagents steers away from a pattern the platform now enables by default. Record the current depth-3 default with the flag to flatten it, and add the two per-session ceilings (200 subagent spawns, 200 WebSearch calls) that a long fan-out session can actually reach. Wording on the concurrency cap stays neutral on what happens to over-cap spawns, per the note on danielmiessler#1569 that the changelog does not state whether they queue or are refused.
The row that teaches how to resolve the Algorithm version named 8.1.0 while ALGORITHM/LATEST reads 8.4.0 — three versions of drift in the one place a reader looks up the answer. Line 26 of the same file was already correct, so this was a single missed edit rather than a systemic lag. (cherry picked from commit deac16f)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two stale-fact corrections in
DOCUMENTATION/. No behaviour change.Subagent nesting default
The default has moved twice in three releases — 5 until 2.1.217, 1 in 2.1.217, 3 from 2.1.219 — and the guidance still said subagents cannot spawn subagents, steering away from a pattern the platform now enables by default. Records the current depth-3 default with
CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH=1to flatten it, plus the version history so the next move is easy to spot.Also adds the two per-session ceilings (200 subagent spawns, 200 WebSearch calls) that a long fan-out session can actually reach.
Per your note on #1569, the concurrency-cap wording stays neutral on what happens to over-cap spawns — the changelog states the cap but not whether they queue or are refused.
Algorithm version pointer
The row that teaches how to resolve the Algorithm version named 8.1.0 while
ALGORITHM/LATESTreads 8.4.0. Line 26 of the same file was already correct, so this was a single missed edit rather than systemic lag.Two notes so you can close this fast if it is already handled:
DelegationSystem.mdis retired to history-only status. This edit is offered on the same reasoning you gave there — a known-false claim shouldn't ride under a RETIRED banner. If the retirement means you'd rather not touch it at all, closing is fine.