Agent runtime

Context Engineering

The discipline of deciding what an AI model sees on every call — instructions, retrieved data, memory, tool definitions, examples — and how to assemble them reliably as the workflow grows.

Operating principle

Production AI is not a prompt. It is a system of context, tools, permissions, traces, evals, and feedback loops.

What it is

Context engineering is the work of building the prompt the model actually sees. It's not 'prompt engineering' as one-off wording tuning — it's the systematic discipline of assembling instructions, retrieved context, memory, examples, tool definitions, and conversation history into a coherent input on every model call. It's where most production AI quality is decided.

Why it matters

The model is the same; the system around the model is what makes one team's AI feel sharp and another team's feel scattered. Context engineering is the cluster of decisions that determines whether the model has what it needs to give a good answer — retrieval design, chunk strategy, memory shape, prompt structure, example selection, tool surface.

How it works

Components: a stable system prompt (personality, scope, refusal patterns), retrieved context from a governed source graph, working memory and relevant episodic memory, examples selected by similarity to the current task, scoped tool definitions, and the user input itself. Each is its own slot in the context budget; each is testable; each is versioned.

Related resources