Spot The Subagent That Will Flood The Thread
Identify subagent design choices that defeat context isolation by using vague scope, broad tools, or no return contract.
A log-analysis subagent is being created before a production debug session. Which hotspots reveal a subagent spec that will flood the main thread? All tools enabled for a narrow log worker Correct. Subagents should have specific tool access. Giving a narrow log worker broad write and external tools invites wandering, permission risk, and irrelevant context. No structured return format Correct. Without a return contract, the worker may paste raw logs back into the main thread. The point of a subagent is to return only synthesized signal. Named worker visible at top A clear name helps invocation. The issue would be…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in