# 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>
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馃
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>
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馃
- **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.
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 鉂わ笍
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>
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>
- 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>
# 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>
- Requires adding a new `PushNotificationConfig.id` field to support
multiple push notification callbacks per task
---------
Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: Holt Skinner <holtskinner@google.com>
New addition to the agentcard: Optional iconUrl field that can point to
an image icon file for the agent.
---------
Co-authored-by: a2a-bot <a2a-bot@google.com>
## Problem
In client-server messaging, the A2A protocol uses the [JSON-RPC
2.0](https://www.jsonrpc.org/specification) format, and the protocol
specification is written using the [JSON-Schema
specification](https://json-schema.org/). Fully complying with the
standards can help validate the payloads more accurately and help better
test different client and server implementations.
In addition to making the A2A spec more compliant with the mentioned
standards, changes in this PR are meant to fix a few minor bugs in the
A2A protocol spec (mismatches from what was implemented in the sample
A2A server and clients.
Addresses issue #353.
## Summary of changes
* Makes field "id" required on requests and responses. This field is
important because, according to the JSON RPC 2.0 spec, a message that
does not have an "id" is considered a notification, and the callee does
not have to send a response to such requests. Similarly, without the
"id" on the responses, the caller cannot correlate the responses to the
pending requests, meaning that fully JSON-RPC-compliant clients would
not be able to resolve such RPC calls.
---
*Edit: clearer wording + add issue references*
*Edit2: the scope of this PR has been reduced due to other updates
fixing parts of the spec, summary items were edited to reflect what has
already been addressed in other PRs.*
---
## (OLD) Summary of changes
* Add a missing definition for "TaskSendParams.acceptedOutputModes"
(described in #354). Fixed in #599.
* Remove "default" values for "const" fields. Compliance with JSON
schema, version `>=draft-6` and reduce ambiguity.
https://json-schema.org/understanding-json-schema/reference/const
Fixed in #599
* Make fields "jsonrpc" and "id" required on requests and responses.
Compliance with JSON-RPC 2.0.
* Make fields "error.code" and "error.message" required on errors. Fixed
in #599.
* In a few places, sort non-top-level dict keys to make them more
aligned with the pydantic JSON schema outputs. Since now, we are
discouraged from editing the spec manually, this item also drops out of
the scope of our concerns.
* The initial commit in this PR also included cleaning up several
unnecessary "null" types, which were addressed more thoroughly in #352.
## (OLD) Additional notes
While I sorted dictionaries within each model so that the keys of each
model would be in the same order as the pydantic-based scripts' exports,
at the same time, **I decided not to sort the top-level keys**
(`$defs/ModelKey`). Because doing so would make the diff ugly and harder
to read the applied changes. The top-level key sorting can be done
afterward.
---------
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: kthota-g <kcthota@google.com>
Use @a2a-bot to auto-generate `specification/json/a2a.json` whenever
`types/src/types.ts` is updated in a PR.
---------
Co-authored-by: a2a-bot <a2a-bot@google.com>
### Problem
Clients need to follow up or refine previously created tasks by agents.
### Proposal
**New Task in same contextId (Preferred)**
Context can be thought of as a larger goal from a client perspective.
Clients can use the same contextId from the previous task and send a
message for refinement or followup. Agents should spawn up new tasks.
Tasks cannot restart processing from terminal states (Completed, Failed
and Cancelled).
### Proposed API Change
* Addition of optional `referenceTaskIds` field in the `Message` object.
* Optional addition of `referenceArtifactId` in `part` metadata of
`Message` object.
# 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/google/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> 馃
# Description
feat: Optimize the camel case naming.
- [x] Follow the [`CONTRIBUTING`
Guide](https://github.com/google/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)
Co-authored-by: Andy Tian <tianxingzhivlog@gmail.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>