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.
A2A Docs
Developing A2A docs
- Clone this repository and
cdinto the repository directory - Run
pip install -r requirements-docs.txt - Run
mkdocs serve, edit.mdfiles, and live preview - Contribute docs changes as usual
How it works
- The A2A docs use mkdocs and the mkdocs-material theme
- All of the source documentation / Markdown files related to the A2A docs are
in the
docs/directory in the A2A repository mkdocs.ymlin the repository root contains all of the docs config, including the site navigation and organization- There is a GitHub Action in
.github/workflows/docs.ymlthat builds and publishes the docs and pushes the built assets to thegh-pagesbranch in this repository usingmkdocs gh-deploy --force. This happens automatically for all commits / merges tomain. - The A2A documentation is hosted in GitHub pages, and the settings for this are in the A2A repository settings in GitHub.
Building the Python SDK Documentation
The Python SDK documentation is built using Sphinx.
Prerequisites
Ensure you have installed the documentation dependencies:
pip install -r ../../requirements-docs.txt
Building the Docs
-
Run the following command to build the HTML documentation:
sphinx-build -b html docs/sdk/python docs/sdk/python/api -
The generated HTML files will be in the
sdk/python/apidirectory. You can opensdk/python/api/index.htmlin your browser to view the documentation.