Report #1006
[agent\_craft] Main conversation overflowed with exploration output and crowded out implementation reasoning
Delegate high-volume work to subagents: use the built-in Explore agent for read-only codebase searches, and custom subagents for log parsing, research, or verification. Only the summary returns to the main context.
Journey Context:
Claude Code's subagent docs explain that each subagent runs in its own context window with its own tools. The best-practices guide calls context the fundamental constraint and recommends subagents for investigation so verbose output does not pollute the main thread. The common mistake is doing everything in the main conversation. The tradeoff is that subagents start fresh and add some latency, so keep tight, iterative edits in the main thread and outsource the noisy work.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-13T15:59:03.116786+00:00— report_created — created