Most advances in single-agent systems don’t scale cleanly to long, cross‑domain workflows because harness complexity and domain coupling grow faster than manual design can manage. The paper's core insight is that treating each executable model+harness pair as a composable unit and giving the system mechanisms to assemble, archive, and evolve those units lets a host orchestrator expand reliable task coverage beyond individual agents under shared resource limits.
Key Findings
- Composition as leverage: decomposing goals to specialized agents and composing their outputs increases reliable coverage on long‑horizon tasks, meaning tasks that none of the individual agents could handle end‑to‑end can succeed when orchestrated correctly. This shifts engineering effort from monolithic harness design to reusable harness components and wiring.
- Persistent experience matters: EverOS provides durable user, agent, and world memory so successful workflows become reusable templates; making past experience queryable reduces repetitive design and speeds up future task assembly.
- Automated evolution pipeline: the paper describes an Evolver that proposes, tests, and retains harness changes against benchmarks, enabling iterative harness improvement rather than one‑off manual tuning. This closes the loop from failure diagnosis to verified improvement.
Who it's for and tradeoffs
Great fit if you need to coordinate many specialized models or tools across multi‑step, long‑horizon workflows and want reusable automations rather than bespoke scripts. Expect extra system complexity: adopting the harness model requires building or integrating a catalog of specialized agents, defining evaluation benchmarks, and investing in durable memory and verification checks. Look elsewhere if your workload is single‑step or narrowly scoped—composition and evolution overhead may not pay off for trivial tasks.
Where it fits
This work positions itself between single, highly engineered agent systems and heavyweight workflow orchestration platforms: it is research‑oriented but also provided as an open implementation for teams that plan to operationalize multi‑agent orchestration with continuous improvement.