Document sub agent grouping and independent launches - #975
Merged
Conversation
#973 moved plain children out of the sidebar's top level and into their parent card's Sub Agents list, added `child: false` for launching outside the lineage, and capped nesting at one level. It shipped with no doc changes, so four surfaces still said a launched agent "appears as a top-level entry in the sidebar". Rewrites the Agents and Repo Tools orchestration sections around what actually renders now: the Sub Agents list, the row's session controls behind an overflow menu, the depth cap, orphan promotion when a parent is archived, and `child: false`. Corrects the agent-cycling shortcut (it skips every sub agent, not only review children), folds lineage and provenance into the list_agents bullet, and covers self-archive in the README row. The subagents skill gains the same contract in agent-facing terms — the depth cap in particular, since it fails at the point of use halfway through work the agent has already planned around. Adds a "Sub Agents" ambient tip (since 0.35.0, the release ab79797 landed in) pointing at the new agents#sub-agents anchor. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Uh oh!
There was an error while loading. Please reload this page.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Nightly docs audit. Scoped to the diff since
7d4e2a4b— #973 (lineage + sidebar grouping) and #972 (self-archive), which between them changed where a launched agent renders and shipped with no doc changes at all.What was wrong
Four surfaces still said a launched agent "appears as a top-level entry in the sidebar" and "is not nested under its parent like persona reviewers". Since #973, every agent with a parent renders as a row in that parent card's Sub Agents list; a top-level card is what
child: falsegets you.What changed
child: false, the one-level nesting cap, the row's session controls (attach/detach, resume, and the overflow menu with Pause / Session settings / Archive), orphan promotion when a parent is archived, and self-archive. Added anid="sub-agents"anchor. The Agent details paragraph no longer claims persona agents show a role block on their own card — they render as sub agent rows.child: falseadded to thedispatch_launch_agentbullet; lineage and provenance folded into thelist_agentsbullet (clears a backlog item from Surface agent delegation lineage in list_agents and messages #967).Mod+Shift+↑/↓skips every sub agent now, not only review children, and anchors on the containing card when a sub agent is selected.dispatch_launch_agent,dispatch_archive_agent,list_agents).since: 0.35.0(confirmed bygit merge-base --is-ancestor ab797976 65a75e5a), linkingagents#sub-agents.Docs only — no behavior change.
pnpm run checkand the tips unit tests pass.Deferred
agent-card.tsx's Persona block looks unreachable now (a persona agent always has a parent, and review children cascade on archive) — code cleanup, not docs.Next run: the Status Events deep-dive, which this displaced for a second time and should run regardless of what that diff turns up.
🤖 Generated with Claude Code