72 Commits

Author SHA1 Message Date
Darrel
032e67c46a
Merge branch 'main' into create-not-set 2025-12-01 14:23:45 -05:00
iliesicatrinel
b6ef9eec55
fix(spec): Remove metadata field from ListTasksRequest (#1235)
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>
2025-11-29 02:52:52 -06:00
Darrel Miller
1ab7f11789 docs(spec): Rename set push notification configuration methods to create to fix accidental change 2025-11-28 12:21:53 -05:00
Darrel
18ca2533bf
docs(spec): Updated specification to render data models as a table generated from the proto instead of a raw proto snippet (#1225)
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>
2025-11-25 09:11:28 -08:00
yuri
61d1e3a6f9
docs: Readme files accuracy fix (#1186)
## Problem
There are a couple of readme file with spelling, capitalization fixes to
align with rest of documents.


## Solution
“a2a specification” -> “A2A specification”.
“Helloworld” -> “Hello World”.


## Changes
docs/topics/a2a-and-mcp.md
docs/tutorials/python/4-agent-executor.md
docs/tutorials/python/7-streaming-and-multiturn.md
specification/grpc/README.md

## Testing
âś… Documentation builds successfully with mkdocs
âś… Markdown linting passes
âś… All internal anchor links verified
âś… No broken cross-references

## Issue
Fixes #1185

---------

Signed-off-by: Yuri Zhao <yu.zhao5@huawei.com>
2025-11-21 10:19:44 -06:00
Darrel
b078419954
docs(spec): Large refactor of specification to separate application protocol definition from mapping to transports. (#1160)
Related to #1151 

Fixes https://github.com/a2aproject/A2A/issues/998
Fixes https://github.com/a2aproject/A2A/issues/1091
Fixes https://github.com/a2aproject/A2A/issues/1072
Fixes https://github.com/a2aproject/A2A/issues/1058
Fixes https://github.com/a2aproject/A2A/issues/975
Fixes https://github.com/a2aproject/A2A/issues/1105
Fixes https://github.com/a2aproject/A2A/issues/989
Fixes https://github.com/a2aproject/A2A/issues/1189
Fixes https://github.com/a2aproject/A2A/issues/1187
Fixes https://github.com/a2aproject/A2A/issues/1177
Fixes https://github.com/a2aproject/A2A/issues/1180
Fixes https://github.com/a2aproject/A2A/issues/1172



In order to more effectively describe the A2A protocol in a consistent
way across different protocols, this PR refactors the specification to
describe the application protocol in a transport agnostic way, and then
have separate sections that describe how each of the transports map to
the abstract application protocol. To see a preview of what it looks
like you can go here
https://purple-moss-0838db51e.3.azurestaticapps.net/specification/

The goal of the TSC is to use the changes in this PR as the baseline for
a v1.0 Release Candidate. This will give SDK maintainers an stable
document to validate the changes in the specification through
implementations before v1.0 release.

There are many pending feature requests for the A2A specifications that
the TSC are supportive of. However, getting a stable, consistent,
unambiguous, multi-protocol specification is necessary before additional
features can be added safely.

## Document Restructuring 

- [A2A
Operations](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#3-a2a-protocol-operations)
are described independent of wire protocol
- [Protocol Data
Model](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#4-protocol-data-model)
is described using protobuf as source of truth. All other serializations
are derived from that.
- Protocol bindings (formerly described as transports) are now described
in their own sections
-
[JSON-RPC](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#9-json-rpc-protocol-binding)
-
[gRPC](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#10-grpc-protocol-binding)
-
[HTTP](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#11-httpjsonrest-protocol-binding)
- [Operation Parameters
](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#32-operation-parameter-objects)
describe structures reused across different operations
- [Operation
Semantics](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#33-operation-semantics)
describe common behavior patterns across operations

## New Sections

- [Requirements
Language](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#21-requirements-language)
- [Capability
Validation](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#334-capability-validation)
- [Abstract description of error
handling](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#332-error-handling)
- [Abstract description of
"headers"](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#325-headers)
-
[Extensions](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#46-extensions)
-
[Versioning](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#36-versioning)
- [Custom Binding
Guidelines](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#12-custom-binding-guidelines)
- [JSON Field Naming
Conventions](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#54-json-field-naming-convention)
- [Data Type
Conventions](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#55-data-type-conventions)
- [Security
Considerations](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#77-security-considerations)
- [Agent Card
Signing](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#84-agent-card-signing)
- [IANA
Considerations](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#13-iana-considerations)

## Protocol Clarifications

- Defining order for events returned from [Stream
Message](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#312-stream-message)
- [JSON
Examples](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#416-filepart)
provided for protobuf definitions of data model objects that previously
used discriminators
- Clarification of returned errors where multiple are applicable. e.g.
[Cancel
Task](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#315-cancel-task)
- Defined returned events and usage scenarios for
[Resubscribe](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#316-resubscribe-to-task)
- Defined protocol binding for errors using protocol native capabilities
for all bindings
-
[JSON-RPC](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#94-error-handling)
-
[gRPC](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#104-error-handling)
-
[HTTP](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#115-error-handling)
  
## Artifact Generation

The scripts have been changed to enable a2a.json to be generated from
the a2a.proto so that a2a.proto and specification.md are the only
normative source. Additional work is required to align the generated
a2a.json with the original one.

Release-As: 1.0

---------

Signed-off-by: Luca Muscariello <muscariello@ieee.org>
Signed-off-by: Luca Muscariello <lumuscar@cisco.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Sam Betts <1769706+Tehsmash@users.noreply.github.com>
2025-11-20 14:52:09 -05:00
madankumarpichamuthu
a2de7981ca
fix(grpc): missing field in gRPC spec - state_transition_history (#1138)
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 #1139 
Closes #1139
2025-10-19 10:05:42 -04:00
Copilot
2a1f819aaa
fix(grpc): Fix inconsistent property name between gRPC and JSON-RPC in Message object (#1100)
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>
2025-10-18 13:19:36 -04:00
Eden Reich
0a9f629e80
feat(spec): Add tasks/list method with filtering and pagination to the specification (#831)
# 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>
2025-10-16 12:47:20 -07:00
Holt Skinner
7d73a5766e
docs: Add gRPC Data Structures to Specification.md (#1040)
- Added region tags in gRPC proto for imports
2025-09-08 12:49:53 -05:00
Ioannis Papapanagiotou
b3b266d127
fix: Add missing metadata field to Part message in gRPC specification (#1019)
## 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>
2025-09-02 16:56:11 +00:00
hoonji
a8b45dcc42
fix(proto): Adds metadata field to A2A DataPart proto (#1004)
The Python DataPart class [has
metadata](e3a7207164/src/a2a/types.py (L285)),
but the proto doesn't. This leads to loss of important information
during Python->proto conversion; e.g. ADK embeds part types like
"function_call" and "function_response" [in the
metadata](https://github.com/google/adk-python/blob/main/src/google/adk/a2a/converters/part_converter.py#L207-L211).

Fixes #1005 🦕
2025-09-02 11:53:58 -05:00
Che Liu
e6b8c654a8
fix: Revert "chore(gRPC): Update a2a.proto to include metadata on GetTaskRequest" (#1000)
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.`
2025-08-22 10:03:15 -07:00
Shane Price
f0d48cdd5f
chore(gRPC): Update a2a.proto to include metadata on GetTaskRequest (#996)
# Description

https://a2a-protocol.org/latest/specification/#73-tasksget

JsonRPC supports this field while GRPC does not

Part of #998
2025-08-20 20:29:37 +01:00
Shane Price
17e7f62df9
fix(proto): Add icon_url to a2a.proto (#986)
# 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 🦕
2025-08-20 16:00:17 +01:00
Holt Skinner
911f9b059c
fix(grpc): Update CreateTaskPushNotificationConfig endpoint to /v1/{parent=tasks/*/pushNotificationConfigs} (#979)
Seems to have been a typo
2025-08-20 15:49:14 +01:00
Holt Skinner
00cf76e7bb
fix(spec): Suggest Unique Identifier fields to be UUID (#966) 2025-08-13 20:56:28 +01:00
Mike Smith
2b7cb6f840
fix: Add name field to FilePart protobuf message (#983)
This is present in the JSON-RPC spec and was missing from the gRPC
definition.

Fixes: #984
2025-08-13 16:48:03 +01:00
kthota-g
cab1bc3c96
chore(spec): clean up comments in gRPC spec (#959)
# Description

Fixes #861  🦕
2025-08-07 16:05:37 +01:00
kthota-g
8d57eba286
docs: Address typos in docstrings and docs. Fixes #940 (#941)
Fixes #940  🦕

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
2025-07-31 15:59:53 +01:00
dmandar
6a152a83ad
chore: Update default protocol version to 0.3.0 (#932)
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>
2025-07-30 14:57:35 +00:00
Mike Smith
e162c0c6c4
feat!: Add mTLS to SecuritySchemes, add oauth2 metadata url field, allow Skills to specify Security (#901)
# 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>
2025-07-29 13:39:27 -06:00
kthota-g
6fb2b771b0
ci: Trigger ci build for spec update (#936) 2025-07-29 19:50:41 +01:00
kthota-g
476863efa6
chore: Push to trigger spec update wf (#934)
# 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>
2025-07-29 11:16:51 -07:00
kthota-g
2cd7d98bc8
feat!: Add method for fetching extended card (#929)
# 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>
2025-07-29 09:31:45 -07:00
Israel Ekpo
074a3dd06b
docs: Update Docs to Clarify that Task Id Must Be Generated By the A2A Server (#926)
Fixes #925  🦕

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
2025-07-28 17:03:25 +01:00
Mike Smith
ef4a305053
feat: Add signatures to the AgentCard (#917)
# 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 🦕
2025-07-25 18:12:25 +00:00
Holt Skinner
23d5c5967b chore: Update spec from #910 2025-07-24 20:20:43 +01:00
Holt Skinner
e834347c27
fix(spec): Add Transport enum to specification (#909)
Adds Enum of supported Transports to Specification, with extensibility
for proprietary protocols.
Adds URL formatting requirement for `AgentInterface.url` and
`AgentCard.url`

Co-authored-by: Stefano Maestri <stefano.maestri@javalinux.it>
2025-07-24 19:56:39 +01:00
pstephengoogle
2eef3f6113
fix(spec): Add SendMessageRequest.request json_name mapping to message (#904)
Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: Holt Skinner <holtskinner@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
2025-07-23 14:41:14 -06:00
Holt Skinner
0c95b1fa8a
docs(spec): Improve docstrings in the specification (#887)
Co-authored-by: a2a-bot <a2a-bot@google.com>
2025-07-18 18:34:47 +01:00
kthota-g
6f1d17ba80
fix: Type fix and doc clarification (#877)
Release-As: 0.2.6

---------

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>
2025-07-17 17:10:05 +01:00
pstephengoogle
6ba72f0d51
fix: Update json names of gRPC objects for proper transcoding (#847) 2025-07-08 16:30:48 -04:00
Holt Skinner
32f3f9eb2e Revert "feat(spec): Add AGENT_CARD_WELL_KNOWN_URI to spec (#824)"
This reverts commit 66da9d10ee87dc1f8baa20a21360bebbe7d4ff1b.
2025-07-02 13:09:37 -05:00
Holt Skinner
66da9d10ee
feat(spec): Add AGENT_CARD_WELL_KNOWN_URI to spec (#824)
Prevents usage of "Magic Strings" in SDKs, which supports better
adherence to the recommended path for Agent Cards.

NOTE: This path might also need to be changed based on feedback in
https://github.com/protocol-registries/well-known-uris/issues/66 so
having a global constant would make this adjustment easier.

Fixes #816 🦕
2025-07-02 11:51:35 -05:00
bufdev
426f7a8833
chore: Add exceptions for buf lint and upgrade buf.yaml to v2 (#786)
This PR does a few cleanups to `buf.yaml`:

- Upgrades `buf.yaml` to
[`v2`](https://buf.build/blog/buf-cli-next-generation), which is what is
generally used going forward, and matches the `buf.gen.yaml` version. In
this case, virtually no changes.
- Adds lint exceptions for those lint rules that do not pass `buf lint`.
This now ensures that `buf lint` passes.
- Updates a few comments in `buf.yaml` for clarification.
- Updates the `README.md` to use `buf lint` instead of `buf build`. Note
that `buf build` is implicitly run via `buf lint`.
- Removes the instruction about checking for breaking changes, as
there's no mechanism for this set up yet. Happy to contribute a PR to
make this simple if this would be desirable.
- Removes the instruction to modify `buf.yaml`. `buf.yaml` should
generally never need modification.

---------

Signed-off-by: bufdev <bufdev-github@buf.build>
2025-07-02 10:42:07 -05:00
Holt Skinner
b3a725b97a
chore(spec): Add examples and fix spelling errors in proto (#823) 2025-07-02 10:37:41 -05:00
Holt Skinner
7fd0dcc6e4
chore(spec): Add default value for AgentCard.protocolVersion (#812)
- Prevents a breaking change in the Python Library
2025-06-30 15:19:55 -05:00
dmandar
90fa642094
feat(spec)!: Add a required protocol version to the agent card. (#802)
Add a new protocol version field to the agent card.

Release-As: 0.2.5
2025-06-30 15:04:16 -05:00
Holt Skinner
3590012159
chore(spec): Add @TJS-examples to spec and add missing Union Types (#810)
- **Replaced `@example` with `@TJS-examples`**: All JSDoc `@example`
tags have been converted to `@TJS-examples`, used
by`typescript-json-schema` to generate example values.
- **Completed Union Types**: The `JSONRPCResponse` union type was
incomplete. Added the missing `ListTaskPushNotificationConfigResponse`
and `DeleteTaskPushNotificationConfigResponse` types to make it
consistent with the defined request types.
2025-06-30 19:52:04 +00:00
Paulchen
16577ac6b3
format: update formatting (#798)
- update formatting settings for vscode
- format settings files
- remove whitespace
- remove empty not final new lines
2025-06-30 13:56:25 -05:00
kthota-g
147a675ba0
fix: Typo in delete push notif config (#782)
# 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> 🦕
2025-06-23 15:55:46 -07:00
Holt Skinner
08132ac5c7
docs: Repo Link Updates (#780) 2025-06-23 21:34:48 +02:00
Matteo Murru
419a497f68
docs: Add @TJS-examples for AgentProvider and AgentExtension interfaces (#758)
Add missing `@TJS-examples` annotations to `AgentProvider` and
`AgentExtension` interfaces to improve TypeScript developer experience.

Examples use Google ecosystem references (ai.google.dev, OAuth 2.0) and
follow existing JSDoc patterns in the codebase.

First contribution to open source ❤️
2025-06-23 13:08:53 +00:00
Holt Skinner
4a5e970ec2
fix(spec): Make AgentCard.additionalInterfaces Optional for backwards compatibility (#760)
The Python SDK expects a value for `additionalInterfaces` if this is not
optional. New versions would be a breaking change.

Unit test output

```
ERROR tests/client/test_client.py - pydantic_core._pydantic_core.ValidationError: 1 validation error for AgentCard
additionalInterfaces
  Field required [type=missing, input_value={'name': 'Hello World Age... tags=['hello world'])]}, input_type=dict]
```

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
2025-06-16 13:00:53 -05:00
Holt Skinner
14424a69d5
fix(spec): Fix casing of types.ts from #749 (#759)
Change from `snake_case` to `camelCase`
2025-06-16 12:46:59 -05:00
pstephengoogle
b35485e02e
feat: Add support for multiple transport announcement in AgentCard (#749)
This is designed to be backward compatible. Existing cards will work and
be correct with this update. New fields are added to the agent card and
default interpretation for these are provided to be backward compatible

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: Holt Skinner <holtskinner@google.com>
Co-authored-by: tomsun28 <tomsun28@outlook.com>
Co-authored-by: Mike Smith <mikeas@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: kthota-g <kcthota@google.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2025-06-16 11:13:44 -06:00
kthota-g
f355d3e922
feat: Support for multiple pushNotification config per task (#738)
- Support for list pushNotificationConfig for task
- Support for delete pushNotificationConfig
- Get pushNotificationConfig by id or by task
- update protos to use PushNotificationConfig

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
2025-06-14 14:10:46 -07:00
pstephengoogle
f506881c9b
fix: Address some typos in gRPC annotations (#747)
Fix transcoding typos

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: Holt Skinner <holtskinner@google.com>
2025-06-12 13:52:25 -04:00
Mike Smith
70f1e2b0c6
feat: Add protocol support for extensions (#716)
# Description

This updates the protocol to support Extensions. Extension profiles are
documents that describe modifications or additions to the core A2A
profile. AgentCards can declare supported extensions via
`capabilities.extensions`. This declaration can include additional
information via `capabilities.extensions.params`. Clients can use this
as a basis for extension negotiation: if a client supports an extension
that the server supports, the client can then follow the protocol
defined by the extension. This can include, but is not specifically
limited to:

1. Requiring specific structure of messages, such as following a
specific schema for a DataPart.
2. Providing additional information in request/response Message and
Artifact objects via their `metadata` field.
3. Exposing additional methods beyond the core A2A protocol methods.

Messages and Artifacts can now include an indication of which extensions
are present in their content. I do not yet know if extension indications
are necessary on other data structures (such as `MessageSendParams` or
`TaskStatus`). I'd say extension indications are not strictly necessary
at all: it's possible to infer that an extension was followed by
inspecting the message content itself (are the metadata fields you
expect present, does the DataPart follow the schema you expect, etc).
However, they are useful for validation and simplifying extension
implementation logic: "you said you followed this extension, so I'll
validate fields are present and then perform my processing".

Fixes #585

---------

Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
2025-06-04 10:17:37 -06:00