Conversation
| if not agent_advertised_extensions: | ||
| return None | ||
|
|
||
| for req_uri in requested_extensions: |
There was a problem hiding this comment.
So, the client is the one that determines which version gets selected if there are two, right? If it sends [0.8, 0.9], then this will select 0.8 even if 0.9 is available, just because it is first.
Do we want to be more complicated than that, like select the "newest" version that are in both sets? Or do you think we should leave it up to the client to send them in preferred order?
There was a problem hiding this comment.
I was under the impression that a client would typically only request a single version at a time. Is there a scenario where an Angular v0.9 renderer would need to request both v0.8 and v0.9 simultaneously?
If we do need to support multiple versions, we cannot rely on the client to determine priority or order, as context.requested_extensions is implemented as a set within the A2A SDK.
There was a problem hiding this comment.
The client can support more than one version at a time. But someone has to decide. Maybe the client is already doing this based on what the agent card has in it, and just requesting the one that it wants, and I just don't know how it works. :-)
There was a problem hiding this comment.
Let's go with the current logic. I'll follow up with a separate PR to select the "newest" version and we can have more discussions there explicitly.
The agents may support multiple versions of A2UI extensions. Based on client requested extension, the agent SDK should dynamically activate one that is supported by the agent.
|
I've got the contact_lookup, restaurant_finder and rizzcharts samples working individually, but when testing the orchestrator sample, the A2UI extension seems not to be propagated to the sub agents. I'll take a deeper look later and verify other samples, component_gallery and mcp_app_proxy. |
2 participants
The agents may support multiple versions of A2UI extensions. Based on client requested extension, the agent SDK should dynamically activate one that is supported by the agent.
Description
Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.
List which issues are fixed by this PR. For larger changes, raising an issue first helps reduce redundant work.
Pre-launch Checklist
If you need help, consider asking for advice on the discussion board.