Context Engineering for Reliable AI Agents

For three years after ChatGPT's launch, prompt engineering was the named profession of the LLM era — a discipline of phrasing, role-play, and clever instructions aimed at a single inference call. The shift announced by Anthropic's Applied AI team in late September 2025 reframes that work as a special case of something larger. Their definition is deliberately mechanical: context is 'the set of tokens included when sampling from a large-language model,' and the engineer's job is to find 'the smallest possible set of high-signal tokens that maximize the likelihood of desired outcome.' Prompts are still in there. They are just no longer the unit of work.

The mechanism behind the displacement is that context is finite, attention is quadratic, and long contexts decay. Anthropic notes that LLMs 'like humans, lose focus or experience confusion at a certain point,' and Elastic's measurements show accuracy degrading around 32,000 tokens for some models — a phenomenon now widely called context rot. Once you accept that more context can hurt, prompt engineering's instinct to stuff the window with examples and instructions becomes actively harmful. Philipp Schmid's now-quoted line — 'most agent failures are not model failures anymore, they are context failures' — is the field's clearest statement of why the throne changed hands. The model is no longer the bottleneck; what you put in front of it is.

If context engineering is the discipline, the past four months have produced its first widely accepted abstractions — and they look nothing like prompts. LangChain's November filesystem post and the December arXiv paper 'Everything is Context' both converge on the same primitive: an agentic filesystem, 'a single interface through which an agent can flexibly store, retrieve, and update an infinite amount of context.' Persistent files replace the ephemeral prompt as the seat of agent memory. Anthropic's harness essay sits alongside this, arguing that since 'each new session begins with no memory of what came before,' the surrounding scaffolding — tool definitions, environment, retrieval policies — has to do the remembering. HumanLayer's coinage of 'harness engineering' formalizes the practice as a permanent fix loop: every agent mistake gets engineered out of the harness so the agent never makes it again.

The third primitive is structural: sub-agents as context firewalls. Isolating a noisy task — a long search, a brittle parse — inside a child agent prevents intermediate junk from polluting the parent thread, an idea LangChain's developer-facing taxonomy (write, select, compress, isolate) puts at the same level as retrieval and compression. Manus's framework rebuilds, repeated four times, are essentially an evolution of which primitives bear weight: 'you can't reliably predict which observation might become critical ten steps later,' so structure must absorb the unpredictability that prompts cannot. These abstractions are the real artefact of the rebrand. Calling something 'context engineering' is just vocabulary; treating filesystems, harnesses, and isolated sub-agents as first-class building blocks is the actual change.

Vocabulary shifts only matter when payroll moves with them, and on this score the case is unusually clear. Cognizant has committed to deploying 1,000 dedicated context engineers over the next year — a single-vendor headcount number large enough to redefine the role's labor market. The justification is operational, not aspirational: one of Cognizant's wealth-management clients reported a 40% reduction in advisor prep time, the kind of number that lets a services firm price a practice. Gartner's July 2025 declaration that 'context engineering is in, prompt engineering is out' gave enterprise buyers analyst cover to relabel their AI programs.

The demand-side reasoning is in Atlan co-founder Prukalpa Sankar's framing: '83% of organizations are actively experimenting with AI, yet only 17% are able to drive value,' with data quality, governance, and disconnected systems acting as the major barriers. That 83/17 gap is exactly the territory context engineering claims — and it explains why the role is forming inside large enterprises rather than at frontier-model labs. Frontier models have plateaued enough that further capability gains come from what surrounds them; the marginal hire is no longer a researcher but someone who can wire retrieval, memory, governance, and tooling into a coherent context substrate. When a Box CEO calls context engineering 'the long pole in the tent for AI Agents adoption' on X, what he is really describing is a budget line that did not exist a year ago and now does.

The contrarian read deserves a fair hearing because it is internally consistent. On Reddit, an r/AIMemory thread titled 'Is Context Engineering the new hype?' captured a mixed reception, with a vocal minority arguing the term is little more than rebranded prompt engineering — the same activity (curating what goes into the model) under a more legitimate-sounding name. A parallel critique in the same community holds that 'AI memory engineering' is the more honest framing, because what builders actually need is durable memory across sessions, not just better single-shot context curation. From this angle, the filesystem and harness vocabulary is a halfway house: it admits prompts are not enough, but stops short of treating memory as the real primitive.

The steelmanned counter is that the displacement is not about a word swap but about scope. Prompt engineering optimizes a single call; context engineering optimizes an ongoing process across tools, retrieval, sub-agents, and persistent files — what KDnuggets called the move from teaching machines to speak to 'building the worlds they think within.' Manus's four framework rebuilds, Anthropic's pair of essays, and the academic formalization in 'Everything is Context' are all evidence that practitioners are doing materially different work, not renaming old work. The honest answer is probably that both readings have weight: the term 'context engineering' is loose enough to absorb prompt-craft as a subset, which is why the Reddit critique lands; and the abstractions underneath it — filesystems, harnesses, context firewalls — are concrete enough that calling the whole thing rebrand undersells what changed. The memory-engineering camp may simply be early to the next rename.