← Latest papers
💬 NLP

Agentic Context Engineering: Evolving Contexts for Self-Improving Language Models

The paper introduces Agentic Context Engineering (ACE), a framework that treats contexts as evolving playbooks to overcome brevity bias and context collapse, enabling self-improving language models to achieve state-of-the-art performance on agent and domain-specific benchmarks through structured, incremental updates without requiring labeled supervision.

Original authors: Qizheng Zhang, Changran Hu, Shubhangi Upasani, Boyuan Ma, Fenglu Hong, Vamsidhar Kamanuru, Jay Rainton, Chen Wu, Mengmeng Ji, Hanchen Li, Urmish Thakker, James Zou, Kunle Olukotun

Published 2026-03-31
📖 5 min read🧠 Deep dive

Original authors: Qizheng Zhang, Changran Hu, Shubhangi Upasani, Boyuan Ma, Fenglu Hong, Vamsidhar Kamanuru, Jay Rainton, Chen Wu, Mengmeng Ji, Hanchen Li, Urmish Thakker, James Zou, Kunle Olukotun

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

The Big Problem: The "Short-Note" Trap

Imagine you are training a brilliant but forgetful intern (the AI) to do a complex job, like managing a bank or running a software company.

In the past, when the intern made a mistake, the boss (the developer) would try to fix it by rewriting the intern's entire instruction manual. But there was a catch: the boss kept trying to make the manual shorter and shorter so it was easy to read.

This caused two big problems:

  1. The "Too Short" Problem: To make the manual short, the boss had to throw away the tiny, specific details that actually mattered (like "always check the date format" or "never trust this specific API"). The manual became a vague summary like "Be careful," which wasn't helpful.
  2. The "Memory Collapse" Problem: Every time the boss rewrote the manual, the intern would accidentally delete old, useful notes while trying to summarize new ones. After a few weeks, the manual was so short and empty that the intern was worse at their job than when they started.

The Solution: ACE (The "Living Playbook")

The authors of this paper created a new system called ACE (Agentic Context Engineering). Instead of rewriting the whole manual every time, ACE treats the instructions like a growing, living playbook (like a sports coach's strategy binder or a chef's recipe book).

Here is how ACE works, using a Kitchen Analogy:

Imagine a head chef (the AI) trying to cook a perfect meal.

1. The Three Specialized Roles

Instead of one person trying to do everything, ACE splits the work into three specialized roles:

  • The Generator (The Cook): This is the AI actually doing the task. It tries to solve the problem (cook the meal). If it burns the toast, it notes what happened.
  • The Reflector (The Food Critic): This is a smart observer. It looks at the Cook's mistakes and successes. Instead of just saying "You failed," it writes a specific note: "The toast burned because the oven was set to 'Broil' instead of 'Bake'. Next time, check the dial."
  • The Curator (The Librarian): This is the organizer. It takes the Critic's specific notes and adds them to the Playbook. It doesn't rewrite the whole book; it just adds a new sticky note or a new bullet point to the existing list.

2. The "Delta" Update (Adding Sticky Notes)

Old methods tried to rewrite the whole Playbook from scratch every time. ACE is different. It uses "Delta Updates."

Think of it like a Google Doc where you don't delete the whole page to fix a typo. You just add a small comment or a new bullet point.

  • Old Way: "Here is the new manual. It is 2 pages long." (The old 50 pages are gone).
  • ACE Way: "Here is the old manual. I am adding one new rule: 'Check the oven dial.'"

This prevents the "Memory Collapse" because the old, detailed rules stay safe in the book, and new insights are simply added on top.

3. The "Grow and Refine" Strategy

As the AI solves more problems, the Playbook gets bigger. But a giant book is hard to read. So, ACE has a "Refinement" step.

  • If the Playbook gets too messy, the Curator looks for duplicate notes (e.g., "Check the oven" and "Make sure the oven is on") and merges them.
  • It keeps the book comprehensive (full of details) but organized (easy to find things).

Why This Matters (The Results)

The paper tested this system on two main things:

  1. AI Agents: Giving AI the ability to use tools (like sending emails or booking flights).
  2. Specialized Knowledge: Like financial analysis or medical diagnosis.

The Results were amazing:

  • Better Performance: The AI using ACE got significantly higher scores (about 10% better) than the best previous methods.
  • Cheaper & Faster: Because ACE doesn't have to rewrite the whole manual every time, it saves a massive amount of computing power and time.
  • No Teacher Needed: ACE can learn just by looking at whether the AI succeeded or failed in the real world. It doesn't need a human to grade its homework.
  • Beating the Giants: On a famous test called "AppWorld," an open-source AI using ACE performed as well as (or better than) a top-tier, expensive, closed-source AI system from a major tech company.

The Takeaway

ACE changes the game from "Summarizing" to "Accumulating."

Instead of forcing the AI to forget details to be concise, ACE lets the AI build a massive, detailed library of experience. It treats the AI's memory not as a short note on a napkin, but as a growing encyclopedia that gets smarter, more detailed, and more reliable every single day, without ever losing the important stuff.

It's the difference between trying to remember a whole book by reciting a one-sentence summary versus having a well-organized library where you can look up exactly what you need, right when you need it.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →