What is context engineering?
Updated Oct 26, 2026 · Sources listed at the end
Context engineering is the practice of choosing and maintaining the right set of information (tokens) that a model sees while it works: instructions, files, tool results and conversation history, not only the prompt you type. Anthropic calls it “the natural progression of prompt engineering”.1
Why it matters
Anthropic describes context rot: as the number of tokens in the context window grows, the model’s ability to recall information from it decreases. That makes context a finite resource. Their guiding principle is to find “the smallest possible set of high-signal tokens” that makes the desired outcome likely.1
Context engineering in coding tools
- Instruction files: CLAUDE.md, AGENTS.md and Cursor rules put stable project knowledge in front of the agent every session.23
- Scoped rules: Cursor can apply a rule only when matching files are involved, keeping unrelated instructions out.3
- Tools instead of pasted data: MCP lets an agent fetch what it needs on demand.
Prompt engineering vs context engineering
Prompt engineering is writing and organising instructions. Context engineering covers everything else that lands in the window as well.1 See prompt engineering for coding.
Footnotes
Tools mentioned
- Claude Code: paid from $20/mo
- Cursor: free plan, paid from $8/mo