---
title: "Context Engineering 2.0: what the paper says"
description: "Context Engineering 2.0 is an October 2025 paper arguing context engineering is decades old: we are in era 2.0, where agents read plain language, 3.0 is next."
image: "https://bombos.ai/assets/og-en-v2.png"
---

# What is Context Engineering 2.0?

Short answer

"Context Engineering 2.0: The Context of Context Engineering" is an October 2025 arXiv paper by Qishuo Hua, Pengfei Liu and seven co-authors. It argues context engineering is over twenty years old and splits it into eras: 1.0 (1990s to 2020, sensors and rules), 2.0 (from 2020, LLM agents that read natural language), and a future 3.0 and 4.0. Its core idea: context engineering is reducing entropy.

*Piet Baudoin · published November 17, 2026 · November 17, 2026*

## The main claim: this is not new

Most writing on context engineering dates it to 2025, when the term became popular for AI agents. The paper argues the problem is older. Ever since computers had to respond to people, someone had to decide what information about the situation the system could use. The paper builds its definition on a classic one from human-computer interaction research: context is “any information that can be used to characterize the situation of entities that are considered relevant” to an interaction. Context engineering then is “the systematic process of designing and optimizing context collection, storage, management, and usage.”

## The four eras

| Era | Period | What the machine can do | Who does the context work |
| --- | --- | --- | --- |
| 1.0 Primitive computation | 1990s to 2020 | Structured input, sensor signals, rules | Designers act as “intention translators” |
| 2.0 Agent-centric intelligence | 2020 to now, starting with GPT-3 | Reads natural language, handles some ambiguity | Developers and users curate prompts, memory, tools |
| 3.0 Human-level intelligence | Future | Reads high-entropy signals such as emotion and social cues | Mostly the system |
| 4.0 Superhuman intelligence | Speculative | Builds context itself and surfaces needs people have not stated | The machine |

The thread through all four is what the paper calls entropy reduction. People fill in missing context without noticing; machines cannot. So someone has to turn high-entropy intent into low-entropy, machine-usable form. The smarter the machine, the less of that work falls on the human. Read this way, “2.0” is not a version of a tool but a point in that curve.

## The design considerations

The paper groups the practical part into four stages:

1.  **Collection and storage.** Two principles: minimal sufficiency, “The context value lies in sufficiency, not volume”, and semantic continuity, keeping meaning rather than raw data.
2.  **Management.** Timestamps, tagging, hierarchical notes, layered memory, isolating sub-agents and lightweight references instead of full content. Short-term memory is context that is relevant now; long-term memory is context important enough to be abstracted and kept, with a transfer step between them.
3.  **Usage.** Selecting what to load by semantic relevance, logical dependency, recency, frequency and user preference, which the paper calls “attention before attention”. Sharing context between agents, within one system through prompts, fixed-schema messages or shared memory, and across systems through adapters, shared formats, readable summaries or vectors.
4.  **Self-baking.** The agent digests its own history into lasting structures: natural-language summaries, facts in a fixed schema, hierarchical memory or compressed embeddings. Each trades off structure, readability and upkeep.

It ends with open problems: storage, degradation on long inputs, errors that spread through memory, evaluation, and a proposed “Semantic Operating System for Context” in which context “is actively managed and evolved.”

## The common misunderstanding

