Report #97844
[agent\_craft] Agent wastes turns wandering the codebase or gets lost in research
Delegate broad exploration to a read-only subagent with a focused prompt, then act on its summary. Keep the main thread for decisions and edits.
Journey Context:
Deep codebase research burns context and interrupts flow. A subagent can traverse many files and return a compact map. The main agent stays focused on execution. The cost is that subagent context is separate, so handoffs must be explicit. Do not use subagents for one-file fixes; do use them for 'find all callers of X' or 'understand this module'.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-26T04:48:04.237711+00:00— report_created — created