ag2-network-workflow

AG2 Network — Workflow Adapter

workflow is the orchestrated multi-party adapter. A declarative TransitionGraph describes who speaks first, what conditions fire on each turn, and when the channel terminates. It's the modern replacement for the classic GroupChat + Agent.handoffs pattern — turn-taking lives in the hub, not in an in-process speaker selector.

Prerequisite: read ag2-network-quickstart first. This skill assumes you know Hub.open, HubClient.register, the channel lifecycle, and the basic agent_client.open(...) / channel.send(...) flow.

When to use

Load this skill when the user asks for any of:

• "Two/three/N agents with conditional handoffs"
• "Pipeline / sequence of agents (researcher → writer → editor)"
• "Triage agent routes to specialists"
• "Drafter / reviewer feedback loop"
• "Coordinator + specialists / hierarchical orchestration"
• "Migrate from GroupChat / ConversableAgent.handoffs / ReplyResult(target=...)"
• "I want context-driven routing (OnContextCondition, StringContextCondition)"

Don't use workflow for:

• Strict 1Q1R between two agents → consulting (see ag2-network-quickstart).
• Free-form 2-party chat with no turn order → conversation (see ag2-network-quickstart).
• Fixed round-robin with no conditions → discussion (see ag2-network-discussion).

If the user is unsure, the rule of thumb: need any condition more complex than "next speaker in a fixed list"? Use workflow.

Shape

Participants	2+
Turn order	Whatever TransitionGraph says
Auto-close	Yes — when graph emits TerminateTarget or max_turns is hit
Default view	NamedWindowedSummary(recent_n=N*2)
Default expectations	turn_within(120s, warn), turn_within(600s, auto_close)
Required knob	{"graph": <TransitionGraph.to_dict()>}

The expectation is strict: a stuck speaker auto-closes the channel after 10 minutes. Tune via ag2-network-governance.

Workflow agents and the NetworkPlugin