claude-news
paperEmergent Mind·25 Oct 2026

Are Self-Evolving Agents Continual Learners?

Tests whether self-evolving agents like ReasoningBank, GEPA and Meta-Harness learn new tasks without forgetting old ones.

Depth 4/5Score 4.56

Abstract

The paper assesses three self-evolving methods (ReasoningBank, GEPA, and Meta-Harness) to determine if they can continually learn new tasks while preserving previously learned skills, using metrics like terminal advantage and average advantage. GEPA achieves the highest plasticity but incurs the most severe stability loss, indicating a trade-off between adapting to new tasks and retaining previous knowledge The study shows that self-evolution can improve performance, but current methods fail to balance plasticity and stability effectively, leading to significant interference and forgetting. Find the latest research on continual learning in self-evolving agents? Research question and conceptual framework “Are Self-Evolving Agents Continual Learners?” examines whether nonparametric self-evolving LLM agents satisfy the central requirement of continual learning: acquiring competence on incoming task families while preserving performance on previously learned and not-yet-seen families (2610.25858). The paper focuses on agents whose model parameters remain frozen and whose adaptation occurs exclusively through the harness: system prompts, external memories, skill files, and controller code. This formulation is important because self-evolution operates at the timescale of deployment. Unlike gradient-based continual learning, which requires parameter updates and often substantial data or computation, harness-level adaptation can occur after individual episodes. The paper formalizes an evolver ff that maps the current harness and accumulated experience to a new harness. The resulting agent policy is therefore determined by the fixed LLM and a changing nonparametric state. The authors distinguish two adaptation paradigms. Self-modification rewrites globally shared artifacts, as in GEPA and Meta-Harness. Experience augmentation stores reflections or trajectories externally and retrieves them at inference time, as in ReasoningBank. Both mechanisms can improve performance on the task that generated the update, but they expose different interference mechanisms when the task distribution changes. The study defines continual learning over task families and evaluates the complete policy sequence rather than only the final checkpoint. This is a consequential methodological choice: a method that eventually relearns a task after damaging it may obtain a reasonable terminal score while performing poorly over much of the deployment horizon. Performance is therefore …

Explained

What happened

A paper (arXiv 2610.25858) tests whether self-evolving agents, ones that improve by rewriting their own harness (prompts, memory, skills) while model weights stay frozen, can learn continually: keep improving on new tasks without forgetting old ones. Only the abstract was available, so there are no detailed numbers here.

Setup: four drifting task streams whose topic, workflow or domain shifts over time, built from BIRD (text-to-SQL), BFCL (function calling) and ScienceWorld. Three methods tested: ReasoningBank, GEPA and Meta-Harness.

Findings:

  • Self-evolution helps overall on most streams.
  • But more plasticity (adapting fast) consistently costs stability (remembering old skills).
  • Methods that edit one shared prompt or workspace (GEPA, Meta-Harness) make global edits: a change that helps today's task hurts unseen tasks and overwrites earlier knowledge as the stream shifts.
  • Retrieval-based memory (ReasoningBank) keeps updates more local across distant domains, but it still pulls irrelevant "foreign" memories for new tasks, and suffers retrieval collisions when similar questions need different workflows.

Conclusion: today's self-evolving agents are incomplete continual learners.

Why it works

This is the classic stability-plasticity dilemma from machine learning, now showing up in prompts instead of weights:

  • A single shared prompt is like a model with no capacity limits on interference: every edit touches every task. Fixing SQL-related instructions can quietly break the function-calling behaviour.
  • Memory retrieval isolates knowledge per situation, but similarity is not relevance. Two queries can look alike while needing different procedures, so the agent retrieves the wrong playbook.

The bigger pattern

"Agents that improve themselves by editing their instructions" have the same failure mode as a team wiki that everyone edits without review: drift and regressions. You need scoping (which rule applies where) and regression tests on old tasks.

What it means in practice

  • If you let agents update their own skills or prompts, keep edits scoped to a section or task type, and keep a small regression set of past tasks to check before accepting a change.
  • For memory-based agents, store context about when a memory applies, not just the text, to avoid retrieval collisions.
  • Version prompt and skill changes in git so regressions can be traced and reverted.