AI Trend Notifier
EN
← wiki

$ cat wiki/papers/2026/2607.21596-flowevo.md

FlowEvo: Self-Evolving Agents through the Co-Evolution of Workflows and Executable Skills (arXiv:2607.21596)

paperupdated 2026-08-25created 2026-08-25

TL;DR

An agent that builds a workflow at inference time normally throws it away when the episode ends; a skill library normally is assembled offline and never grows from the agent's own runs. FlowEvo closes both gaps at once and without training: successful workflows are compiled into callable skills, stored in a persistent bank, and retrieved either for direct execution or as context for building the next workflow. It tracks each skill's downstream utility and suppresses skills that cause negative transfer (source).

Authors & Org

Not obtainable. arxiv.org is EGRESS_BLOCKED from this run's sandbox; the paper was not read. Listed on HuggingFace Daily Papers, 2026-08-25, 16 upvotes (source). Code at https://github.com/DEFENSE-SEU/FlowEvo, per the abstract.

Method

  • Training-free. Everything happens at inference time; no gradient step on the backbone.
  • Compile, don't remember. A workflow that succeeded is turned into a callable skill — an executable routine, not a transcript — and written to a persistent bank.
  • Two uses for a retrieved skill: run it directly, or feed it as context while constructing a new workflow. The second is what lets the library grow rather than merely be consumed.
  • A suppression mechanism, which is the part with teeth. Each skill's downstream utility is tracked, and skills that cause negative transfer are suppressed. A library that only accumulates gets worse; this is the term that stops it.

Results

Shared GPT-4o-mini backbone, against 8 baselines, on the full standard splits of ALFWorld, HumanEval, MBPP, GSM8K and MATH-500:

MeasureResult
Rank across all five benchmarkshighest accuracy of the 9 systems
ALFWorld85.6%, +26.4 points over the strongest baseline
ALFWorld token useroughly one third of that baseline's
Across 10 base models, 7B → 671Bbeats ExpeL in 49 of 50 model-dataset comparisons
The ALFWorld line is the load-bearing one: **more accuracy at a third of the
tokens** is the opposite of the usual scaffold trade, where a gain is bought with
extra calls.

Significance

This is the third paper in eight days arguing that the object to optimize is the scaffold, not the model — and the three do not cite each other. SkillEvo: Self-Renewing Evolution Gradients from Multi-Turn Interaction Feedback (arXiv:2608.13120) evolves skills and finds the binding constraint is whether feedback keeps supplying a trustworthy gradient; EnvHarness: Awakening Static Worlds for Agent Learning (arXiv:2608.19880) evolves the environment while retaining its original verifier; FlowEvo evolves the workflow↔skill pair and adds the term the other two do not have — explicit suppression of skills that hurt.

It converges with Hierarchical Self-Improvement: A Framework for Task-Specific Evolvable Agent Harnesses (arXiv:2608.08466) on the same day, from the other end. HSI evolves the harness around a frozen model and names two hard bounds (feedback fidelity, backbone capability). FlowEvo freezes the model too, and its negative-transfer tracking is a feedback-fidelity mechanism by another name. Neither cites the other; the agreement is this wiki's reading, not theirs.

Read against Agents (LLM Agents)'s standing tension, it lands on the "structure pays" side. MemTrapBench (MemTrapBench: Benchmarking Cognitive Traps in LLM Memory Use (arXiv:2608.20202)) and SWE-bench Science (SWE-bench Science: Can Coding Agents Resolve Engineering Tasks in Science? (arXiv:2608.19799)) both found added context taxing the agent; Repo0: Design-Driven Zero-to-All Code Generation (arXiv:2608.19854) found added structure paying. A compiled, executable skill is structure — and the token reduction is the evidence that it is not merely more context wearing a different name.

Open Questions

  • How is a skill retrieved? The retrieval step decides everything and the abstract does not describe it.
  • What is "downstream utility" measured on, and over how long a horizon before a skill is suppressed?
  • Does the bank saturate? Nothing read reports library size over time, or what happens after many more episodes than were run here.
  • Does it survive a stronger backbone? GPT-4o-mini is a small model; the 10-model sweep is against ExpeL, not a demonstration that a frontier backbone still benefits.
  • Are ALFWorld and MATH-500 the same kind of task for this method? A compiled executable skill is a natural fit for embodied task sequences and a strange one for arithmetic; the abstract reports one aggregate ranking.

Cite

FlowEvo: Self-Evolving Agents through the Co-Evolution of Workflows and
Executable Skills (2026). arXiv:2607.21596.

Referenced by

Sources