Skip to content
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

Migrate stateflow to 0.4 #3864

Closed
jackgerrits opened this issue Oct 21, 2024 · 1 comment · Fixed by #4026
Closed

Migrate stateflow to 0.4 #3864

jackgerrits opened this issue Oct 21, 2024 · 1 comment · Fixed by #4026
Labels
needs-design A design needs to be created and agreed upo proj-agentchat size-medium takes up to a week
Milestone

Comments

@jackgerrits
Copy link
Member

Stateflow is a useful pattern that should be ported to 0.4

@jackgerrits jackgerrits added this to the 0.4 milestone Oct 21, 2024
@fniedtner fniedtner removed the feature label Oct 24, 2024
@jackgerrits jackgerrits added the size-medium takes up to a week label Oct 24, 2024
@ekzhu ekzhu added the needs-design A design needs to be created and agreed upo label Oct 30, 2024
@ekzhu
Copy link
Collaborator

ekzhu commented Oct 30, 2024

The existing v0.2 stateflow does not support stateful select next speaker function as the state is passed in as the GroupChat object. It is a limitation as it forces the user to use a pre-defined state.

The core idea of stateflow is overriding the select speaker function. Thus, there should be a public GroupChat base class in v0.4 AgentChat. This requires more design.
 
Consider moving this to v0.4.1 milestone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-design A design needs to be created and agreed upo proj-agentchat size-medium takes up to a week
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants