195 Commits

Author SHA1 Message Date
Holt Skinner
c24b1151d1
docs(spec): Update inconsistencies in documentation for 1.0 Spec (#1466)
In the future, we should probably explore refactoring the docs set to
avoid these becoming out of sync going forward

This pull request updates the project documentation to align with the
v1.0 Agent2Agent (A2A) Protocol Specification defined in
specification/a2a.proto. It ensures that all conceptual guides,
summaries, and tutorials reflect the current normative definitions,
  RPC method names, and wire formats.

  Summary of Changes


1. RPC Method Naming Updates
Standardized all method references to use the v1.0 PascalCase naming
convention:

   * `message/send` → `SendMessage`
   * `message/stream` → `SendStreamingMessage`
   * `tasks/get` → `GetTask`
   * `tasks/list` → `ListTasks`
   * `tasks/cancel` → `CancelTask`
* `tasks/pushNotificationConfig/set` →
`CreateTaskPushNotificationConfig`
   * `tasks/resubscribe` → `SubscribeToTask`
   * `agent/getAuthenticatedExtendedCard` → `GetExtendedAgentCard`

2. JSON Example & Wire Format Corrections
Updated examples across all "Topic" files and the Python Quickstart to
match v1.0 breaking changes:
* Removed `kind` discriminators: Examples for Message, Task, Part, and
StreamResponse now use member-based polymorphism (e.g.,
     {"text": "..."} instead of {"kind": "text", "text": "..."}).
* Enum Standardization: Changed role and state enums from
kebab-case/lowercase to SCREAMING_SNAKE_CASE with type prefixes (e.g.,
     `"ROLE_USER"`, `"TASK_STATE_COMPLETED"`).
* Response Wrapping: Updated examples to reflect that `SendMessage` and
`SendStreamingMessage` return a unified response object where
     the message or task is nested within the result.

  3. LLM Context (`docs/llms.txt`)
* Completely refreshed the protocol summary and RPC method list to
ensure LLM-based tools (like Gemini CLI) have an accurate
     representation of the v1.0 API surface and error codes.

  4. Link & Anchor Maintenance
* Updated internal documentation links and spans to point to the correct
sections in the specification.md (e.g., correcting the
     anchor for GetExtendedAgentCard).

  Why this is needed
The v1.0 release introduced significant structural improvements for
ProtoJSON compliance and architectural consistency. Documentation
examples were previously showing v0.3.0 patterns which would cause
integration errors for developers using the latest SDKs.
2026-02-10 11:45:49 -06:00
Ivan Shymko
3f6ad2d9d6
docs(spec): Fix MTLS scheme proto embedding (#1462)
Currently properties for `MutualTlsSecurityScheme` are not renderred
([source](https://a2a-protocol.org/latest/specification/#456-mutualtlssecurityscheme)):
<img width="1273" height="374" alt="image"
src="https://github.com/user-attachments/assets/be4c7dbb-749d-4391-aec8-fdd55c0dd625"
/>

This PR makes casing consistent for both mkdocs anchors and heading.

Tested via `mkdocs serve`:
<img width="1505" height="626" alt="image"
src="https://github.com/user-attachments/assets/348a6ef9-3868-43bf-8319-efe63092b95b"
/>

Re https://github.com/a2aproject/A2A/pull/1460#discussion_r2783691658
2026-02-10 18:17:45 +01:00
Ivan Shymko
741ccaa3af
docs(spec): Fix streaming examples (#1458)
1. Reference `StreamResponse` instead of duplicated and inconsistent
definitions in JSON-RPC and HTTP+JSON/REST message streaming protocol
bindings. Currently JSON-RPC example also contains outdated `/* Task |
Message | TaskArtifactUpdateEvent | TaskStatusUpdateEvent */` definition
which implies `kind` field.
2. Minor consistency fix:
```diff
-Referenced Objects:
+**Referenced Objects:**
```

Fixes #1459.
2026-02-09 16:21:26 +01:00
Darrel
ed97dea512
docs(spec): What changed from v0.3.0 to v1.0 (#1436)
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>
2026-02-05 12:23:18 -05:00
Kuba Herczyński
ce73987171
docs(spec): Fix wording around A2A-version header. (#1435)
fixes #1417

---------

Co-authored-by: Darrel <darrmi@microsoft.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
2026-02-05 09:05:49 -08:00
Darrel
6292104e35
fix(spec): Added clarification on timestamps in HTTP query params (#1425) 2026-01-29 15:09:21 -05:00
Luca Muscariello
b86d8bb2ed
docs: clean up documentation build chain and fix broken links (#1400)
- Move a2a.proto to specification/ root
- Update build scripts and macros to support new proto location
- Fix broken internal links and anchor references in specification.md
- Update .gitignore to properly exclude generated SDK docs
- Configure Sphinx to suppress external SDK warnings
- Fix MkDocs redirects and Python SDK toctree structure

---------

Signed-off-by: Luca Muscariello <muscariello@ieee.org>
2026-01-29 21:00:02 +01:00
Darrel
b03d141aea
fix(spec): Added clarifying text around messages and artifacts (#1424)
This pull request updates the A2A protocol specification to clarify the
distinction between Messages and Artifacts, and makes a minor adjustment
to protocol negotiation requirements.

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
2026-01-29 14:44:25 -05:00
Didier Durand
f6129cafa1
docs: fix some typos in various files. (#1198)
Hi,
As per title, fixing typos in various files: see commit diffs for
details
Cheers
Didier

---------

Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
2026-01-29 11:03:42 -06:00
madankumarpichamuthu
4dd980f6ff
fix(spec)!: Standardize spelling of "canceled" to use American Spelling throughout (#1283)
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>
2026-01-29 09:51:18 -06:00
madankumarpichamuthu
0655ff324a
fix: Clarify blocking calls return on interrupted states (#1403)
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>
2026-01-29 11:52:29 +01:00
Darrel
bfae8f7791
fix: Simplify Part message structure by flattening FilePart and DataPart (#1411)
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>
2026-01-28 17:48:33 +01:00
madankumarpichamuthu
810eaa1c6e
docs(spec)!: Align enum format with ADR-001 ProtoJSON specification (#1384)
Updates specification to use ProtoJSON enum format
(SCREAMING_SNAKE_CASE) instead of kebab-case, aligning with ADR-001
decision.

Changes:
- Updated Section 5.5 enum value formatting rules
- Added reference to ADR-001 and ProtoJSON specification
- Updated all JSON examples to use SCREAMING_SNAKE_CASE enums:
  - Role enums: user -> ROLE_USER, agent -> ROLE_AGENT
- Task state enums: working -> TASK_STATE_WORKING, completed ->
TASK_STATE_COMPLETED, etc.

This aligns the specification with the TSC-approved ADR-001 decision to
leverage ProtoJSON for JSON serialization.

Fixes #1344

Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Amye Scavarda Perrin <amye@amye.org>
2026-01-27 09:53:46 -08:00
Darrel
3e6c7db907
fix(spec): Fix/1251 clarify authentication scheme (#1256)
Fixes #1251

---------

Co-authored-by: Luca Muscariello <muscariello@ieee.org>
2026-01-27 09:39:39 -08:00
madankumarpichamuthu
5b101cce0f
refactor(spec)!: Remove redundant final field from TaskStatusUpdateEvent (#1308)
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>
2026-01-27 09:07:50 -08:00
Vinay Ramesh
19e2059852
docs: provide clarity in task id specification to address #1406 (#1407)
# Description
Provides clarity on server generated task ids in the specification
documentation to address underspecification of Message payloads and
expected error handling.

Fixes: #1406

Co-authored-by: Darrel <darrmi@microsoft.com>
2026-01-27 09:06:05 -08:00
hugo-romero-mm
229d005bff
docs(partners): Add MasOrange to partners list (#1409)
Hi A2A Team,
I’d like to submit [MasOrange](https://masorange.es/en/) to be added to
the A2A partners list: https://a2a-protocol.org/latest/partners/

A2A integration: We are working with A2A as a core building block for
agent discovery and agent-to-agent interoperability across our
ecosystem. We also maintain ongoing discussions with Google on
A2A-related topics, including Gemini Enterprise integrations and agentic
cloud capabilities, providing them direct feedback. We are implementing
A2A as the default protocol for exposing and connecting agentic systems
within MasOrange, adapting its usage to our security and governance
requirements, with future potential benefits for the OSS community.


Best regards,
Hugo Romero, AI Engineer at MasOrange

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
2026-01-26 09:41:30 -08:00
Ivan Shymko
bb527d4299
docs: Bring back Python SDK reference (#1415)
Currently [`SDK Reference >
Python`](https://a2a-protocol.org/latest/sdk/python.md) link gives 404:

<img width="1138" height="308" alt="image"
src="https://github.com/user-attachments/assets/2bd3bda0-0536-4450-8e82-5ec9ee5ce044"
/>

1. Fix the link to open
[this](https://a2a-protocol.org/latest/sdk/python/api/index.html)
instead. This was setup in #949 and is generated automatically from the
latest docs. Looks like it was accidentally changed to `python.md` (the
one not used ever before, it used to be `python/index.md`) in #1160.
2. Fix redirect to use absolute URL with `latest`. This is required due
to https://github.com/mkdocs/mkdocs-redirects/issues/18, current way
isn't going to work. `v0.3.0` tag of the website (the one you get after
clicking `Latest Released Version` from
[here](https://a2a-protocol.org/latest/specification/)) doesn't have the
generated documentation either way, see
[here](https://github.com/a2aproject/A2A/tree/gh-pages/v0.3.0/sdk/python).
3. Replace `Google LLC` with `The Linux Foundation` in the generated SDK
reference.
4. Update copyright year in both places.

Tested via `mkdocs serve`.

Fixes #1347.
2026-01-26 10:12:40 -06:00
madankumarpichamuthu
d14f410711
fix: Restore CreateTaskPushNotificationConfig method naming (#1402)
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>
2026-01-25 11:42:23 -05:00
madankumarpichamuthu
4befaeacaf
docs: Remove v1 from HTTP binding URLs in specification (#1383)
Updates specification documentation to align with proto file changes by
removing /v1/ prefix from all HTTP REST endpoint URLs.

Changes:
- Updated all HTTP endpoint examples (POST, GET, DELETE)
- Updated API operation reference table
- Removed /v1/ from 41 occurrences throughout the specification

Fixes #1350
2026-01-20 09:19:25 -08:00
Jeff Mesnil
f9a8f5b85d
fix(spec): Update security schemes example (#1364)
Update security scheme example to use the correct key for the security
schemes instead of the `type` field.

This fixes #1355

Signed-off-by: Jeff Mesnil <jmesnil@redhat.com>
2026-01-15 11:32:26 -05:00
madankumarpichamuthu
40d6286fbe
refactor(spec)!: Move extendedAgentCard field to AgentCapabilities (#1307)
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>
2026-01-14 08:41:30 -05:00
Sam Betts
0e204bf878
fix(spec)!: Fixes for the last_updated_after field (#1358)
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/1288

Fixes: #1287
Fixes: #1206

---------

Co-authored-by: Yaroslav Shevchuk <yarolegovich@gmail.com>
Co-authored-by: Darrel <darrmi@microsoft.com>
2026-01-14 08:34:02 -05:00
Mauro Sardara
525ff38e5f
feat(spec)!: modernize oauth 2.0 flows - remove implicit/password, add device code / pkce (#1303)
## Description

Modernizes OAuth 2.0 flow support by removing deprecated
flows and adding modern, secure alternatives.

Fixes: #1234 

## Changes

### Breaking Changes

**Removed (deprecated by OAuth 2.0 Security BCP):**
- `ImplicitOAuthFlow` - Use Authorization Code + PKCE instead
- `PasswordOAuthFlow` - Use Authorization Code + PKCE or Device Code
instead

### Added

**New OAuth Flow:**
- `DeviceCodeOAuthFlow` (RFC 8628) - For CLI tools, IoT devices, and
input-constrained scenarios

**Enhanced Security:**
- `pkce_required` field added to `AuthorizationCodeOAuthFlow` (RFC 7636)

Co-authored-by: Darrel <darrmi@microsoft.com>
2026-01-13 22:24:49 -05:00
Darrel
a4afeea788
fix(spec): Clarify versioning strategy and client responsibilities in protocol specification (#1259)
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>
2026-01-13 22:10:38 -05:00
Vinay Ramesh
e8c0f0fd61
docs(spec): patched security scheme and add anchor tag for Security (#1279)
Minor patch to `security_scheme` reference to `securityScheme` and added
a missing anchor tag for `Security`. Another docs change should be added
to clarify usage of `Security`. Opened
https://github.com/a2aproject/A2A/discussions/1278 for clarification.

Fixes https://github.com/a2aproject/A2A/issues/1280

Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Darrel <darrmi@microsoft.com>
2026-01-12 13:34:26 -05:00
Didier Durand
cc8e67ebea
docs: fixing some typos in various files (#1310)
Hi,
Giving a second read to the repo, I found these additional typos: see
commit diffs.
Didier

---------

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>
2026-01-08 08:55:51 -08:00
Sam Betts
60f83c3faa
fix(spec)!: Remove deprecated fields from a2a.proto for v1.0 release (#1301)
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
2026-01-06 11:29:53 -05:00
Kuba Herczyński
a336a5a484
fix(spec): Clarify contextId behavior when message is sent with taskId but without contextId (#1309)
Fixes #1249.

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
2025-12-24 11:33:17 -05:00
William Wang
d803564477
doc: add amikonet to partners list (#1316)
Hi A2A Team,

I would like to submit AmikoNet (https://amikonet.ai/) to be added to
the A2A partners list.

About AmikoNet: AmikoNet is the first social network where AI agents and
humans interact as equals.

Our platform enables AI agents to have their own profiles(which include
its agent card), create content, and collaborate with both humans and
other agents. All content is stored in markdown format optimized for AI
agent consumption.

A2A Integration: We use Google A2A as our core protocol for agent
discovery, allowing autonomous agents to find and connect with each
other across our network. This makes AmikoNet a natural fit for the A2A
ecosystem.

We're excited to be part of the A2A community and help advance the
standard for AI agent collaboration.

Best regards,

William
Amiko Team
2025-12-18 13:00:44 -08:00
Holt Skinner
1a2d580a3e
docs: Update COMMUNITY.md (#1312)
- Removed previous events section from community documentation.
- Updated list of A2A Integrations
2025-12-15 11:59:10 -06:00
Didier Durand
dec450b3c4
docs: fix typos in specification.md (#1304)
Hi,
Recent changes in in specification.md brought some typos: this PR fixes
them.
See commit diffs for details.
Didier
2025-12-11 09:30:47 -06:00
kadirpekel
290c87f0c2
docs: Add Hector to A2A Protocol Integrations (#1129)
This PR adds Hector to the A2A integrations list. Hector is a pure
A2A-native declarative AI agent platform written in Go that enables
building powerful agents through YAML configuration alone, with zero
code required. Unlike other frameworks that retrofit A2A support, Hector
is built from the ground up on the A2A protocol specification, providing
100% compliance with agent discovery, task execution, streaming (SSE),
and session management. Its unique value proposition is seamless
integration of external A2A agents via simple YAML configuration (type:
"a2a", url: "https://agent-url"), enabling true multi-agent
orchestration across heterogeneous systems and demonstrating the full
potential of A2A interoperability.

Homepage: https://gohector.dev
Repository: https://github.com/kadirpekel/hector

Would love to see Hector to the A2A integrations list if you also agree.
I believe it demonstrates the protocol's potential for true agent
interoperability.
2025-12-10 16:12:16 +00:00
Holt Skinner
f74fe490a8 docs: Fix broken link to Python SDK Docs 2025-12-05 14:19:17 -06:00
Andrew Wickham
c56ea72d5b
docs: Update A2A-Extensions header to align with current standard (#1248)
Replace the `X-A2A-Extensions` header with `A2A-Extensions` to align
with rfc6648.

Fixes #1238
2025-12-05 13:01:13 -06:00
madankumarpichamuthu
c42ef44805
docs: Remove deprecated kind discriminators from Life of a Task example (#1224)
Removes usage of deprecated 'kind' discriminators from the Life of a
Task documentation to align with v1.0 specification changes.

Changes:
- Removed 'kind' field from Part objects (4 occurrences) - deprecated in
v1.0 per spec section A.2.1
- Removed invalid 'kind' field from Task objects (2 occurrences) - never
part of Task specification
- Updated Part field names: mimeType → mediaType, bytes → fileWithBytes

The specification (section A.2.1) states that v1.0 removed the 'kind'
discriminator for Part types and streaming events, using JSON member
names as discriminators instead. Task objects never had a 'kind' field
in the proto definition.

Fixes #1220
2025-12-05 18:57:32 +00:00
madankumarpichamuthu
c196824396
fix(spec)!: Rename supportsAuthenticatedExtendedCard to supportsExtendedAgentCard (#1222)
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
2025-12-05 18:54:19 +00:00
madankumarpichamuthu
8704c88a72
docs: Clarify push notification payload format in topics documentation (#1223)
Fixes inconsistency between topics and specification documentation
regarding push notification payloads. The topics documentation
previously stated the payload was not strictly defined, while the
specification explicitly defines it as StreamResponse format.

- Updated docs/topics/streaming-and-async.md to specify StreamResponse
format
- Added references to specification sections for detailed structure
- Aligns with specification.md sections 3.1.7 and 4.3.3

Fixes #1216
2025-12-05 12:15:20 -06:00
iliesicatrinel
d381cea9d0
docs(spec): Update specification to use proto_to_table macro for all core operations (#1242)
We should use the proto_to_table macro for describing inputs/outputs of
operations to avoid having to modify the specification manually after
protobuf definition changes.

Other changes:
- small updates to capitalization/markdown annotations to ensure
consistency with the rest of the specification
- modified proto_to_table to return `None` string if proto is empty
(e.g. `GetExtendedAgentRequest`). We should use macro for this request
even if it's empty, because we may add fields
(https://github.com/a2aproject/A2A/pull/1195).

Fixes https://github.com/a2aproject/A2A/issues/1243 🦕

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Darrel Miller <darrel.miller@microsoft.com>
2025-11-28 16:01:09 -05:00
Emmanuel Hugonnet
5792804372
fix(doc): Makes JSON-RPC SendMessage response clearer (#1241)
Fixing issue #1240 by providing something more in line with what is
expected.

Fixes https://github.com/a2aproject/A2A/issues/1240 🦕

---------

Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
2025-11-26 15:36:32 -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
Martin Harrigan
d8dd640d2b
docs: fix conflicting description of artifact name (#1153)
The heading says the artifact name is updated but the following text and
JSON shows that it remains the same.
2025-11-21 17:21:39 +00: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
Ben Clarke
0534ba6a9e
docs: add A2A Net to partners list (#1201)
Added A2A Net to the list of partners.
2025-11-13 08:59:26 -08:00
YoTaro (Yot) Watanabe
b069cc7b19
docs Add NTT DATA to partners list (#1200)
Update partners with NTT DATA

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
2025-11-11 15:34:05 -08:00
Ivan Cheung
7c8181e045
docs: Updated references to Go (#1202) 2025-11-11 15:37:02 -06:00
Farah Juma
202aa069e6
fix: Update the Java tutorials and descriptions (#1181)
Updating the Java section for the Tutorials page to list the current
samples.

Fixes https://github.com/a2aproject/A2A/issues/1182
2025-10-29 10:43:03 -07:00
alan blount
6fd5c38914
docs: updated a2a logo SVGs (#1184) 2025-10-29 10:20:59 -05:00
chitra-venkatesh
db8e55c044
Doc Update partners.md (#1178)
Update partners with ParkourSC
2025-10-26 16:57:53 -07:00