docs: clarify subagent vs delegation distinction in Lesson 16#86
Closed
calebwilson706 wants to merge 1 commit into
Closed
docs: clarify subagent vs delegation distinction in Lesson 16#86calebwilson706 wants to merge 1 commit into
calebwilson706 wants to merge 1 commit into
Conversation
Separate the three overloaded meanings of "delegation" so the lesson no longer conflates distinct execution models: - Move `/delegate` out of "Triggering subagents reliably" into its own "Full delegation with `/delegate`" section. It hands the whole request to a cloud runner and does not spawn a subagent, so listing it as a subagent trigger taught the wrong mental model. - Add a comparison table contrasting subagents (in-session, isolated context) with `/delegate` (separate cloud runner, fresh environment). - Add a framing note at the top of Concepts flagging the three senses of "delegation": subagents, pipelines and `/delegate`. - Cross-reference Lesson 12's `infer: true` for the auto-delegation behaviour so that thread reads as one concept across both lessons. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
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.
Summary
Lesson 16 (Agent Delegation) overloaded the word "delegation" across three genuinely different mechanisms and filed one of them under the wrong concept. This tightens the distinction.
What changed
/delegateout of "Triggering subagents reliably" into its own "Full delegation with/delegate" section./delegatehands the entire request to a cloud agent runner and does not spawn a subagent, so listing it as subagent-trigger Replace American English spelling with UK English #4 taught the wrong mental model./delegate(separate cloud runner, fresh environment)./delegate.infer: truefor the auto-delegation behaviour, so that thread reads as a single concept across both lessons.Why
The custom-agents (L12) ↔ delegation (L16) split is sound, but inside L16 "delegation" meant subagent execution, agent pipelines, and full cloud handoff interchangeably. The
/delegatemis-grouping was the sharpest issue: it actively conflated an in-session subagent with a separate cloud runner.🤖 Generated with Claude Code