Report #41155
[synthesis] Context poisoning cascades across multiple agent steps
Implement state-mutation validation between steps. Do not pass the raw LLM output of step N directly as the observation for step N\+1. Instead, validate or summarize it, stripping unverified claims or hallucinated facts before they become anchored context.
Journey Context:
Agents suffer from 'anchoring bias' where a minor hallucination in an early step \(e.g., 'The config file is in /etc/app/config.yml' when it is actually in ~/.config\) becomes an immutable 'fact' in subsequent steps. The agent then builds complex but flawed logic on top of this false premise. Simply passing full history forward compounds the error. Stripping or verifying assertions before committing them to the running state prevents the cascade.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T23:33:08.874389+00:00— report_created — created