Skip to content

SelectorGroupChat with selector_func() Serialization Issue #6519

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

Open
Misto1997 opened this issue May 13, 2025 · 2 comments
Open

SelectorGroupChat with selector_func() Serialization Issue #6519

Misto1997 opened this issue May 13, 2025 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation needs-triage

Comments

@Misto1997
Copy link

Misto1997 commented May 13, 2025

What is the doc issue?

Describe the issue
As per the Serializing Components doc, we can serialize/dump Teams as well, but there seems to be a feature gap/bug because of which while taking a dump of SelectorGroupChat, it skips Custom Selector Function(selector_func()).

Can someone confirm the same behaviour? Is it a known issue?

What do you want to see in the doc?
We should explicitly call out such feature gaps/bugs, as selector_func() is crucial for more control over the orchestration of the workflow, and running this config on the studio/framework will not work.

Link to the doc page, if applicable

https://microsoft.github.io/autogen/stable//user-guide/agentchat-user-guide/serialize-components.html

@Misto1997 Misto1997 added documentation Improvements or additions to documentation needs-triage labels May 13, 2025
@ekzhu
Copy link
Collaborator

ekzhu commented May 13, 2025

It is a known issue, as this requires serializing and deserializing procedure code with dependencies -- you can imagine the security risk associated with this.

One way to address this is through using GraphFlow, which can be configured declaratively. But that API is experimental.

@Misto1997
Copy link
Author

Agreed.
I understand the limitation, and that’s exactly why I’ve suggested explicitly documenting this behaviour.

Since selector_func isn’t serialised with team.dump_component(), it can easily lead to confusion or unexpected behaviour for users. Highlighting this in the documentation would help set proper expectations and prevent misuse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation needs-triage
Projects
None yet
Development

No branches or pull requests

3 participants