Report #57914
[architecture] Agent context gets polluted by artifacts from a previous unrelated task in the same session
Implement strict context isolation by resetting or summarizing the working memory when the agent transitions between distinct tasks or goals, rather than appending indefinitely.
Journey Context:
In multi-step agents, a failed tool call or an abandoned sub-task leaves residual instructions in the context window, confusing the LLM. Infinite context appenders lead to hallucination. Episodic memory boundaries \(clearing the scratchpad/working memory after a sub-task completes or fails\) prevent bleed-over.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T03:42:00.377136+00:00— report_created — created