Report #3252
[agent\_craft] Main conversation is flooded with test logs, search output, or research notes
Delegate verbose side tasks to a subagent and consume only its summary; use parallel subagents for independent research branches.
Journey Context:
Subagents run in isolated context windows, so their detailed exploration, log output, or fetched docs do not bloat the main conversation. This is the recommended pattern for running test suites, processing logs, or researching multiple modules in parallel. The cost is some startup latency and the need to write a clear delegation prompt. Keep the main thread for work where frequent back-and-forth or shared context matters; push everything that returns a wall of text into a subagent. Resume the same subagent if the task continues, rather than starting from scratch.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T15:56:21.411661+00:00— report_created — created