Fetching from the wire…
Public story · 2026-08-10 · high
Subtask examples drove most of the gain, not the workflow layer, using GPT-5-mini as the teacher model.
Why now: It's part of the August 10 coverage of techniques for running capable AI agents on smaller models.
Agent Memory Distillation lifted a 4-billion-parameter model's AppWorld score by 27.2 points, per a paper posted to arXiv (2608.07169).
The technique splits an agent's memory into three layers instead of one context dump. Workflow memory holds task strategy. Subtask memory holds intermediate behavioral examples. Function memory holds calling conventions and a list of common errors. GPT-5-mini served as the teacher model that generated all three, then the memory got distilled down for smaller models to use.
That split matters for anyone running agents on hardware that can't fit a frontier model. The teacher only has to generate the memory once. After that, a 4B model gets most of the benefit without needing GPT-5-mini in the loop at inference time.
Workflow and subtask memory get injected before the agent starts a task. Function memory works differently. It only fires after a tool call fails, as a reactive fix rather than a standing instruction.
The numbers back up that structure. Beyond the 27.2-point AppWorld gain, the same setup added 11.2 points on BFCL V3 and 3.4 on ToolSandbox. Subtask memory, the middle layer, contributed the most of the three, and 4B models saw the biggest lift of any size tested.
The paper doesn't say what generating the memory costs, or whether the gains hold with a different teacher model.
Concrete behavioral examples beat abstract task strategy for small models here. If that pattern holds under ablation on other benchmarks, giving an agent examples looks like a better default than giving it a plan.
Each link below shares sources, entities, or timing with this story.
Instead of retraining the expensive main model, a single small language model is RL-trained to specialize at each node of a recovery graph covering drift classification, operation detection, risk evaluation and recovery decision (arXiv 2608.14109). Rewards combine rule-based s...
The pattern most agent memory systems use, dumping a retrieved trajectory into context, degrades as traces lengthen and as source-specific values diverge from the target. QCR replaces the dump with a structured memory holding reusable procedures plus bindings, applicability co...
Numbers first, because they're the whole argument. On AppWorld's 168 tasks with DeepSeek-V3.2: ALTK-Evolve hit 89.3% goal completion at 263K tokens per task. ACE hit 80.4% at 634K (IBM Research on HF). Nine points better, 41% of the tokens. On the weaker gpt-oss-120b: 56.0% at...
Three memory strategies across eight models from 30B to 745B on AppWorld's 585 multi-step tasks. Curated retrieval gave gpt-oss-120b +16.1 percentage points on goal completion for 5% more tokens. DeepSeek-V3.2 needed the full guideline set for +9.5pp at a 78% token cost. GLM-5...
Store reusable procedures plus bindings, applicability conditions, and verification requirements instead of the raw trace. That gained 10.7 points of success on WebArena, WorkArena, and AppWorld while cutting online tokens 48.9% (arXiv). Direct trace reuse gets worse as your t...
Chen et al. extend AppWorld into a 516-task user-in-the-loop benchmark across nine simulated apps, injecting ambiguities and constraints that force the agent to ask clarifying questions, request confirmation, or declare a task infeasible (arXiv 2607.20536). Opus 4.7 gets 48.6%...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.