19. Preventing Context Pollution with Subagents (Delegating Heavy Lifting)
Show notes
In Episode 19 of Beyond Prompting, author Sho Shimoda explores how to manage complex, search-heavy engineering tasks without cluttering your main conversation window using Subagents. When an agent reads dozens of files, runs multiple searches, and pursues false leads, that intermediate noise dilutes the main conversation's working memory. In this episode, we break down:
- Solving Context Pollution: Why the primary benefit of delegation is keeping your main conversation's context clean by running heavy investigations in isolated, disposable subagent context windows that return only concise summaries.
- The Three Justifications for Subagents: Identifying when to delegate based on context economy (high byproduct-to-conclusion ratio), specialized roles (such as a read-only security or schema reviewer), and true task parallelism.
- Defining Subagents (.claude/agents/): Structuring custom subagents in Markdown with YAML frontmatter, restricting tool access (e.g. limiting to Read, Grep, and Glob), and why writing a clear description field is the entire invocation mechanism.
- What Crosses the Boundary: Understanding what a subagent inherits (system prompt, CLAUDE.md, git snapshot, brief) versus what stays isolated (conversation history and intermediate tool outputs), and using agent IDs to resume subagents via SendMessage.
- Forks, Depth, and Concurrency: Distinguishing standard subagents from forks (/subtask), navigating spawn depth limits (up to 3 layers), concurrency caps (up to 20 subagents), and knowing when not to delegate.
(Note for listeners: This episode covers Chapter 19 of Sho Shimoda's book RUNNING CLAUDE: The Operator’s Guide to Chat, Cowork and Claude Code, available on Amazon as the successor book to Master Claude: Chat, Cowork and Code).