Context Engineering for AI Agents

For three years the dominant assumption was that better foundation models would unlock production agents. That assumption has quietly collapsed. The new consensus, articulated most directly by Harrison Chase, is that capability is no longer the limiter — context is. LangChain's central claim is that most of the time when an agent is not performing reliably the underlying cause is that the appropriate context, instructions and tools have not been communicated to the model ^[2]. Anthropic's Applied AI team frames the same shift differently: context must be treated as a finite resource with diminishing marginal returns, and the engineering job is to surface the smallest possible set of high-signal tokens rather than to flood the window ^[1].

This reframing has practical teeth. Prompt engineering — the message-level instruction craft that dominated 2022-2024 and briefly carried six-figure salaries — is now treated as a subset of a broader discipline ^[10]. Context engineering covers everything that ends up in the model's view across a multi-turn agent run: system prompts, tool definitions, retrieved documents, memory, prior tool results, and the running message history. As Chase puts it on the Sequoia podcast, agent context is non-deterministic — you don't actually know what the context at step 14 will be because there's 13 steps before that that could pull arbitrary things in ^[3]. That non-determinism is why traces, not source code, are becoming the unit of debugging.

The field now has a shared vocabulary for failure. Drew Breunig's June 2025 essay names four modes: poisoning (a hallucination enters context and gets repeatedly referenced), distraction (the model fixates on its own history instead of training), confusion (irrelevant tokens skew the answer), and clash (parts of context contradict each other) ^[4]. The vocabulary stuck because the underlying empirical picture is unambiguous.

The numbers are not subtle. Chroma Research's 2025 study tested 18 frontier LLMs and found every single one degrades as input length increases — performance grows increasingly unreliable as input length grows ^[5]. Databricks measured Llama 3.1 405b correctness beginning to drop around 32,000 tokens ^[5]. Google DeepMind's own Gemini 2.5 technical report acknowledges context distraction past 100,000 tokens, with the agent favoring repeating actions over novel planning ^[4]. Microsoft and Salesforce found a 39% average performance drop when prompts were sharded across multiple conversational turns, with OpenAI's o3 falling from 98.1 to 64.1 on affected benchmarks ^[4]. And the most actionable data point of all: on the Berkeley Function-Calling Leaderboard, a quantized Llama 3.1 8b failed with 46 tools available but succeeded with 19 tools in the same 16K window — a roughly 3x accuracy swing driven entirely by pruning tool surface area ^[4]. Bigger context windows are not free capability; they are a budget with steep marginal cost.

Anthropic has aligned more of its platform with context engineering than any other lab. The Model Context Protocol, launched in November 2024, became the substrate — and the strategic payoff arrived when both OpenAI and Google adopted MCP across their stacks, turning a single-vendor protocol into the de facto cross-vendor standard ^[7]. MCP downloads grew from 2M monthly at launch to 97M by March 2026, a 4,750% expansion in 16 months ^[7].

In January 2026, Anthropic followed by shipping three native context primitives on the Claude Developer Platform. Compaction is a whole-transcript operation that flattens user messages, assistant messages, tool calls, tool results, and even prior compaction blocks into a summary ^[6], with a server-side minimum trigger of 50K input tokens. Tool-result clearing fires by default at 100K tokens and keeps the last three tool uses ^[6]. A memory tool gives agents persistent external storage. These are no longer harness-level concerns built by application developers — they are first-class API features.

The second pillar is Agent Skills, which lean on progressive disclosure: Claude loads information only as needed ^[9]. Skill metadata is loaded at startup; the full skill body is pulled in on demand. That is just-in-time retrieval lifted from the developer best-practices essay — agents maintain lightweight identifiers (file paths, stored queries, web links) and use these references to dynamically load data into context at runtime using tools ^[1]— and burned into the platform.

Across the practitioner videos and developer forums tracked for this cluster, an unusual amount of agreement has formed on what production context engineering actually looks like — and notably, it does not look like a longer prompt or a bigger model. The Manus co-founder Yichao Ji, in conversation with LangChain, frames the playbook as three operations: context reduction via dual-form tool results (a full version plus a compact one), context offloading via layered action spaces with filesystem-backed state, and context isolation via narrowly-scoped sub-agents with constrained-decoding inter-agent comms. Human Layer founder Dexter Horthy, in his YC Root Access deep-dive, makes a complementary case: subagents earn their cost as context-isolation primitives, not as parallelism primitives, and frequent intentional compaction is the difference between an agent that survives a real codebase and one that fails on its second tool call.

Developer community discussion on X and Reddit lands on the same shape. The dominant frustration is with naive dump-everything-into-RAG patterns; the dominant enthusiasm is for purpose-built context systems that prune what an agent sees rather than expand it. Anthropic's Agent Skills release was framed in the same community discussion as Anthropic effectively open-sourcing its production playbook for context engineering. What is notable is that this playbook is not Anthropic-specific — it is the same vocabulary practitioners now use regardless of which model they target, which makes the playbook itself the durable asset. The strategic stakes are large: fewer than one in four organizations experimenting with AI agents have managed to scale them to production ^[8], and the converging consensus is that closing that gap runs through context discipline, not model upgrades.