-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Support A2A metadata in A2aAgentExecutor #3160
Copy link
Copy link
Open
Labels
core[Component] This issue is related to the core interface and implementation[Component] This issue is related to the core interface and implementationneeds review[Status] The PR/issue is awaiting review from the maintainer[Status] The PR/issue is awaiting review from the maintainer
Milestone
Metadata
Metadata
Assignees
Labels
core[Component] This issue is related to the core interface and implementation[Component] This issue is related to the core interface and implementationneeds review[Status] The PR/issue is awaiting review from the maintainer[Status] The PR/issue is awaiting review from the maintainer
Type
Fields
Give feedbackNo fields configured for Feature.
Is your feature request related to a problem? Please describe.
A2A <> x402 integration relies on
metadatawhich is discarded byconvert_a2a_request_to_adk_run_argswithin theA2aAgentExecutor. For now I'm doing:and monkey patching, but it would be great to get native support for this.
Describe the solution you'd like
Ideally I'd like for arbitrary A2A metadata to be made available to the ADK agent as part of the
state(unless there is a better spot, maybe addrequest_metadatatoInvocationContext?). At a minimum, I'd like theA2aAgentExecutorConfigto support a full A2A request to ADK run args, not just the partiala2a_part_converter.Describe alternatives you've considered
Ad-hoc transfer like above.
Additional context
This is required by the A2A <> x402 spec.