A2A: propagate request and message metadata through the bridge#282
Merged
rockfordlhotka merged 2 commits intomainfrom Apr 21, 2026
Merged
A2A: propagate request and message metadata through the bridge#282rockfordlhotka merged 2 commits intomainfrom
rockfordlhotka merged 2 commits intomainfrom
Conversation
Add optional Metadata dictionaries to AgentMessage and AgentTaskRequest, and map them (plus non-text parts) across the HTTP → RabbitMQ bridge so capability handlers can read structured inputs a caller attached to an A2A v1 request. The "skill" key stays consumed for routing; everything else on SendMessageRequest.Metadata lands on AgentTaskRequest.Metadata, and Message.Metadata round-trips through AgentMessage.Metadata. Data parts are mapped alongside text parts in both directions. Closes #281 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Metadata: IReadOnlyDictionary<string, string>?toAgentMessageandAgentTaskRequest.RockBotBridgeHandler, populateAgentTaskRequest.MetadatafromRequestContext.Metadata(minus the"skill"key already consumed for routing) andAgentMessage.Metadatafrom the incomingMessage.Metadata. JsonElement values are stringified; non-string kinds are preserved via their raw JSON text.Parts (not just the first text) intoAgentMessagePart, propagatingKind = "data"parts with their JSON body andMediaType.AgentMessage.Metadataback onto outboundMessage.Metadata, and emit data parts viaPart.FromData— text parts continue to pass through as before.Messageverbatim instead of a text-only rebuild, so captured history reflects what was actually sent.Test plan
AgentMessage.MetadataandAgentTaskRequest.MetadatainRockBot.A2A.TestsRockBot.A2A.Gateway.Testscovering:"skill"key stripped from request metadata, text/data part mapping in both directions, stringification of JsonElement values, andJsonElementround-trip for repliesCloses #281
🤖 Generated with Claude Code