liveBook · Manning

Context rot

As explained in Context Engineering

Context rot is degradation in the usefulness of accumulated context as a task evolves and its information loses relevance, structure, or priority.

Context rot is the gradual loss of usefulness in accumulated context as a task evolves. Old decisions, intermediate results, summaries, and tool outputs can remain after their value expires, causing an agent to repeat old assumptions or treat temporary details as current. section 8.1.1

Unlike staleness, context rot is not simply a matter of age: accumulated information also loses relevance, structure, or priority. Mitigate it by pruning context, tracking explicit task state, and summarizing only what the next step needs. section 8.1.1

Instruction artifacts can also contribute to context rot when they preserve obsolete paths, scripts, or temporary constraints. Keep them concise, clarify how nested guidance relates to root guidance, and review changes so outdated directives can be pruned. section 2.4.2

How Context Engineering covers it

How deep it goes
Defines the degradation, describes its symptoms, and names mitigations without specifying implementation procedures.
Examples
Uses long conversations, multi-step agent runs, and obsolete commands or paths as examples.
What you can do after
Diagnose context degradation and apply pruning, explicit task state, focused summaries, or directive reviews.
How it connects
Connects context rot to context pruning, task state, summaries, and instruction artifacts.

Also explained in

Compare how 2 books explain context rot →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Context Engineering. The section links point to the parts of the book it draws on.