-
Notifications
You must be signed in to change notification settings - Fork 18
Description
The A2A spec says that the payload of a message/send request (MessageSendParams) contains an optional metadata field, which is for the use of extensions:
https://a2a-protocol.org/latest/specification/#711-messagesendparams-object
The Worker.run_task() method takes a TaskSendParams argument, which also has a field metadata for extension metadata.
But when the message is forwarded to the broker (TaskManager.send_message()), this metadata object is omitted.
Is there any particular reason for this? In some cases it could be useful for the Worker to have access to extension metadata.
I think that resolving this would require no more than to add 'metadata': request['params']['metadata'] to the initialisation of broker_params in TaskManager.send_message().
fasta2a/fasta2a/task_manager.py
Line 123 in a6d6cf0
| broker_params: TaskSendParams = {'id': task['id'], 'context_id': context_id, 'message': message} |