Report #104018
[synthesis] Agent abandons its plan mid-execution when the context window fills or an exception interrupts it
Keep the plan as an explicit, versioned, mutable data structure outside the LLM context; on each turn load only the current step plus recent observations, and checkpoint after every committed state change. Never depend on the model to remember the plan.
Journey Context:
ReAct-style prompts put the plan inside the model's context, which works for short trajectories. When the window fills, compression or summarization drops plan details first; when an error occurs, the model opportunistically replans toward a simpler path. The synthesis across context-window research and production agent logs is that plans are fragile state, not robust instructions. Externalize them.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-13T05:05:49.179469+00:00— report_created — created