Some operations like GetTask / SubscribeToTask still used complex /
compound identifiers like `tasks/<uuid>` which requires the
clients/servers to deconstruct/construct these IDs as they are normally
using just the UUID to store the resource in the DB etc.
This commit refactors them so they are just the IDs, in some cases this
meant that we needed to split one field into two i.e. parent + name.
Fixes: #1390
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Darrel <darrmi@microsoft.com>
Fixes inconsistent spelling of cancel-related terms across the
specification and documentation. The proto definition uses
TASK_STATE_CANCELLED (double 'l'), but various documentation files were
using single 'l' spelling.
Changes:
- cancelled → canceled
- cancellable → cancelable
- `TaskNotCancellableError` → `TaskNotCancelableError`
Files modified:
- docs/specification.md
- docs/llms.txt
- docs/topics/life-of-a-task.md
All documentation now consistently uses single 'l' to match the proto
definition and JSON naming conventions.
Fixes#1270
Release-As: 1.0.0
---------
Signed-off-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Darrel <darrmi@microsoft.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Updates the specification to clarify that blocking SendMessage calls
must return when tasks reach interrupted states (input_required,
auth_required) in addition to terminal states. This prevents deadlock
scenarios where tasks waiting for user input would cause blocking calls
to hang indefinitely.
Changes:
- specification/grpc/a2a.proto: Updated blocking field comment to
include "terminal or interrupted state"
- specification/grpc/a2a.proto: Fixed AUTH_REQUIRED classification to be
an "interrupted state" (consistent with INPUT_REQUIRED)
- docs/specification.md: Updated blocking behavior description to
include interrupted states and changed "final task state" to "current
task state"
This enables proper client workflows where blocking calls can return on
INPUT_REQUIRED or AUTH_REQUIRED, allowing clients to provide the needed
information and resume with subsequent SendMessage calls.
Fixes#1264
---------
Co-authored-by: madankumarpichamuthu <madankumarpichamuthu@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Darrel <darrmi@microsoft.com>
This change simplifies the Part message design by:
- Renaming oneof 'part' to 'content' for clarity
- Flattening FilePart fields (file_with_uri -> url, file_with_bytes ->
bytes) directly into Part
- Flattening DataPart by using google.protobuf.Value instead of Struct
- Moving media_type and filename to Part level (available for all
content types)
- Removing separate FilePart and DataPart messages
Also updated migration guidance documentation to reference ancillary
documents instead of requiring an in-spec appendix.
Related to issue #1255
Replaces PR #1363
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Terminal states (COMPLETED, FAILED, CANCELLED, REJECTED) already
indicate task completion, making the final field redundant. This creates
consistency across streaming, polling, and push notification
communication patterns.
Changes:
- Removed final field (field 4) from TaskStatusUpdateEvent in proto
- Updated examples to remove final: true references
- Clarified that streams close upon terminal states
- Added migration guidance in Appendix A.2.2
Fixes#1232
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Darrel <darrmi@microsoft.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Bypassing tech-writing review as it is a simple rename and the majority of the changes are in the specification. Changes to conceptual docs are just for aligning names.
Restores the intentional rename from "Set" to "Create" for push
notification configuration methods that was lost during refactoring.
When the protocol was updated to support multiple Push Notification
Configurations, the method was changed from "Set" (which implies
replacing a single config) to "Create" (which implies creating a new
instance among many).
Changes across all documentation and proto files:
- specification/grpc/a2a.proto: Renamed RPC method and request message
- docs/specification.md: Updated all references, section titles, and
method tables
- docs/topics/streaming-and-async.md: Updated links and text
- docs/llms.txt: Updated method reference
Fixes#1394
---------
Co-authored-by: madankumarpichamuthu <madankumarpichamuthu@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Darrel <darrmi@microsoft.com>
Removes the `state_transition_history` field from `AgentCapabilities`
message as it has no corresponding API implementation. This capability
flag could mislead clients into expecting functionality that doesn't
exist in v1.0.
The field can be reintroduced in a future version when a proper
implementation is designed, including:
- Adding status_history field to Task message
- Adding include_status_history parameters to Get/List operations
- Defining behavior for history storage and retrieval
Fixes#1228
Co-authored-by: madankumarpichamuthu <madankumarpichamuthu@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Fixes inconsistencies between proto file documentation and the actual
method names defined in section 5.3 of the specification.
Updated method references in proto comments:
- message/send → SendMessage
- tasks/get → GetTask
- tasks/cancel → CancelTask
- tasks/pushNotificationConfig/delete → DeleteTaskPushNotificationConfig
- tasks/pushNotificationConfig/set → SetTaskPushNotificationConfig
- tasks/pushNotificationConfig/list → ListTaskPushNotificationConfig
These changes align the proto documentation with the Method Mapping
Reference table in section 5.3 of specification.md, which defines the
canonical method names for JSON-RPC and gRPC bindings.
Fixes#1267
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
### Description
Both fields are optional in
[types.ts](https://github.com/yarolegovich/A2A/blob/main/types/src/types.ts#L637)
and [jsonrpc
schema](https://github.com/a2aproject/A2A/blob/main/specification/json/a2a.json#L1683).
For both cases it might be useful to differentiate 0 and unset. For
example:
1. A client calls GetTask and doesn't want History to be fetched /
included in the response.
2. A client calls SendMessage and doesn't want history to be persisted
at all.
The change is backward-compatible and makes it possible for a2a servers
to provide consistent behavior regardless of the selected transport.
Fixes#1072
---------
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Darrel <darrmi@microsoft.com>
Relocates `supports_extended_agent_card` from AgentCard to
AgentCapabilities for architectural consistency. All optional features
that enable specific operations now reside in the capabilities object.
Rationale:
- Consistent placement: streaming, push_notifications, and
state_transition_history are all in AgentCapabilities
- Improved discoverability: developers naturally check capabilities for
optional features
- Semantic correctness: extended agent card support is a capability
Changes:
- Proto: Removed field 13 from AgentCard, added field 5 to
AgentCapabilities
- Field renamed: supports_extended_agent_card → extended_agent_card
- Updated all references: AgentCard.supportsExtendedAgentCard →
AgentCard.capabilities.extendedAgentCard
- Updated JSON examples to reflect new structure
- Added migration guidance in Appendix A.2.2 of specification
Breaking change: Clients and agents must update capability checking
logic. See specification Appendix A.2.2 for migration steps.
Fixes#1229
---------
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Darrel <darrmi@microsoft.com>
This PR combines two fixes for the ListTaskRequest last_updated_after
field one changes the field to a timestamp type and one renames it and
clarifies the ordering of the task list result.
Original PR for the timestamp type fix was:
https://github.com/a2aproject/A2A/pull/1288Fixes: #1287Fixes: #1206
---------
Co-authored-by: Yaroslav Shevchuk <yarolegovich@gmail.com>
Co-authored-by: Darrel <darrmi@microsoft.com>
Fixes#1258
### High level summary of changes:
- protocolVersion in AgentCard is now an array called protocolVersions
- Servers are expected to return UnsupportedVersionError if they get a
request with an A2A-Version header higher than they support.
- Clients are expected to fallback to a supported version if that is
acceptable to them. Tooling should help here.
- Not every minor version needs to be enumerated in the protocolVersions
array. 2.2 infers support for 2.1 and 2.0.
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Sam Betts <1769706+Tehsmash@users.noreply.github.com>
While this is a reserved word for proto itself, best practise is to
avoid field names that conflict with language (python etc) keywords, as
"message" isn't a language keyword this improves the consistency and
readability when using the types generated from the proto and avoids
needing to translate the name for JSON encoding.
Closes: #1230
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Darrel <darrmi@microsoft.com>
As v1.0 is a major release and may contain breaking changes this commit
cleans up the deprecated fields in the a2a.proto and references to this
in the spec doc.
Closes: #1227
Fixes naming inconsistency between the agent card property and the
GetExtendedAgentCard method. The property name now matches the method
naming convention.
- Updated proto definition: supports_authenticated_extended_card →
supports_extended_agent_card
- Updated all documentation references across specification.md and
llms.txt
- Maintains semantic meaning while improving consistency
Fixes#1215
Add scope field to the requests and AgentInterface, deprecate the three
fields defining transports in favor of a new supported_interfaces field.
fixes#1148
The ListTasksRequest message includes a google.protobuf.Struct metadata
field, which cannot be represented as simple URL query parameter
required by HTTP GET requests. This causes service config generation to
fail with `http: map field 'google.protobuf.Struct.fields' referred to
by message 'a2a.v1.ListTasksRequest`.
Since it's unclear whether metadata will be useful for ListTasks, I
propose to remove it at least for now to fix the specification.
Fixes#1236🦕
---------
Co-authored-by: Darrel <darrmi@microsoft.com>
In the currently published specification the data model definitions
include a proto snippet and then have a list of fields under the
snippet. This creates duplicated information. To prevent this
duplication while maintaining an easy to read presentation of the
abstract data models, this PR uses a Python macro to convert the proto
into a markdown table.
Also took the opportunity to do an editorial pass on the comments in the
a2a.proto before the field descriptions were removed from the
specification.md. Some of this content came from the types.ts file that
often had information that was not in a2a.proto.
A preview of the changes can be seen here
https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#41-core-objects
# Proto to Markdown Table Conversion
The macro system provides two main functions (`proto_to_table` and
`proto_enum_to_table`) that convert Protocol Buffer definitions into
formatted markdown tables:
1. **Locates Definitions**: Reads the `.proto` file and uses region
markers (`--8<-- [start:Name]` and `--8<-- [end:Name]`) to extract
specific message or enum definitions.
2. **Parses Structure**: Analyzes the proto content to separate three
sections:
- **Description**: Comments appearing before the message/enum
declaration
- **Fields/Values**: The actual field or enum value definitions with
their inline comments
- **Notes**: Comments appearing after the closing brace
3. **Extracts Field Details**: For each field, it captures:
- Field name (converted from snake_case to camelCase, or using
`json_name` annotation)
- Type (mapped to readable formats like "string", "array of integer",
"map of string")
- Required status (based on `REQUIRED` annotation or `optional` keyword)
- Description (from preceding comment lines)
4. **Generates Output**: Assembles the markdown output with:
- Description text at the top
- A formatted table with columns for Field/Type/Required/Description (or
Value/Description for enums)
- Special notes for `oneof` groups
- Additional notes from comments after the definition
The conversion automatically handles multi-line field definitions, map
types, repeated fields, and filters out protolint directives and region
markers from the output.
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Add missing fields to align gRPC specification with JSON specification:
- Add reference_task_ids field to Message to support cross-task context
references, matching the referenceTaskIds field in JSON spec
- Add state_transition_history capability flag to AgentCapabilities to
indicate support for task state transition history tracking
These changes ensure feature parity between gRPC and JSON-RPC
implementations of the A2A protocol. Both additions are optional fields
and maintain backward compatibility with existing implementations.
Fixes#1139Closes#1139
This PR resolves an inconsistency in the Message object property names
between the two transport protocols:
**Issue:**
- JSON-RPC (TypeScript): Used `parts: Part[]` for the array of content
parts
- gRPC (Protocol Buffers): Used `repeated Part content = 5;` for the
same field
**Solution:**
Updated the gRPC protocol buffer definition in
`specification/grpc/a2a.proto` to use `parts` instead of `content`,
aligning it with the JSON-RPC naming convention:
```proto
// Before
repeated Part content = 5;
// After
repeated Part parts = 5;
```
Also updated the associated comment to reflect the change from "Content
is the container..." to "Parts is the container...".
**Impact:**
- Ensures consistent property naming across both transport protocols
- Eliminates potential confusion for developers working with different
transports
- Maintains backward compatibility while improving developer experience
- No changes needed to existing JSON schema or TypeScript definitions
The fix is minimal and surgical, changing only the field name in the
gRPC definition to match the established JSON-RPC convention.
Fixes#1083.
<!-- START COPILOT CODING AGENT TIPS -->
---
💡 You can make Copilot smarter by setting up custom instructions,
customizing its development environment and configuring Model Context
Protocol (MCP) servers. Learn more [Copilot coding agent
tips](https://gh.io/copilot-coding-agent-tips) in the docs.
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: darrelmiller <447694+darrelmiller@users.noreply.github.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: Darrel <darrmi@microsoft.com>
# Description
Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make
sure it goes smoothly:
- [x] Follow the [`CONTRIBUTING`
Guide](https://github.com/a2aproject/A2A/blob/main/CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- [x] Ensure the tests and linter pass (Run `nox -s format` from the
repository root to format)
- [x] Appropriate docs were updated (if necessary)
- [x] Fix existing linting errors (I guess they were already on the main
upstream)
Fixes#761🦕
---------
Signed-off-by: Eden Reich <eden.reich@gmail.com>
Co-authored-by: Holt Skinner <holtskinner@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: Darrel <darrmi@microsoft.com>
Co-authored-by: Amye Scavarda Perrin <amye@amye.org>
## Summary
- Adds missing `metadata` field to the `Part` message in the gRPC
specification
- Fixes inconsistency between TypeScript/JSON and gRPC protocol
definitions
- Prevents data loss during Python ↔ gRPC conversions
## Problem
The `Part` message in `specification/grpc/a2a.proto` was missing the
`metadata` field that exists in the TypeScript and Python
specifications. This caused important metadata (like ADK function
call/response types) to be lost during conversions between Python and
gRPC representations.
## Solution
Added `google.protobuf.Struct metadata = 4;` to the `Part` message,
following the same pattern used by other proto messages in the
specification (Task, Message, Artifact, etc.).
Fixes#1005
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Reverts a2aproject/A2A#996
Fixes#1002
GetTaskRequest in the REST protocol is a GET. GET does not have request
body, and all fields in GET should be serializable to a query param.
metadata when being a struct cannot be serialized to query param, and
this is causing failure during API discovery doc generation `http: map
field 'google.protobuf.Struct.fields' referred to by message
'a2a.v1.GetTaskRequest' cannot be mapped as an HTTP parameter.`
# Description
According to the specification for `0.3.0` there is an optional icon url
in AgentCard, however this is not present in the provided protobuf spec.
~I didn't know which tag is preferred for this field, so I incremented
the highest tag found.~
Gemini helped notify me about the Next Tag comment.
Fixes#987🦕
We can push this when we release 0.3.0
Release-As: 0.3.0
---------
Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
# Description
This PR makes changes to our security representations in AgentCards:
1. Adds a new MutualTLSSecurityScheme type for indicating mTLS
connection requirements. This matches the same field in the OpenAPI
specification v3.1. This type is pretty lacking: there is no way to
indicate any requirements on the certificate that is presented by the
client. I expect we'll want to extend this in the future (for example,
we may want to allow an agent to indicate that a SPIFFE certificate must
be presented). For now, users are advised to put requirements in the
description field.
2. Adds a field for specifying a URL for OAuth2 provider metadata. This
is planned for OpenAPI Specification v3.2, which has not yet been
released. This allows clients to fetch additional information about the
OAuth provider, such as to discover if they support Dynamic Client
Registration.
3. Allows AgentSkills to specify a `security` field. This allows agents
to indicate security requirements for leveraging a particular skill.
I also clarified the usage and expectations for the `security` field in
the base AgentCard.
This change is marked backwards incompatible due to the addition of the
MutualTLSSecurityScheme, which adds a new type to an exhaustive enum
(the security scheme `anyOf`).
Release-As: 0.3.0
---------
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: Holt Skinner <holtskinner@google.com>
# Description
Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make
sure it goes smoothly:
- [ ] Follow the [`CONTRIBUTING`
Guide](https://github.com/a2aproject/A2A/blob/main/CONTRIBUTING.md).
- [ ] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- [ ] Ensure the tests and linter pass (Run `nox -s format` from the
repository root to format)
- [ ] Appropriate docs were updated (if necessary)
Fixes #<issue_number_goes_here> 🦕
---------
Co-authored-by: a2a-bot <a2a-bot@google.com>
# Description
This change adds support for a new JSON-RPC method
`agent/getAuthenticatedExtendedCard` for fetching authenticated extended
card.
This is only applicable if `AgentCard.supportsAuthenticatedExtendedCard`
bit is set to `true` that allows fetching authenticated context specific
agent card.
In the previous versions, the extended card was served via
`{AgentCard.url}/../agent/authenticatedExtendedCard` endpoint. This
endpoint is being removed in favor of the JSON-RPC method. This endpoint
will be deprecated in the SDKs and will be removed in a future release.
Release-As: 0.3.0
---------
Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
# Description
This introduces a `signatures` field on the AgentCard that contains JWS
formatted signatures. See issue #916 and discussion #199 for further
details, including how signatures are constructed and verified.
Fixes#916🦕