features

Fleet fan-out

Broadcast input across N sessions with divergence detection and halt-on-failure rolling mode.

The fan-out controller turns one operator’s keystrokes into N parallel sessions. It is built on the same control channel — every target session is just another uterm session, registered as a fan-out participant.

One operator broadcasting to four hosts via the fan-out controller, with one host flagged divergent.

Modes

Parallel: input goes to every target simultaneously, output streams back interleaved.
Sequential: targets run one at a time, optionally halting on the first failure (rolling deploy semantics).

Divergence detection

The controller computes Levenshtein similarity between the latest output delta from each target and the majority delta. When one target’s output drifts away from the rest, it is flagged immediately and surfaced in the UI — that host did something different from the others.

In sequential mode, divergence (or an explicit non-zero exit) can stop the rollout before the next target is touched.

Auditing

Because every target session is a real uterm session, the full DeckMux record (presence, snapshots, annotations, chat) is captured per-target. A fleet fan-out produces N independent, replayable session recordings.