-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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: Improve Gallery UX. #5047
Comments
I got a same problem |
Thanks for the feedback. You can create a new gallery (import from a URL or paste it in), modify it to add teams, tools, models, termination conditions etc. @joslat , @LeonG7 any chance you have tried the Gallery? |
Does this mean that each gallery has its own configuration of models, agents, tools, terminations? |
Yes, a Gallery is a collection of components.
Yes. Any model that has an OpenAI compliant API can be used . Gemini has an openai client. Please see the documentation here https://microsoft.github.io/autogen/dev/user-guide/autogenstudio-user-guide/faq.html#q-can-i-use-other-models-with-autogen-studio You will need to update the
|
I tried but no option to edit the components or add new ones, only way is to edit the code/Json directly right at the moment, or am I wrong? |
Yes. |
I think that would make a lot of sense, @victordibia 💯 |
Hi. It would be nice if changes to the gallery file are saved to a database instead of the browser's localStorage. Because: 1. All data should be recoverable from appdir when doing a fresh install. 2. When I change the server's port from 8080 to 8081 the localStorage from localhost:8080 isn't available. |
@itisi000 , |
What feature would you like to be added?
Make it easier to import, edit, customize items in a Gallery. Current UX only enables direct JSON editing.
AutoGen Studio: cannot create components/templates: models, agents, tools and teams.
In the previous version it was possible to create custom configured instances that could be reused (templates/components). On the new one I miss those features.
Why is this needed?
To be able to define reusable components. Also ideally there should be a publicly available library of those so that we can share through export and import them and enhance our experience greatly.
The text was updated successfully, but these errors were encountered: