fix: propagate A2A request metadata into the run config in AgentExecutor#1345
Open
copybara-service[bot] wants to merge 1 commit into
Open
fix: propagate A2A request metadata into the run config in AgentExecutor#1345copybara-service[bot] wants to merge 1 commit into
AgentExecutor#1345copybara-service[bot] wants to merge 1 commit into
Conversation
…utor` During A2A communication, `AgentExecutor` invoked the 4-argument `Runner.runAsync`, which hardcodes `stateDelta = null` and silently dropped the caller's incoming request metadata. Route the incoming request metadata (`RequestContext.getParams().metadata()`) into `RunConfig.customMetadata` under the `a2a_metadata` key, so downstream processing can read it. This mirrors ADK Python and Go, which pass A2A request metadata through the run config and leave the session state delta null, rather than writing framework IDs into session state. Add tests for the metadata and no-metadata cases. PiperOrigin-RevId: 945055254
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
1 participant
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.
fix: propagate A2A request metadata into the run config in
AgentExecutorDuring A2A communication,
AgentExecutorinvoked the 4-argumentRunner.runAsync, which hardcodesstateDelta = nulland silently dropped thecaller's incoming request metadata.
Route the incoming request metadata (
RequestContext.getParams().metadata())into
RunConfig.customMetadataunder thea2a_metadatakey, so downstreamprocessing can read it. This mirrors ADK Python and Go, which pass A2A request
metadata through the run config and leave the session state delta null, rather
than writing framework IDs into session state. Add tests for the metadata and
no-metadata cases.