Skip to main content

Agent Framework Orchestrations

Orchestration patterns for Microsoft Agent Framework. This package provides high-level builders for common multi-agent workflow patterns.

Installation

pip install agent-framework-orchestrations

Orchestration Patterns

SequentialBuilder

Chain agents/executors in sequence, passing conversation context along:

from agent_framework.orchestrations import SequentialBuilder

workflow = SequentialBuilder(participants=[agent1, agent2, agent3]).build()

# Preserve agent1 and agent2 as visible progress, while the default builder output remains Workflow Output.
workflow = SequentialBuilder(
    participants=[agent1, agent2, agent3],
    intermediate_output_from=[agent1, agent2],
).build()

ConcurrentBuilder

Fan-out to multiple agents in parallel, then aggregate results:

from agent_framework.orchestrations import ConcurrentBuilder

workflow = ConcurrentBuilder(participants=[agent1, agent2, agent3]).build()

HandoffBuilder

Decentralized agent routing where agents decide handoff targets:

from agent_framework.orchestrations import HandoffBuilder

workflow = (
    HandoffBuilder()
    .participants([triage, billing, support])
    .with_start_agent(triage)
    .build()
)

By default, each user response returns to the agent that requested it. To have the start agent re-evaluate every user turn, disable return-to-previous routing:

workflow = (
    HandoffBuilder()
    .participants([triage, billing, support])
    .with_start_agent(triage)
    .enable_return_to_previous(False)
    .build()
)

GroupChatBuilder

Orchestrator-directed multi-agent conversations:

from agent_framework.orchestrations import GroupChatBuilder

workflow = GroupChatBuilder(
    participants=[agent1, agent2],
    selection_func=my_selector,
    intermediate_output_from=[agent1, agent2],
).build()

MagenticBuilder

Sophisticated multi-agent orchestration using the Magentic One pattern:

from agent_framework.orchestrations import MagenticBuilder

workflow = MagenticBuilder(
    participants=[researcher, writer, reviewer],
    manager_agent=manager_agent,
    intermediate_output_from=[researcher, writer, reviewer],
).build()

Output Selection

Orchestration builders expose Workflow Output selection using participant names. The core rule is that output_from is an allow-list for Workflow Output, not a routing rule for every other participant output. Unselected participant payloads are hidden unless intermediate_output_from explicitly selects them as Intermediate Output.

  • output_from designates participant emissions as Workflow Output (type='output' events).
  • intermediate_output_from designates participant emissions as Intermediate Output (type='intermediate' events).

If neither list is provided, each builder uses its documented default Workflow Output contract. Sequential emits the last participant; Concurrent, GroupChat, and Magentic emit their aggregator/orchestrator/manager output; Handoff emits participants.

Selection Workflow Output Intermediate Output Hidden payloads
Omit both selections Builder default Workflow Output contract None Builder-specific non-output participant payloads
output_from="all" Every output-capable participant None None
output_from=[writer] Only writer None All other participant payloads
output_from=[writer], intermediate_output_from="all_other" Only writer Every output-capable participant not selected by output_from None
intermediate_output_from="all_other" None, except builder-internal default output executors where applicable Every output-capable participant Builder-internal plumbing payloads
output_from=[], intermediate_output_from="all_other" None, except builder-internal default output executors where applicable Every output-capable participant Builder-internal plumbing payloads
output_from=[writer], intermediate_output_from=[researcher, reviewer] Only writer researcher and reviewer Any other participant payloads

Invalid selections fail at construction or build time:

Invalid selection Why it fails
output_from="all_other" "all_other" is only valid for intermediate_output_from
intermediate_output_from="all" "all" is only valid for output_from
The same participant in both selections One payload cannot be both Workflow Output and Intermediate Output
Duplicate participant selections Duplicates are treated as configuration errors
Unknown participant selections Typos and missing participants are rejected
output_from=[], intermediate_output_from=[] Both explicit selections are empty

When an orchestration is wrapped with workflow.as_agent(), Workflow Output becomes normal response text. Intermediate Output becomes text_reasoning content so callers can inspect progress without changing .text behavior.

Documentation

For more information, see the Agent Framework documentation.

Metadata

Release files for agent-framework-orchestrations 1.4.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agent-framework-orchestrations 1.4.1
File Size Uploaded Provenance Actions
agent_framework_orchestrations-1.4.1.tar.gz 66.9 kB Without provenance Details for agent_framework_orchestrations-1.4.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for agent-framework-orchestrations 1.4.1
File Interpreter ABI Platform Actions
agent_framework_orchestrations-1.4.1-py3-none-any.whl Python 3 none any Details for agent_framework_orchestrations-1.4.1-py3-none-any.whl

Total release size: 140.8 kB

Release files / agent_framework_orchestrations-1.4.1.tar.gz

Download URL agent_framework_orchestrations-1.4.1.tar.gz
Size 66.9 kB
Tags Source
SHA-256 checksum
How to use checksums
038f3a4c2ab9926c2fda3c418039b4c3325614faa8a0a23441f667213017b49a
BLAKE2b-256 checksum
How to use checksums
1de2e62df84eb590558d212765ef49373998bd02014c95b8589fa59006271852
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via RestSharp/106.13.0.0

Release files / agent_framework_orchestrations-1.4.1-py3-none-any.whl

Download URL agent_framework_orchestrations-1.4.1-py3-none-any.whl
Size 73.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
dd05c19b58a766ae733d3220d64ad57e537ce3ed497f3c101645626454834a03
BLAKE2b-256 checksum
How to use checksums
57009b132aae609b0acea5c4898b95874182c1b172b10fd8b7fc728804099024
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via RestSharp/106.13.0.0

Security for agent-framework-orchestrations 1.4.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.4.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page