[Roadmap] AutoGen Studio

[gagb]

Tip

Want to get involved?

We'd love it if you did! Please get in contact with the people assigned to this issue, or leave a comment. See general contributing advice here too.

The app is in /samples/apps/autogen-studio .
Contribution guide is here.

Roadmap

Beta Give feedback

1. [P0] Rewrite DB Layer to enable entity linking [Feature Request]: Improve AutogenStudio Database Implementation (link database entities, remove api keys) #1694. [AutoGen Studio] Add database versioning to manage schema compatibility #1342
2. [P0] Support for a public gallery of agents, workflows, skills, sessions (logs)
3. [P0] Support additional types of workflows in AGS - e.g.., current twoagent/groupchat, sequential chat, automated workflows.
4. [P0] Add ability to learn skills, help users create skills [Issue]: Editing a Skill #1442
5. [P0] Better UX for authoring workflows [Feature Request]: Re-arrange items via drag-n-drop and Re-name playground chats #1362
6. [Feature Request]: Autogen Studio unable to change human input mode #1358
   feature proj-studio +2
7. [P1] Ability to switch between using tool call API and code executor for executing skills #3058
   0.2 needs-triage proj-studio +3
8. [P1] Allow users to interrupt a multi-agent conversation
9. [P1] Ability to rate agents, workflows, skills, sessions
10. [P3] Support extracting skills from current session
11. [AutoGen Studio] AutoGen Studio: Add support for other contributed agents #1364
    0.2 feature proj-studio +3
    
12. [P3] Test UI on mobile device views
13. [P3] Testing on Windows
14. [Feature Request]: Changes made to the llm models in the "Models" tab to carry over everywhere #1361
    feature proj-studio +2
15. [AutoGen Studio] Add Friendly Title to Sessions #1391
    good first issue proj-studio +2
    
16. [AutoGen Studio] Support Authentication in AutoGen Studio

[victordibia]

Great. Current work for this is being done on the autogenstudio branch.

[iMicknl]

Would it make sense to have the devcontainer compatible with AutoGen Studio? Currently it is a pain to run AutoGen Studio from the default devcontainer of this project. Best would be if it is fully ready, and even has a VSCode task to start AutoGen Studio.

[gagb]

Would it make sense to have the devcontainer compatible with AutoGen Studio? Currently it is a pain to run AutoGen Studio from the default devcontainer of this project. Best would be if it is fully ready, and even has a VSCode task to start AutoGen Studio.

Good point. Added to the feature list.

[JonasBE13]

Will RAG be added for AutoGen studio?

[romilandc]

Would it make sense to add Ollama model configuration within the Build -> Models tab? The only method I know of uses is supported by LiteLLM, e.g. https://gist.github.com/shimomurakei/5692335e4fdfb12450afa2580002db77 but UI configuration would be great. Thank you!

[victordibia]

Hi @romilan24 ,

Thanks for the note. Ollama does provide an openai compatible api. https://ollama.com/blog/openai-compatibility.
This way, if you put in your model name, base url and api key, (similar to how you will use an openai model)
Are you having any issues with this?

[romilandc]

Hi @romilan24 ,

Thanks for the note. Ollama does provide an openai compatible api. https://ollama.com/blog/openai-compatibility. This way, if you put in your model name, base url and api key, (similar to how you will use an openai model) Are you having any issues with this?

That actually worked! Thank you for the suggestion, very simple implementation. Then I would suggest we add this as an example for reference because I wasn't able to find any recent examples showing this.

Took some screenshots for reference:

Happy to write this up as well. Thanks @victordibia

[harrywang]

@gagb @victordibia @JingyaChen

Thanks for creating the great AutoGen framework - I have been using it to teach my students about AI agents. My startup Takin.ai (https://takin.ai/) wants to integrate with AutoGen Studio and we saw the new interface shown on the release news web page (https://www.microsoft.com/en-us/research/blog/introducing-autogen-studio-a-low-code-interface-for-building-multi-agent-workflows/).

It seems the changes are quite significant - I wonder whether you can provide any information on the new version of AutoGen Studio:

1. Will the tech stack be changed? the current one is Fastapi + Gatsby

2. When will the new version be released? Any estimate?

Should we wait for the new version or use the current version?

Thanks a lot for your help!

[joslat]

Yes great point, wondering if this roadmap is still relevant. Anyhow I agree on that the UI is sweet enough to "ask for more" :)

[victordibia]

@harrywang

We expect the same backend functionality and tech stack, just updates to UX.

• Gatsby and FastAPI will remain unchanged.
• We do not have an ETA at the moment, but working on this.

[harrywang]

@harrywang

We expect the same backend functionality and tech stack, just updates to UX.

• Gatsby and FastAPI will remain unchanged.

• We do not have an ETA at the moment, but working on this.

@victordibia Thanks a lot. Your reply is very helpful!

[shanmu-raoyunfei]

When will this new version be released?

[rysweet]

@victordibia - are you still using this issue for tracking? will these items carry forward to 0.4?

[ghost]

When will this new AutoGen Studio UI become available?

[victordibia]

@rysweet , we might replace this as work begins replatforming AutoGen Studio on autogen 0.4. I'll try to circle back and close this at that time

Hi @dipteshbosedxc , we do not have an ETA at the moment but we are working on it!

[victordibia]

AutoGen studio is being re-written to use the updated AutoGen 0.4 api.
As part of that we will be implementing an updated UX (in line with the screenshots above @shanmu-raoyunfei).
With the new api, a few capabilities are more straighforward to implement (@SailorJoe6) - e.g., being async and message driven we can now more easily stream agent messages, visualize message flow between agents, interrupt runs, implement human input mode (@SailorJoe6) and a few other things.

ags_update.mp4

Current progress is being tracked in this issue here - #4006 . We will close this issue in favor of that one.
@SailorJoe6 , and others, thanks for all the contributions on the previous version of AGS, happy to get feedback on the current work.