INQUIRING LINE

AI agents that save reusable mini-skills — not full solutions — improve dramatically, and the gains grow as tasks get stranger.

Can workflow memory compound reusable skills into measurable success improvements?

This explores whether agents that store and reuse the routines they discover — 'workflow memory' — actually post measurable performance gains, and what makes that compounding work.


This explores whether agents that store and reuse the routines they discover — 'workflow memory' — actually post measurable performance gains, and what makes that compounding work. The corpus says yes, and unusually for this field, with hard numbers. Agent Workflow Memory extracts reusable sub-task routines (not whole-task scripts), strips out the example-specific values, and stacks them hierarchically — yielding a 24.6% relative gain on Mind2Web and 51.1% on WebArena, with the gains *widening* as the gap between training and test tasks grows Can agents learn reusable sub-task routines from past experience?. That last detail is the interesting part: the more novel the situation, the more a library of abstracted routines pays off, because reusable skills generalize where memorized full solutions don't.

The deeper claim underneath the numbers is that reliability comes from *externalizing* cognition rather than scaling the model. One synthesis frames reliable agents as offloading three burdens — memory, skills, and protocols — into a harness layer so the model stops re-solving the same problems Where does agent reliability actually come from?. VOYAGER is the canonical demonstration: an embedding-indexed library of executable skills, with complex skills composed from simpler ones, lets an agent learn continuously and — crucially — avoid the catastrophic forgetting that weight-update methods suffer Can agents learn new skills without forgetting old ones?. So 'compounding' isn't a metaphor; it's literal composition of stored procedures into bigger ones.

But a skill library only compounds if it's *curated*, not just accumulated. SkillOS shows that separating a trainable curator from a frozen executor shifts a repository away from generic, verbose entries toward actionable execution logic and cross-task meta-strategies — and the trained curator transfers across different model backbones Can a separate trained curator improve skill libraries better than frozen agents?. SkillRL adds a sharp twist on *what* to store: treat successes as concrete demonstrations and failures as abstracted lessons. That asymmetry hits state-of-the-art while using far less context than dumping everything in uniformly Should successful and failed episodes be processed differently?. The implication is that naive 'remember everything' memory degrades, while differentiated memory improves both efficiency and the policy.

There's a counterweight worth knowing about, because it's where the compounding story breaks. In long, multi-turn workflows, agents fail not from missing knowledge but from *weak memory control* — transcript replay and retrieval lack gating, so errors and constraint drift accumulate; a bounded, schema-governed committed state fixes it Can agents fail from weak memory control rather than missing knowledge?. The stakes are concrete: frontier models silently corrupt ~25% of document content across extended relay tasks, with errors compounding without plateauing through 50 round-trips Do frontier LLMs silently corrupt documents in long workflows?. So memory compounds in both directions — good routines compound into measurable wins, but ungated memory compounds errors just as reliably.

The thing you might not have known you wanted: the same mechanism — accumulation across a workflow — is what drives both the 51% gains and the 25% corruption. The difference between them is entirely *governance*: abstraction (drop example-specific values), composition (build complex from simple), curation (a trained editor, not a junk drawer), and gating (a bounded committed state). Memory doesn't help because it's memory; it helps when something decides what's worth keeping.


Sources 7 notes

Can agents learn reusable sub-task routines from past experience?

Agent Workflow Memory induces sub-task routines at finer granularity than full tasks, abstracts example-specific values, and compounds them hierarchically. This produces 24.6% relative gain on Mind2Web and 51.1% on WebArena, with larger gains as train-test gaps widen.

Where does agent reliability actually come from?

Research shows reliable LLM agents externalize three cognitive burdens—memory (state persistence), skills (procedural components), and protocols (structured interaction)—into a harness layer rather than relying on model scale alone. The harness unifies these externalities and eliminates the need for the model to solve the same problems repeatedly.

Can agents learn new skills without forgetting old ones?

VOYAGER demonstrates that storing executable skills in an embedding-indexed library and composing complex skills from simpler ones allows agents to learn continuously while avoiding the forgetting that occurs with weight-update-based methods. Environmental feedback refines skills while an automatic curriculum drives continual exploration.

Can a separate trained curator improve skill libraries better than frozen agents?

SkillOS shows that separating a trainable curator from a frozen executor, grouped by task streams, causes skill repositories to shift from generic verbose additions toward actionable execution logic and cross-task meta-strategies. The trained curator generalizes across different executor backbones and domains.

Should successful and failed episodes be processed differently?

SkillRL demonstrates that treating successful episodes as concrete demonstrations and failures as abstracted lessons achieves state-of-the-art performance on complex tasks while using substantially less context than uniform approaches. The asymmetry mirrors human expert reasoning and avoids the degradation seen in uniform consolidation methods.

Show all 7 sources
Can agents fail from weak memory control rather than missing knowledge?

Agent performance degrades in long workflows because transcript replay and retrieval-based memory lack gating mechanisms. A bounded, schema-governed committed state that separates artifact recall from permanent memory write prevents error accumulation and constraint drift.

Do frontier LLMs silently corrupt documents in long workflows?

Testing 19 models across 52 domains shows even advanced systems degrade documents by ~25% over extended relay tasks, with errors compounding silently without plateauing through 50 round-trips.

Papers this line draws on 8

The research behind the notes this line reads — ranked by how closely each paper relates.

Research prompt for your LLMexpand ↓

Copy into ChatGPT or Claude to take this line of inquiry further — it asks the model to find newer work and re-test which earlier constraints still hold.

You are a research analyst assessing a still-open question: can workflow memory compound reusable skills into measurable, durable success improvements — and under what governance?

What a curated library found — and when (dated claims, not current truth; these span ~2023–2026):
- Agent Workflow Memory extracts abstracted sub-task routines (values stripped) and stacks them hierarchically: +24.6% relative on Mind2Web, +51.1% on WebArena, gains widening as train/test tasks diverge (~2024).
- Reliability comes from externalizing memory, skills, and protocols into a harness so the model stops re-solving problems; VOYAGER-style composable skill libraries avoid catastrophic forgetting (~2026 review).
- Curation beats accumulation: a trained curator decoupled from a frozen executor yields actionable, cross-task entries that transfer across backbones (~2026, SkillOS).
- Store asymmetrically — successes as demonstrations, failures as abstracted lessons — hits SOTA with far less context (~2026).
- Counterweight: ungated memory compounds errors; frontier models silently corrupt ~25% of document content over 50 relay round-trips, without plateauing (~2026).

Anchor papers (verify; mind their dates): Agent Workflow Memory (arXiv:2409.07429, 2024); SkillOS: Learning Skill Curation (arXiv:2605.06614, 2026); LLMs Corrupt Your Documents When You Delegate (arXiv:2604.15597, 2026); Externalization in LLM Agents (arXiv:2604.08224, 2026).

Your task:
(1) RE-TEST EACH CONSTRAINT. For every finding, judge whether newer models, training, tooling, orchestration (memory, caching, multi-agent), or evaluation has RELAXED or OVERTURNED it. Separate the durable question (does memory compound?) from perishable limits (e.g., the 25% corruption, the specific WebArena gains); cite what resolved each, and say plainly where a constraint still holds.
(2) Surface the strongest contradicting or superseding work from the last ~6 months.
(3) Propose 2 research questions that ASSUME the regime has moved.

Cite arXiv IDs; flag anything you cannot ground in a real paper.