How is the termination condition expressed in an AutoGen GroupChat?

Attempt it

Quick reference

TL;DR

AutoGen terminates via two layers. An `is_termination_msg` predicate over the last message plus a `max_round` hard ceiling on the GroupChat.

Memory aid

Sign in for the mnemonic that makes this stick. See Pro pricing.

Easy to grasp

Think of a brainstorming meeting with a written rule and a clock on the wall. The rule says 'when anyone slides a sticky note that says STOP, we are done.' The clock says 'no matter what, the meeting ends after 30 minutes.' Most meetings end on the sticky note. The clock exists for the day everyone forgets the rule and keeps talking. AutoGen runs its multi-agent chat the same way. A predicate checks the last message for a stop signal, and a round counter on the chat ends things if no one ever slides the note.

Key concepts

LLM Frameworks Agents

Quick scan · 2–4 min

Everything important, quickly.

6 min: predicate semantics, sentinel convention, max_round backstop, agent-level vs manager-level wiring, AutoGen 0.4 TerminationCondition classes.

Code example

python

from autogen import AssistantAgent, UserProxyAgent, GroupChat, GroupChatManager

def is_done(msg):
    return "TERMINATE" in (msg.get("content") or "")

assistant = AssistantAgent(
    name="planner",
    system_message="Solve the task. When finished, write TERMINATE on its own line.",
    is_termination_msg=is_done,
)
user = UserProxyAgent(
    name="user",
    is_termination_msg=is_done,
    human_input_mode="NEVER",
)

chat = GroupChat(agents=[assistant, user], messages=[], max_round=12)
manager = GroupChatManager(groupchat=chat, is_termination_msg=is_done)

user.initiate_chat(manager, message="Outline a 1-week launch plan.")

Real-world examples

Real products, models, and research that use this idea.

Microsoft Research's AutoGen demos use the 'TERMINATE' sentinel pattern in their reference notebooks for GroupChat tutorials
AutoGen 0.4 introduced `TerminationCondition` classes (MaxMessageTermination, TextMentionTermination, TokenUsageTermination) that compose the predicate plus ceiling pattern explicitly
Many production multi-agent stacks layer a token-budget termination on top of the standard two for cost-runaway protection

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QHow does AutoGen 0.4's `TerminationCondition` class system change the predicate plus ceiling story?

Sign in or go Pro to see the approach for this follow-up.

QWhen would you make `is_termination_msg` an LLM call?

Sign in or go Pro to see the approach for this follow-up.

QWhy does each agent get its own termination predicate?

Sign in or go Pro to see the approach for this follow-up.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

Sign in for 5 unlocks/day or go Pro for unlimited revision sheets. See Pro pricing.

References

Primary sources. Skim if you want the original framing.