Studio supports allocation of agent server #351
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rayrayraykk
reviewed
Aug 5, 2024
DavdGao
approved these changes
Aug 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Auto server allocation
In the previous version, users must provide
hostandportfor eachto_distcall, if they want to use an existing agent server.Now, the studio will automatically allocate a server to the
to_distfunction when the app is connected to the AgentScope Studio.Improve customized agent class loading
In the new version, the agent server also supports loading a directory of customized agent classes with in-directory dependencies with the
agent_dirparameter.Update Tutorial
The tutorial for the above new features and the usage of server manager page has been updated.
Checklist
Please check the following items before code is ready to be reviewed.