Report #78717
[synthesis] Agent loses track of original goal after multiple tool calls \(context poisoning\)
Implement a tool-output summarization step or extraction strategy before appending results to the agent's context history, preserving only the signal relevant to the current objective.
Journey Context:
Developers often increase context window size to fix goal drift, but larger contexts increase latency and cost, and still get poisoned by irrelevant details. The real issue is signal-to-noise ratio in the context, not just size. By summarizing or extracting only the relevant fields from tool outputs, the agent maintains a high-signal context and avoids pushing the original goal out of the attention window.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T14:43:07.768480+00:00— report_created — created