The title invites the reading that 2.0 is a new method that replaces something called 1.0, the way people speak of “prompt engineering 2.0”. It is not. The paper offers no new technique, benchmark or code. Its value is a vocabulary and a frame: what counts as context, why it costs effort, and which choices every system makes about collecting, storing, selecting and sharing it. If you want the techniques, the July 2025 survey by Lingrui Mei and colleagues is the broader map, and posts such as Anthropic’s are more hands-on; see [What does Anthropic say about context engineering?](https://bombos.ai/en/questions/context-engineering/what-does-anthropic-say-about-context-engineering/)

## What this means for a team

Two ideas from the paper translate directly to a team using several AI tools. First, cross-system sharing: the paper lists the trade-offs between schemas (precise but needing coordination), summaries (flexible but harder to parse) and vectors (compact but hard to inspect). That is the choice a team faces when knowledge has to move between ChatGPT, Claude and a coding agent. Second, self-baking: a team whose AI only recalls old chats keeps repeating itself; one whose corrections become lasting rules accumulates knowledge. For the agent-level version of that loop, see [What is agentic context engineering (ACE)?](https://bombos.ai/en/questions/context-engineering/what-is-agentic-context-engineering/) and [What is a memory OS for AI agents?](https://bombos.ai/en/questions/ai-memory/what-is-a-memory-os-for-ai-agents/)

## Where Bombos fits

Bombos does the cross-system part for a team: one plugin that gives every AI tool the team uses the same memory, with team knowledge, learned rules and what is already in mail, documents and repos. Corrections can be kept as learned rules for later work, which is close to what the paper calls self-baking, and you can see what each answer rests on. It runs in our cloud or on your own server.

## Related questions

Who wrote Context Engineering 2.0?

Qishuo Hua, Lyumanshan Ye, Dayuan Fu, Yang Xiao, Xiaojie Cai, Yunze Wu, Jifan Lin, Junfei Wang and Pengfei Liu. It was submitted to arXiv on October 30, 2025 as 2510.26493.

Is Context Engineering 2.0 a new technique or framework?

No. It is a conceptual paper: a definition, a history and design considerations. It does not ship code or a benchmark.

What is self-baking in the paper?

The paper's term for an agent digesting its own context into lasting knowledge structures, such as summaries, extracted facts or hierarchical memory. Its line: "Without self-baking, agents simply recall; with it, they accumulate knowledge."

How is it different from "A Survey of Context Engineering for Large Language Models"?

The survey by Lingrui Mei and colleagues (July 2025) maps techniques from over 1,400 papers. Context Engineering 2.0 is shorter and conceptual: it asks what context is and how the discipline evolved.

## Sources

1.  [Context Engineering 2.0: The Context of Context Engineering (arXiv 2510.26493)](https://arxiv.org/abs/2510.26493)
2.  [Context Engineering 2.0, full text (arXiv HTML)](https://arxiv.org/html/2510.26493v1)
3.  [A Survey of Context Engineering for Large Language Models (arXiv 2507.13334)](https://arxiv.org/abs/2507.13334)

## What does your AI forget?

1.  01You tell us which AI you use and where it keeps starting over.
2.  02We show what a shared memory changes there, on your own examples.
3.  03You keep the plan, with or without Bombos.

![Piet Baudoin](https://bombos.ai/assets/team/piet-klein.jpg)

**Piet Baudoin**You talk to Piet, from the Bombos teamDutch team from Utrecht and Nijmegen · data in Europe

## More questions about Context engineering

-   [How does LangChain approach context engineering?](https://bombos.ai/en/questions/context-engineering/how-does-langchain-approach-context-engineering/)
-   [What is agentic context engineering (ACE)?](https://bombos.ai/en/questions/context-engineering/what-is-agentic-context-engineering/)
-   [What is advanced context engineering for coding agents?](https://bombos.ai/en/questions/context-engineering/advanced-context-engineering-for-coding-agents/)
-   [How do you do context engineering for multi-agent systems?](https://bombos.ai/en/questions/context-engineering/context-engineering-for-multi-agent-systems/)
-   [What is the difference between context engineering and prompt engineering?](https://bombos.ai/en/questions/context-engineering/context-engineering-vs-prompt-engineering/)
-   [What is context rot and how do you avoid it?](https://bombos.ai/en/questions/context-engineering/what-is-context-rot/)
-   [What is Google's context engineering whitepaper on sessions and memory?](https://bombos.ai/en/questions/context-engineering/what-is-googles-context-engineering-whitepaper/)
-   [What is harness engineering, and how does it differ from prompt and context engineering?](https://bombos.ai/en/questions/context-engineering/what-is-harness-engineering/)

[All questions about Context engineering →](https://bombos.ai/en/questions/context-engineering/)


---

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://bombos.ai/#organization","name":"Bombos","url":"https://bombos.ai/","logo":"https://bombos.ai/assets/bombos-bee.png","description":"Bombos is the memory layer under every AI your team uses. One shared memory for Claude, ChatGPT, Copilot, Cursor and your own agents, that learns how you work.","sameAs":["https://www.linkedin.com/company/bombos-ai","https://www.youtube.com/@truebombos","https://www.instagram.com/truebombos/","https://bsky.app/profile/bombostrue.bsky.social","https://www.threads.com/@truebombos","https://mastodon.social/@Bombos","https://www.tiktok.com/@truebombos","https://t.me/truebombos","https://www.pinterest.com/truebombos/","https://github.com/bombos-ai","https://linktr.ee/bombos.ai","https://bombosai.substack.com","https://hashnode.com/@bombosai","https://hackernoon.com/u/bombos","https://dev.to/bombos"],"email":"info@bombos.ai","areaServed":["NL","Europe"],"knowsLanguage":["nl","en"],"contactPoint":{"@type":"ContactPoint","email":"info@bombos.ai","contactType":"sales","url":"https://bombos.ai/en/contact/","availableLanguage":["nl","en"]}},{"@type":"WebSite","@id":"https://bombos.ai/#website","name":"Bombos","url":"https://bombos.ai/","inLanguage":["nl-NL","en"],"publisher":{"@id":"https://bombos.ai/#organization"}}]}

{"@context":"https://schema.org","@type":"Article","headline":"What is Context Engineering 2.0?","description":"Context Engineering 2.0 is an October 2025 paper arguing context engineering is decades old: we are in era 2.0, where agents read plain language, 3.0 is next.","abstract":"\"Context Engineering 2.0: The Context of Context Engineering\" is an October 2025 arXiv paper by Qishuo Hua, Pengfei Liu and seven co-authors. It argues context engineering is over twenty years old and splits it into eras: 1.0 (1990s to 2020, sensors and rules), 2.0 (from 2020, LLM agents that read natural language), and a future 3.0 and 4.0. Its core idea: context engineering is reducing entropy.","datePublished":"2026-11-17T00:00:00.000Z","dateModified":"2026-11-17T00:00:00.000Z","author":{"@type":"Person","name":"Piet Baudoin"},"publisher":{"@type":"Organization","@id":"https://bombos.ai/#organization","name":"Bombos","logo":{"@type":"ImageObject","url":"https://bombos.ai/assets/bombos-bee.png"}},"image":"https://bombos.ai/assets/og-en-v2.png","mainEntityOfPage":"https://bombos.ai/en/questions/context-engineering/what-is-context-engineering-2-0/","inLanguage":"en-US","isPartOf":{"@type":"CollectionPage","name":"Context engineering","url":"https://bombos.ai/en/questions/context-engineering/"},"citation":[{"@type":"CreativeWork","name":"Context Engineering 2.0: The Context of Context Engineering (arXiv 2510.26493)","url":"https://arxiv.org/abs/2510.26493"},{"@type":"CreativeWork","name":"Context Engineering 2.0, full text (arXiv HTML)","url":"https://arxiv.org/html/2510.26493v1"},{"@type":"CreativeWork","name":"A Survey of Context Engineering for Large Language Models (arXiv 2507.13334)","url":"https://arxiv.org/abs/2507.13334"}]}

{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Bombos","item":"https://bombos.ai/en/"},{"@type":"ListItem","position":2,"name":"Questions","item":"https://bombos.ai/en/questions/"},{"@type":"ListItem","position":3,"name":"Context engineering","item":"https://bombos.ai/en/questions/context-engineering/"},{"@type":"ListItem","position":4,"name":"What is Context Engineering 2.0?","item":"https://bombos.ai/en/questions/context-engineering/what-is-context-engineering-2-0/"}]}

{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Who wrote Context Engineering 2.0?","acceptedAnswer":{"@type":"Answer","text":"Qishuo Hua, Lyumanshan Ye, Dayuan Fu, Yang Xiao, Xiaojie Cai, Yunze Wu, Jifan Lin, Junfei Wang and Pengfei Liu. It was submitted to arXiv on October 30, 2025 as 2510.26493."}},{"@type":"Question","name":"Is Context Engineering 2.0 a new technique or framework?","acceptedAnswer":{"@type":"Answer","text":"No. It is a conceptual paper: a definition, a history and design considerations. It does not ship code or a benchmark."}},{"@type":"Question","name":"What is self-baking in the paper?","acceptedAnswer":{"@type":"Answer","text":"The paper's term for an agent digesting its own context into lasting knowledge structures, such as summaries, extracted facts or hierarchical memory. Its line: \"Without self-baking, agents simply recall; with it, they accumulate knowledge.\""}},{"@type":"Question","name":"How is it different from \"A Survey of Context Engineering for Large Language Models\"?","acceptedAnswer":{"@type":"Answer","text":"The survey by Lingrui Mei and colleagues (July 2025) maps techniques from over 1,400 papers. Context Engineering 2.0 is shorter and conceptual: it asks what context is and how the discipline evolved."}}]}
```
