Context: the working memory you have to manage
What it is — in one coffee-break
The context window is the model's working memory: everything it can "see" while answering — your instructions, the conversation so far, the documents you attached, the results of tools it just used. Context engineering is deciding what goes into that window, in what order, on every single call. If prompt engineering is how you phrase the instruction, context engineering is designing the whole system that feeds the model the right information at the right time.
It became the defining discipline of applied AI because of a stubborn truth: models don't use their windows evenly. Facts buried in the middle of a long context get missed ("lost in the middle"), irrelevant material actively distracts, and every extra token costs money and latency. A million-token window doesn't repeal any of that — it just gives you more rope.
When you actually need it (and when you don't)
For a chat session, you don't — paste what matters, ask your question. You need context engineering when you build anything that runs repeatedly or acts over multiple steps: an assistant over your knowledge base (what gets retrieved and included?), an agent doing a task (what history does it keep, what does it summarize away?), a pipeline like the one that publishes this site (which stories, in which order, with which instructions?). In each case someone has to decide what enters the window — and if nobody decides, the window fills with noise and quality quietly degrades.
The working rules from practice: put stable content first and variable content last (that's also what makes provider-side caching work); include only what the current step needs; summarize old turns instead of carrying them verbatim; and measure — when output quality drops, the context is the first suspect, not the model.
How to recognize good vs bad implementations
Context (Cx) is where the agent-era leaders separate from the pack in our audits. Claude scores 9.5 — context management is arguably Anthropic's core product idea, from prompt caching to context editing for agents. NotebookLM scores 9 by doing one thing perfectly: keeping the model grounded in exactly the sources you gave it, nothing else. Gemini scores 9 with the largest practical windows. Compare that with single-purpose creative tools (Udio: Cx 5) where you can barely steer the model with any surrounding information at all. The question to ask any vendor: what does your tool put into the model's window, and can I see it? Tools that can't answer are guessing on your behalf.
What this costs
Context is the meter that runs. Input tokens are the biggest line on most AI bills — a bloated 50,000-token context on every call costs 25× a disciplined 2,000-token one, for often worse answers. Good context engineering is the rare practice that cuts cost and improves quality at the same time. Check our Model Pricing calculator with your own daily token volumes to see the difference discipline makes.
Where to see it scored
Cx scores with reasons: Claude (9.5), NotebookLM (9), Gemini (9), Windsurf (8.5). Related lessons: Prompts (the instruction layer) and RAG (the retrieval layer that fills the window).