Bigger context windows don't make agents more reliable a study of 18 frontier models found all of them degraded as context grew, a phenomenon called "context rot." The video breaks down four ways an agent's context window goes bad (poisoning, distraction, confusion, clash) using a running example of an agent migrating a codebase to a new database driver. Each fix validate, compact, curate, prune works by deliberately throwing information away.
- Context windows have grown to a million tokens or more, but attention is a finite budget spread across those tokens, so every token competes rather than being looked up like a database row.
- A typical agent context window fills up with system prompt, task prompt, project instructions (e.g. an agents.md file), tool definitions, message history, and usually largest tool results like file contents, test output and schema dumps.
- Context poisoning: the agent misreads documentation, writes itself a false note (the new driver auto-retries connections), and then treats its own note as ground truth deleting good retry code file after file.
- Context distraction: with an hour of its own past actions in the window, the history becomes the strongest pattern for a pattern-continuation machine, so the agent repeats old ground instead of asking what the task needs next.
- Context confusion comes from tool sprawl in one benchmark a model failed a task when offered 46 tools but passed the same task with only 19.
- Context clash happens when the agent later discovers its note was wrong and records the correction, leaving two contradictory versions sitting in the window.
- Fixes: validate conclusions against something real before writing them down; compact long histories into summaries (accepting that compaction is lossy, like a photocopy of a photocopy); curate the tool set to what the job needs; prune superseded information or start a fresh window with the corrected state.
- Offloading detail into permanent files and pulling it in only when needed is suggested as a way to limit compaction's drift.
Context rot: 18 models all got worse with more context
0:16–1:12
States the counterintuitive finding that motivates the whole topic and defines context engineering in one line.
A recent study looked at 18 frontier models and it turned out that they all got less reliable as the context window got bigger. Researchers have taken to giving this thing a name, and that is context rot.
46 tools fail, 19 tools pass
6:03–6:47
A concrete, memorable benchmark result showing that simply exposing fewer tools can flip a failure into a success.
In one benchmark, a model failed a task when it was offered 46 tools, but it then passed the very same task, when it was only offered 19 tools.
The more tokens in the window, the less reliably the model uses any of them.
The window might hold a million tokens, but the attention spread across those tokens is finite.
All four fixes work by throwing something away. An agent can get better at long tasks, by holding less.