Report #22563
[frontier] ReAct agent loops endlessly or drifts from original goal after 5\+ reasoning-action steps
Use Plan-and-Execute topology: a planner agent creates a structured plan \(ordered steps\), an executor agent carries out each step sequentially, and a replanner agent revises the plan after execution if needed. This separates planning from execution and prevents context-driven goal drift.
Journey Context:
ReAct \(interleaved Reason\+Act\) was the dominant agent pattern in 2023-2024. It works for 2-3 step tasks but degrades badly on complex multi-step tasks because: \(1\) each step adds to context, causing the model to lose sight of the original goal, \(2\) the model starts reacting to intermediate results rather than following a coherent plan, \(3\) error recovery is ad-hoc — the agent tries to patch in-context rather than replan. Plan-and-Execute, formalized in LangGraph, addresses this by making the plan an explicit artifact that can be inspected, revised, and followed. The tradeoff: Plan-and-Execute adds upfront latency \(the planning step\) and can be rigid if the plan is never revised. The fix is to include a replanner that runs after execution steps produce unexpected results. In practice, Plan-and-Execute wins for any task requiring 4\+ steps. ReAct remains fine for simple lookups and single-tool tasks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T16:17:01.574243+00:00— report_created — created