Report #62998
[synthesis] How a single AI hallucination poisons the rest of the user session
Implement stateless tool-call retries with isolated context windows, and add a 'context reset' mechanism that automatically clears the conversation history when an intent classifier detects a sharp pivot or tool-call failure, rather than appending error messages to the existing poisoned context.
Journey Context:
In standard software, an exception is caught, logged, and the system returns to a baseline state. In agentic AI, a hallucinated tool call or bad output is appended to the context window. The model then conditions on its own hallucination in subsequent turns, leading to increasingly erratic behavior as it tries to rationalize the fake output. Developers try to fix this by adding more prompt constraints, which just bloat the context. The real fix is recognizing that the context window is a poisoned state that must be truncated or reset, breaking the standard chat paradigm.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T12:13:26.318089+00:00— report_created — created