Skip to content

Multi agent orchestration ADR #11579

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 21 commits into from
May 9, 2025
Merged

Multi agent orchestration ADR #11579

merged 21 commits into from
May 9, 2025

Conversation

TaoChenOSU
Copy link
Contributor

@TaoChenOSU TaoChenOSU commented Apr 16, 2025

Motivation and Context

Multi-agent orchestration ADR. Includes the following orchestrations:

  • Concurrent
  • Sequential
  • Group Chat
  • Magentic One
  • Handoff

Description

An ADR for multi-agent orchestration in Semantic Kernel.

.Net PR: #11542
Python PR: #11993

Contribution Checklist

Sorry, something went wrong.

Copy link
Member

@eavanvalkenburg eavanvalkenburg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I currently don't see the need for Orchestration-type level abstractions, I think it could be much simpler, for me the key thing we need to do is enable Agents, Orchestration and Human-in-the-Loop to all have the same abstractions so that you can endlessly combine them in ways that make sense, and that would mean that each in- and output can be multiple, so that you can do the concurrent pattern but other then that we should strive for a simple setup, and this might be python specific, dotnet might need more defined subclasses of Orchestration...

@TaoChenOSU
Copy link
Contributor Author

I currently don't see the need for Orchestration-type level abstractions, I think it could be much simpler, for me the key thing we need to do is enable Agents, Orchestration and Human-in-the-Loop to all have the same abstractions so that you can endlessly combine them in ways that make sense, and that would mean that each in- and output can be multiple, so that you can do the concurrent pattern but other then that we should strive for a simple setup, and this might be python specific, dotnet might need more defined subclasses of Orchestration...

You're right. This is not Python only. We are considering the overall design by listing the building blocks necessary to accomplish multi-agent orchestration using SK agents and the shared runtime.

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@TaoChenOSU TaoChenOSU marked this pull request as ready for review April 30, 2025 18:12
Copy link
Contributor

@moonbox3 moonbox3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really great to see how this doc has evolved over several iterations into what it is now - awesome work.

@TaoChenOSU TaoChenOSU added this pull request to the merge queue May 9, 2025
Merged via the queue into main with commit 7a77e71 May 9, 2025
16 checks passed
@TaoChenOSU TaoChenOSU deleted the multi-agent-orchestration-adr branch May 9, 2025 18:49
@github-project-automation github-project-automation bot moved this to Sprint: Done in Semantic Kernel May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

5 participants