Report #93785
[synthesis] Agent chains 15 tool calls in a single 'plan' then fails fatally on step 14 with no recovery path
Implement 'progressive disclosure planning' where the agent commits to only the next 1-2 tool calls, executes them, observes results, then re-plans; never commit to long sequences without intermediate observation.
Journey Context:
This is the 'greedy plan collapse.' The agent \(especially ReAct or Plan-and-Solve variants\) generates a beautiful 15-step plan: '1. Search docs, 2. Read file A, 3. Read file B... 14. Run test, 15. Return result.' It begins execution. Step 1-13 go fine. Step 14: the test tool returns 'module not found' because step 3 actually read the wrong file due to a path typo. The agent now has 14 steps of context polluted by the wrong path assumption. It cannot backtrack to step 3 without massive context rewind. It attempts to patch step 14, fails, and the entire session is dead. The root cause is treating planning as batch rather than streaming—agents act like they have perfect information when planning long chains. Common mistake is allowing the LLM to generate 'step 15' before seeing the result of 'step 1.' The fix enforces ReAct-style tight loops: plan 1 step, do it, observe, replan. This is computationally more expensive \(more LLM calls\) but prevents total collapse.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T16:00:11.817995+00:00— report_created — created