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

AutoGen Studio: dragging teams into the canvas #5049

Open
joslat opened this issue Jan 14, 2025 · 4 comments
Open

AutoGen Studio: dragging teams into the canvas #5049

joslat opened this issue Jan 14, 2025 · 4 comments
Labels
proj-studio Related to AutoGen Studio.

Comments

@joslat
Copy link

joslat commented Jan 14, 2025

What feature would you like to be added?

I want to be able to drag teams on the canvas, so instead of one agent, I can drag a "team"... or a sequential chat or a two-agent chat for example. I'd like to have an output and with that output trigger a separate workflow (team)

Why is this needed?

without this, how how do I visually create a workflow/team from zero? you simply cannot

@victordibia victordibia added the proj-studio Related to AutoGen Studio. label Jan 14, 2025
@victordibia
Copy link
Collaborator

victordibia commented Jan 14, 2025

Thanks @joslat ,

I think the behavior you are describing here is an explicit workflow experience with steps/nodes (each with a single input and output, where the output from one step is the input to the next).

We are working on enabling this sort of behavior more explicitly in the API - see #4623 . Once that is finalized on the API level, we will figure out how to enable it on the AGS UI.

@ekzhu @jackgerrits @gagb

@joslat
Copy link
Author

joslat commented Jan 15, 2025

I read the #4623 and yes, that would be awesome to support this and be able to create this workflows. Ideally I could add here a node which is a groupchat, a sequential chat or a two agent chat and also add nested chats on any agent. Drag the nested chat and drag it into the agent placeholder, or, onto the agent. as the agent is the wrapper for it.

This way I could get an agentic workflow to do one thing and delegate some part of the work to another one, enabling complex self-validated scenarios in a very powerful way.

As mentioned in other issue, I don't like the term "teams" and rather prefer "workflow" or "workflows" as at the moment it seems that "there can be only one" - imho that is too restrictive.

@victordibia
Copy link
Collaborator

I agree with everything you mentioned above.
Perhaps a Workflow is at a higher level of abstraction compared to Team.
This also makes sense as in theory, a GroupChat is not really a workflow as there isnt a strictly defined "flow" (the agents mostly chat and solve the task on the fly).

@joslat
Copy link
Author

joslat commented Jan 15, 2025

I see it this way too "Workflow is at a higher level of abstraction compared to Team" 👍
At the end the GroupChat is a "type of node" or also this could be defined as a graph...

Not exactly this but something similar to this image:
Image
There the ReseachManagerAgent and the DeveloperTeamAgent would be akin to the ChatManager but there would be more control on the flow with the possibility to better streamline and optimize the workflow.

(I was playing a bit last year with trying to map agents as graphs, to propose this: microsoft/semantic-kernel#7242)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proj-studio Related to AutoGen Studio.
Projects
None yet
Development

No branches or pull requests

3 participants