Subagents and Context Isolation Quiz

Answers and explanations appear as you take the quiz.

1. What mainly separates a subagent from the main agent?
   • It uses a different programming language
   • It always uses a larger model
   • It works in its own fresh context window and sends back a condensed result
   • It has no access to tools
2. Why can a filling context window be a problem even before its hard limit?
   • Quality often drops as irrelevant material piles up
   • The model's weights change
   • Tokens become cheaper
   • Tools stop working
3. Which task is the best fit for a subagent?
   • Choosing the overall architecture of a codebase
   • Writing tightly linked parts of one function in parallel
   • Keeping naming consistent across a project
   • Searching a large repository for every caller of a function
4. What is a main source of information loss with subagents?
   • Subagents delete files
   • Summaries drop details, and subagents know only what the task description said
   • Subagents cannot read text
   • The main agent forgets its own instructions
5. Why do multi-agent setups usually cost more tokens?
   • Each subagent reloads instructions and repeats some exploration
   • Subagents are billed at double rates
   • Summaries are longer than the original work
   • Parallel work is always billed as sequential
6. Why can parallel subagents produce incompatible results?
   • They share one context window
   • They always use different models
   • They cannot see each other's work while running
   • They run too slowly
7. What should a good subagent task description include?
   • Only a single word
   • The main agent's full transcript
   • Nothing, so the subagent stays unbiased
   • The goal, constraints, scope and exact output format
8. Why might a code-review subagent catch problems the main agent missed?
   • It has more tools
   • It has not seen the main agent's reasoning, so it is less likely to share the same assumptions
   • It always uses a larger model
   • It reads the code faster