Paper Explained: Co-Evolution in Agentic Systems — Three Stages Toward Self-Directed Evolution

Why do agents that are supposed to keep improving after deployment hit a ceiling? A ground-up walkthrough of a survey that organises the field into three stages — evolving peers, evolving environments, and an evolving evolution mechanism — with the defining equations, representative methods, and the open problems in evaluation and safety.

Co-Evolution in Agentic Systems: Toward Self-Directed Evolution Beyond Human Design

Stop running and the world leaves you behind

In Through the Looking-Glass, the Red Queen tells Alice that here you must run as fast as you can just to stay in the same place. Biologists borrowed the line for the Red Queen effect: predators get faster, so prey get faster, and the chase never ends.

This survey brings that idea to AI agents. The premise is simple. Agentic systems are expected to keep getting better after they are deployed, yet the dominant form of self-evolution moves only one side of the relationship (§1).

The ceiling that self-evolution runs into

Self-evolution means an agent keeps updating itself from experience, feedback, and failure without a human in the loop. The common shape is single-entity self-evolution — fine-tuning the model backbone, rewriting memory, adding skills — all of it happening inside one agent (§1).

The problem the paper names is that those updates sit inside a static learning context. Fixed tasks, fixed feedback rules, fixed counterparts. Solving the same benchmark over and over, sparring with the same opponent, leaving the reward scheme exactly as a human wrote it — in every case the learning context has stopped moving. When only one side adapts, the headroom eventually runs out. Sustained progress requires mutual adaptation rather than adaptation on only one side — that is the Red Queen effect restated for agents (§1).

Defining the agentic system first

The paper refuses to leave this vague (§2.1). An agentic system $S=(A,E)$ consists of an agent collective $A$ and an environment $E$. Each individual agent decomposes as:

Put in words: an agent ($a_i$) is nothing more than a brain plus the kit strapped to it, and the kit is part of the definition.

Here $m_i$ is the model backbone (the LLM or policy itself) and $h_i$ is the harness — memory, tools, skills, prompts, workflows. In everyday terms, $m_i$ is what moves when you train, and $h_i$ is what you touch as code: prompt templates, tool definitions, the memory schema. Two agents can share a backbone and still count as distinct if their harnesses give them different roles or objectives. "The agent evolved" is then defined as:

In plain terms: either the brain or the equipment changed, and that counts as evolution. $\Delta$ reads as "how much this changed since last time", $\iff$ as "the two sides mean the same thing", and $\lor$ as "or" — which says that training is not the only route in: rewriting a single line of a prompt already qualifies under this definition.

Agents are also not an unordered set. They come with a structure $\Pi$ encoding roles, communication topology, and division of labour, written $A=(\{a_1,\dots,a_n\},\Pi)$. A change to $\Pi$ alone already means $A$ evolved. The environment $E$ is everything outside $A$, and $\tau^t$ is the accumulated history of thought–action–observation cycles. If the basic anatomy of an agent is unfamiliar, LLM agents from the ground up makes the rest of this easier.

Co-evolution requires mutual pressure, not just contact

Call the mechanism that drives evolution $\Omega$, so that $S^{t+1}=\Omega(S^t,\tau^t)$. $\Omega$ is the bundle of rules that specifies what can evolve, when evolution triggers, how variants are produced, where it happens, and how its quality is judged (§2.2).

Against that backdrop the paper defines co-evolution as a setting where at least two evolving units jointly adapt and continually reshape each other's further evolution, rather than merely exchanging information or interacting. Talking to each other is not enough. One side getting stronger has to change the problem the other side faces.

There is a quick test. Freeze one side, rerun the same experiment, and see whether the result changes. If it does not, what you have is interaction, not co-evolution. That line is exactly what lets the survey exclude most multi-agent work from its scope. The taxonomy then orders the remaining literature by how far the boundary of evolutionary freedom expands (§2.3).