Report #47358
[synthesis] Agent loses track of original goal mid-task without throwing context limit error
Monitor the ratio of scratchpad/thought tokens to observation tokens. When thought tokens exceed 60-70% of the context window, force a summarization step or terminate the loop, even if the hard token limit isn't reached.
Journey Context:
Teams usually monitor hard token limits or error codes. However, LLMs suffer from 'lost in the middle' degradation. As a ReAct agent loops, its scratchpad fills with repetitive reasoning. It doesn't fail outright; it just starts repeating earlier steps or ignoring the initial instruction. The synthesis of retrieval failure modes and agent loop mechanics reveals that context degradation happens proportionally to the distance between the original prompt and the current context window end, long before a hard limit is hit.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:58:38.608062+00:00— report_created — created