feat(spec): add input and output content types #161
Conversation
This file contains hidden or 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
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.
Refs #162
This PR extends the Agent Detail schema by adding two optional array fields:
input_content_types: Specifies supported MIME types for incoming message content.output_content_types: Specifies supported MIME types for outgoing message content.Both fields default to
["text/plain"]when unspecified, aligning with the existing ACP message communication design. This addition clearly documents agent capabilities, promoting better interoperability and integration between agents.Motivation
Agents communicate via messages containing parts, each explicitly specifying their MIME
content_type. This change explicitly captures supported content types at the agent definition level, allowing clients and other agents to understand and correctly interact with each agent's inputs and outputs.Backward compatibility
Fully backward compatible. Agents not specifying these fields default to "text/plain" as before.
Next actions