Plain-language explainer
Context engineering, explained
What is context engineering, and how is it different from prompt engineering?
Context engineering is deciding everything the model gets to see for a task, not just the wording of one prompt. A modern system assembles its context from many sources: instructions, the user's request, retrieved documents, past turns, tool results, memory, and files. The model can only reason about what is in that window, and the window is a limited budget. Good context engineering puts the right information in, leaves noise out, and orders it well. It is the discipline that replaced 'prompt tips' once systems got complex.
Do not just read it. Operate the mechanism yourself in a short interactive lesson.
See it work: Context engineering: cut the noise →Free, no code, no signup.
What people get wrong
- It is just writing a better prompt. The prompt is one input; context engineering manages all of them.
- More context is always better. A full, noisy window degrades answers and raises cost and latency.
- The model remembers your conversation. It only sees what is placed back into the context each turn.
Where you see it in real products
- Assistants assemble instructions, history, and retrieved docs into each request.
- Agents compress and prune context so a long task still fits the budget.
- RAG is one part of context engineering: choosing which documents make the cut.
Related explainers
Part of See How AI Works, a free interactive course, where you learn how modern AI works by operating it, not watching videos.