Is your feature request related to a problem? Please describe.
Right now there's no standard way of communicating Task progress with A2A, resulting in a bad user experience.
I have built typical, conversational agents with A2A. They accept text, have a number of tools they can call, return the results of the tool calls as Artifacts, and send intermediate messages the agent generates as TaskStatusUpdateEvents.
However, because there's no standard way of communicating Task progress, my only option is to send TaskStatusUpdateEvents.
The problem with TaskStatusUpdateEvents is that:
- They would interfere with the intermediate messages the agent generates. The first message might be "Sure, let me help you with that.", followed by "Tool Call X 1/100", "Tool Call X 2/100", "Tool Call X 3/100", ..., and finally "Here are the results I found".
- Because they're typically text, there's no way of displaying them in a UI. I understand data could be sent, but without a standard the format will vary agent to agent.
This pattern is common enough that a standard would make sense.
Describe the solution you'd like
Something like MCP Progress: https://modelcontextprotocol.io/specification/2025-03-26/basic/utilities/progress.
Because a Task can have multiple tool calls it might make sense to have a unique ID associated with each progress. An ideal solution would allow updates from multiple unique IDs at once for parallel tool calls.
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct
Is your feature request related to a problem? Please describe.
Right now there's no standard way of communicating
Taskprogress with A2A, resulting in a bad user experience.I have built typical, conversational agents with A2A. They accept text, have a number of tools they can call, return the results of the tool calls as
Artifacts, and send intermediate messages the agent generates asTaskStatusUpdateEvents.However, because there's no standard way of communicating
Taskprogress, my only option is to sendTaskStatusUpdateEvents.The problem with
TaskStatusUpdateEvents is that:This pattern is common enough that a standard would make sense.
Describe the solution you'd like
Something like MCP Progress: https://modelcontextprotocol.io/specification/2025-03-26/basic/utilities/progress.
Because a
Taskcan have multiple tool calls it might make sense to have a unique ID associated with each progress. An ideal solution would allow updates from multiple unique IDs at once for parallel tool calls.Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct