-
Notifications
You must be signed in to change notification settings - Fork 32
feat(schema): extend agent spec module to support deployment options #355
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
feat(schema): extend agent spec module to support deployment options #355
Conversation
akijakya
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, well done!
schema/objects/agentspec_communication_protocol_responses_api.json
Outdated
Show resolved
Hide resolved
cbab270 to
9cae700
Compare
|
@akijakya Thank you for the review! |
|
I fixed the failing CI job, could you please rebase onto the latest main? |
Signed-off-by: Paul Cayet <[email protected]>
9cae700 to
039d8a9
Compare
ramizpolic
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this also raises a question of perhaps having a more generalized/native OASF module (outside of agentspec) for communication.
there is a recurring pattern that different standard are redefining the communication support, so it may be useful to have this natively supported by OASF.
for the purpose of the agentspec, LGTM
Context
In this PR we extend the Agent Spec module to enable assistant developers to provide and store information about how an agent can be instantiated or consumed (including what are the preferred runtime framework / serving protocol and required environment variables to run the agent), including:
See the discussion in #352