Python: Propagate A2A metadata from Message, Artifact, Task, and event types#5256
Open
kartikmadan11 wants to merge 1 commit intomicrosoft:mainfrom
Open
Python: Propagate A2A metadata from Message, Artifact, Task, and event types#5256kartikmadan11 wants to merge 1 commit intomicrosoft:mainfrom
kartikmadan11 wants to merge 1 commit intomicrosoft:mainfrom
Conversation
…t types A2AAgent was only propagating Part-level metadata but silently dropping metadata from Message, Artifact, Task, TaskStatusUpdateEvent, and TaskArtifactUpdateEvent. This adds metadata propagation at each conversion boundary so server-transmitted metadata is preserved on AgentResponseUpdate.additional_properties. For streaming events (TaskArtifactUpdateEvent, TaskStatusUpdateEvent), metadata from the inner object (artifact/message) is merged with the outer event metadata. Adds 8 regression tests covering all affected types plus None-safety. Fixes microsoft#5240
Contributor
giles17
approved these changes
Apr 15, 2026
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
3 participants
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.
Motivation and Context
The A2A protocol defines a
metadatafield onMessage,Artifact,Task,TaskStatusUpdateEvent, andTaskArtifactUpdateEvent. Currently,A2AAgentonly propagates Part-level metadata (via_parse_contents_from_a2a), but silently drops metadata at every other level, losing information transmitted by the server.Fixes #5240
Description
Metadata is now propagated at each conversion boundary in
_agent.py:MessageAgentResponseUpdate.additional_propertiesmessage.metadatadirectlyArtifactMessage.additional_properties→ merged into updateartifact.metadataon Message, then merged withtask.metadataTaskAgentResponseUpdate.additional_propertiestask.metadataon all updates produced from the taskTaskArtifactUpdateEventAgentResponseUpdate.additional_properties{**artifact.metadata, **event.metadata}mergedTaskStatusUpdateEventAgentResponseUpdate.additional_properties{**message.metadata, **event.metadata}mergedMessageMessage.additional_propertieshistory_item.metadatadirectlyFor streaming events, metadata from the inner object (artifact or status message) is merged with the outer event metadata, since they represent different layers of information.
Eight regression tests cover all affected types plus a None-safety check.
Contribution Checklist