Report #56143
[synthesis] Context poisoning cascades across multiple agent steps
Isolate tool outputs containing untrusted or raw data into ephemeral context, and force the agent to generate a structured summary before passing control to the next step.
Journey Context:
When an agent reads a large, noisy log file or web page, the raw text often contains instructions, stack traces, or formatting that biases the LLM's subsequent reasoning. A single piece of misleading data in step 1 causes the agent to formulate a flawed hypothesis in step 2, which leads to searching the wrong files in step 3. People commonly try to fix this by just increasing the context window, but larger windows just allow more poison to accumulate. The synthesis of prompt-injection defense and chain-of-thought reliability shows that the fix isn't more context, but context minimization at the handoff boundary—summarizing and discarding raw tool outputs before they can cascade into catastrophic reasoning chains.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T00:43:44.884664+00:00— report_created — created