What causes context pollution in a long-running agent?

Attempt it

Context pollution is when an agent's growing message history (tool calls, observations, intermediate thoughts) crowds out the original task or the recent relevant signal, so the model loses track or gets confused. It is caused by every step appending to the prompt without compression. Mitigations include summarising old turns, dropping irrelevant tool output, and using a separate scratchpad agent.

Your answer

An agent works by adding things to its prompt step after step. Every thought it generates, every tool call it makes, every tool result it reads, gets appended to the running message history. After 30 or 40 steps that history is huge. **Context pollution** is what happens next. The growing pile of intermediate text crowds out the original task or the most recent useful signal. The model still sees everything, but it cannot focus. The original instruction sits at the top buried under tens of thousands of words of detours and the model starts behaving as if the most recent noise is the actual goal. Two things cause it. The first is that nothing is ever removed: tool calls and results stack up forever unless someone prunes them. The second is that not all tool output is useful, so the prompt fills up with content that has no bearing on the next decision. A 50-page document the agent skimmed for one sentence still occupies the full 50 pages in context. The fixes are equally concrete. Summarise old turns into a short paragraph as the conversation gets long. Drop tool outputs that are no longer needed. Keep the original instruction near the front and pinned in a structured place. Some teams run a separate scratchpad agent that holds notes outside the main thread.

**Context pollution** is the degradation of an agent's behaviour as its accumulated message history (tool calls, results, intermediate thoughts) crowds out the original task or the most recent relevant signal. The model still receives all the tokens, but its attention is not uniform, and the more noise it has to wade through, the worse it grasps what to do next. The root cause is that every step appends to the prompt without any compression. A tool that returned a 20,000-token page of HTML stays in the context as a 20,000-token blob even when the agent only needed one fact from it. After 30 steps, the prompt is dominated by transcripts of intermediate work, and the original user instruction sits buried at the top. The failure shows up in two characteristic ways. The first is **lost-in-the-middle**: the model attends more to the start and end of the context than to the middle, so anything important that ended up in the middle stops being followed. The second is goal drift: the most recent noisy tool output starts to look more salient than the original task, and the next action chases the noise. Mitigations are well known. Summarise old turns into compact memory. Drop or truncate tool outputs that are no longer needed. Move long reference material into a retrieval store rather than the live context. Pin the original goal near the bottom of the prompt where attention is strongest.

Quick reference

TL;DR

Context pollution is when an agent's accumulated history of tool calls, observations, and thoughts crowds out the original task or the relevant signal, so the model loses focus or gets confused.

Memory aid

Sign in for the mnemonic that makes this stick. See Pro pricing.

Easy to grasp

Imagine a tutor helping a student with one math problem. Every five minutes the tutor writes a fresh note: 'asked about fractions, then about decimals, then about negative numbers.' After two hours the notepad is full of side trips and the tutor can barely remember what problem they were originally solving. Context pollution is that notepad effect for an agent. Every tool call, every search result, every intermediate thought gets appended to the prompt. The original goal sits at the top buried under thousands of words of detours. When the model goes to take the next step, it spends most of its attention on the loudest noise nearby instead of the quiet original instruction.

Key concepts

Context Pollution Context Window Lost in the Middle

Detailed answer & concept explanation

~7 min read

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.

Sign in for 5 free unlocks/day or go Pro for unlimited. See Pro pricing.

Quick scan · 2–4 min

Everything important, quickly.

Define context pollution as growing history crowding out the original task or recent signal. Explain why it is a signal to noise problem, not a capacity problem. Describe two mechanisms: lost-in-the-middle attention skew and goal versus noise salience competition. Close with the four mitigation families and the working set versus log mindset.

Real-world examples

Real products, models, and research that use this idea.

LangGraph offers built-in checkpointing and a message-trimming policy so long-running agents can compress old turns rather than carry them indefinitely.
Anthropic's agent guides recommend summarising prior tool results once their key fact has been extracted, to keep the active prompt focused.
Cursor's coding agent truncates large file contents to the specific symbols and lines the next step needs, rather than carrying every read file in full.
Devin and other long-horizon coding agents use a separate scratchpad or notes file that lives outside the main message thread to avoid polluting the active context.
Production support agents typically summarise the ticket plus the last three exchanges and drop earlier verbose tool output once it has been distilled.

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QA frontier model with a one-million-token context window still degrades on long agent runs. Why is capacity not enough?

Sign in or go Pro to see the approach for this follow-up.

QWhat is the failure mode of overly aggressive summarisation?

Sign in or go Pro to see the approach for this follow-up.

QHow does a separate scratchpad or notes file differ from in-prompt summarisation?

Sign in or go Pro to see the approach for this follow-up.

Don't say this

Red flags and common mistakes that signal junior thinking. Click to expand.

Most common mistake

Believing a larger context window solves it. Frontier models have a million-token context, yet attention degrades and signal to noise drops well before that limit. Pollution is a quality problem, not a capacity problem.

Sign in or go Pro to see all red flags and common mistakes. See Pro pricing.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

Sign in for 5 unlocks/day or go Pro for unlimited revision sheets. See Pro pricing.

References

Primary sources. Skim if you want the original framing.