231 Commits

Author SHA1 Message Date
Yaroslav
757f0ec6d0
fix(spec): recent transcoding-related error changes (#1627)
Fix error code mappings table so that http codes correspond to
[`google.rpc.Code`](https://github.com/googleapis/googleapis/blob/master/google/rpc/code.proto#L32)-defined
mappings.

Undo changes made in https://github.com/a2aproject/A2A/pull/1600 to
jsonrpc error handling section. The changes made were meant to address
http-grpc transcoding compatibility. I don't see a convincing reason for
forcing jsonrpc error data format, so I assume JSONRPC section was
updated by mistake.

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

---------

Co-authored-by: Darrel <darrmi@microsoft.com>
Co-authored-by: Mike Smith <mikeas@google.com>
2026-04-14 15:37:40 -04:00
Holt Skinner
8dda73b3b4
docs: Add Rust SDK to list of official SDKs (#1729)
- Change table header to include repository instead of stability (all
are currently stable)

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Sampath Kumar <sam1990kumar@gmail.com>
2026-04-09 08:38:46 +00:00
Iva Sokolaj
b9f03d4c96
docs: update code snippet markers to match refactored sample identifiers (#1732)
Fixes:
https://a2a-protocol.org/latest/tutorials/python/6-interact-with-server/#understanding-the-client-code

Sample update: #508
2026-04-09 09:55:38 +02:00
Amye Scavarda Perrin
43bddf8cc1
[Feat]: New logos + mascot (#1719)
Co-authored-by: Darrel <darrmi@microsoft.com>
2026-04-07 13:09:37 -04:00
Sampath Kumar
3c0e23e996
docs: fix table duplication in A2A Specification document (#1704) 2026-04-07 10:13:34 -05:00
Sam Betts
66df070988
docs: Add custom protocol bindings documentation (#1619)
## Summary

- Adds `docs/topics/custom-protocol-bindings.md`, a dedicated page
documenting custom protocol bindings as a concept distinct from
extensions; covers declaration in the Agent Card, specification
requirements, key areas to address (data type mappings, service
parameters, error mapping, streaming, authentication), and
interoperability testing
- Adds `docs/topics/extension-and-binding-governance.md`, merging the
governance content previously in `extensions.md` with the equivalent
custom protocol binding governance; deduplicates the tiers section into
a single section with a naming table; notes that SDKs SHOULD implement
official custom protocol bindings vs MAY for extensions
- Adds spec section 5.8 defining URI-based custom binding identification
as a SHOULD requirement and updates the section 12.7 Agent Card example
accordingly
- Replaces the verbose inline governance sections in `extensions.md` and
`custom-protocol-bindings.md` with short summaries linking to the new
governance page
- Adds Custom Protocol Bindings and Extension & Binding Governance to
the mkdocs.yml nav

---------

Signed-off-by: Sam Betts <1769706+Tehsmash@users.noreply.github.com>
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-04-07 13:31:18 +02:00
alan blount
f991a08f2c
docs: add Community SDKs (#1698)
## Summary

Add a Community SDKs section to the Community Hub page listing
community-maintained A2A SDK implementations for languages not covered
by official SDKs.

Fixes #1602

## Changes

- **Updated: `docs/community.md`** — inline SDK directory section with
listings and submission requirements
- **Updated: `mkdocs.yml`** — cleaned up nav
- **Updated: `.github/actions/spelling/allow.txt`** — added GitHub
usernames

## Initial Listings

| Language | Repository | Package | Spec Version |
|----------|-----------|---------|-------------|
| 🦀 Rust | [tomtom215/a2a-rust](https://github.com/tomtom215/a2a-rust) |
[crates.io](https://crates.io/crates/a2a-protocol-sdk) | 1.0.0 |
| 🦀 Rust | [EmilLindfors/a2a-rs](https://github.com/EmilLindfors/a2a-rs)
| [crates.io](https://crates.io/crates/a2a-rs) | 0.3.0 |
| 🍎 Swift |
[tolgaki/a2a-client-swift](https://github.com/tolgaki/a2a-client-swift)
| SPM | 1.0.0 |
| 💧 Elixir |
[actioncard/a2a-elixir](https://github.com/actioncard/a2a-elixir) |
[hex.pm](https://hex.pm/packages/a2a) | 0.2.0 |

## Context

Community SDKs are emerging (see
[#1638](https://github.com/a2aproject/A2A/issues/1638) for the Rust
SDK), but there was no place in the docs for users to discover them.
Rather than a standalone page, these are inlined as a section on the
Community Hub for better discoverability.

---------

Co-authored-by: Zaf (AI Assistant) <zaf@0-a.org>
2026-03-31 09:43:27 -07:00
petterlindstrom79
5ac9d2c7d7
docs: add Strale to partners list (#1702)
Adds [Strale](https://strale.dev) to the A2A partners list.

Strale is an API capability marketplace for AI agents with a live A2A
implementation:

- **Agent Card**: https://api.strale.io/.well-known/agent-card.json
- **A2A endpoint**: `POST https://api.strale.io/a2a` (JSON-RPC:
`message/send`, `tasks/get`)
- **273 skills** across compliance, company data (27 countries),
financial validation, Web3/DeFi, and developer tools
- **Link header** on all responses: `Link:
</.well-known/agent-card.json>; rel="agent-card"`

Also accessible via MCP (Streamable HTTP), REST API, and x402 (USDC
micropayments on Base).
2026-03-30 07:35:29 -07:00
ivoshemi-sys
72d1459ddb
Add OIXA Protocol to partners list (#1692)
## Summary

[OIXA Protocol](https://oixa.io) is a live open protocol where AI agents
hire and pay other AI agents autonomously — built on A2A for agent
communication, with economic guarantees on Base Mainnet.

## How OIXA uses A2A

OIXA builds directly on A2A as the communication layer for agent
discovery and task coordination. It publishes a standard A2A agent card:

```
http://64.23.235.34:8000/.well-known/agent.json
```

**Protocol stack:**
- **COMMS:** A2A + MCP — agent discovery and task protocol
- **PAYMENT:** x402 Protocol — autonomous HTTP payments
- **FUNDS:** Base Mainnet + USDC — trustless on-chain escrow
- **REGISTRY:** ERC-8004 — on-chain agent identity

## What OIXA adds on top of A2A

A2A defines *how* agents communicate. OIXA defines *how they transact*
when that communication leads to work that should exchange value:

- Reverse auction discovery: agents bid to complete tasks (lowest bid
wins)
- On-chain USDC escrow: funds lock at bid acceptance, release
automatically on verified delivery
- Cryptographic output verification: not just delivery confirmation but
quality verification
- Stake-based anti-Sybil: 20% stake per bid makes economic attacks
impossible
- On-chain reputation: every completed A2A transaction builds a
verifiable score

## Links

- Site: https://oixa.io
- GitHub: https://github.com/ivoshemi-sys/oixa-protocol
- SDK: `pip install oixa-protocol` (LangChain, CrewAI, AutoGen,
Haystack, MCP)
- Live API: http://64.23.235.34:8000/docs
- A2A agent card: http://64.23.235.34:8000/.well-known/agent.json

Co-authored-by: Openclaw <Openclaw@Mac-mini-de-Ivan.local>
2026-03-27 09:37:45 -07:00
Iva Sokolaj
32a7d3a0bd
docs: update python tutorial for a2a-sdk v1.0.0-alpha.0 (#1678)
Issue: #1679

# Description

[a2a-samples/python](https://github.com/a2aproject/a2a-samples/tree/main/samples/python)
is being updated to use the new `v1.0`:
[samples-#462](https://github.com/a2aproject/a2a-samples/issues/462). We
are looking to merge [update helloworld sample to
v1.0-alpha](https://github.com/a2aproject/a2a-samples/pull/474) and
consequently need to update python tutorial in A2A as it references the
`helloworld sample`.

# Key Changes
- **Agent Skills & Card** (3-agent-skills-and-card.md): Updated the docs
to match the new AgentCard schema. Replaced the legacy `url` property
with `icon_url`, documented the new `supported_interfaces` field for
protocol bindings, and added mentions of the extended_agent_card
capability.
- **HelloWorldAgentExecutor logic** (4-agent-executor.md): Rewrote the
walkthrough for the execute method to reflect the modern event-driven
approach and to make the difference between non-streaming and streaming
more clear. It now explicitly describes enqueueing Task,
TaskStatusUpdateEvent (with `TASK_STATE_WORKING`),
TaskArtifactUpdateEvent, and TaskStatusUpdateEvent (with
`TASK_STATE_COMPLETED`) instead of single string messages.
- **Server Setup** (5-start-server.md): Replaced `0.0.0.0` with
`127.0.0.1` in the host binding tutorial and log examples to enforce
safer local testing defaults.
- **Client Interaction** (6-interact-with-server.md): 
- Replaced MessageSendParams dictionaries with native protobuf
`Message/Part/Role` construction.
- Replaced direct A2ACardResolver instantiation with the new
`ClientFactory` approach.
- Unified the documentation around `send_message` (which now handles
streams dynamically based on `config` and agent capabilities) and
updated expected log outputs.
2026-03-26 13:50:49 +01:00
Alex
3c1a5ff473
docs: add WritBase to partners list (#1634)
Closes #1636

Adds [WritBase](https://github.com/Writbase/writbase) to the A2A
partners list.

WritBase is an MCP-native task management control plane for AI agent
fleets — Postgres-backed, multi-tenant, with full provenance tracking.
It includes bidirectional A2A↔WritBase status mapping alignment and
supports inter-agent task delegation with assignment tracking and
delegation safety.
2026-03-16 11:18:55 -07:00
Darrel
4f77f1bdd0
docs: Blog post announcing V1.0 (#1621)
Co-authored-by: Amye Scavarda Perrin <amye@amye.org>
Co-authored-by: ToddSegal <10716715+ToddSegal@users.noreply.github.com>
2026-03-12 17:02:05 +00:00
Holt Skinner
6845a87b50
docs: Update Specification.md for 1.0.0 from release candidate (#1620) 2026-03-12 11:47:56 -05:00
Copilot
087604615d
docs: fix inconsistent HTTP method for list tasks examples in specification (#1613)
Fixes #1612

Section 6.5 examples used `POST /tasks/list` with a JSON body,
contradicting section 11.3.2 which correctly defines list tasks as `GET
/tasks` with query parameters.

## Changes

- **`docs/specification.md` — Section 6.5 (Task Listing and
Management):** Updated all four HTTP examples to use `GET /tasks` with
query parameters instead of `POST /tasks/list` with a request body:

  | Example | Before | After |
  |---|---|---|
| All tasks from a specific context | `POST /tasks/list` + JSON body |
`GET /tasks?contextId=...&pageSize=10&historyLength=3` |
| All working tasks across all contexts | `POST /tasks/list` + JSON body
| `GET /tasks?status=working&pageSize=20` |
| Pagination | `POST /tasks/list` + JSON body | `GET
/tasks?contextId=...&pageSize=10&pageToken=...` |
| Validation error | `POST /tasks/list` + JSON body | `GET
/tasks?pageSize=150&historyLength=-5&status=running` |

Enum values in query parameters now use the short form (e.g.,
`status=working`) per the field type handling rules already defined in
section 11.5.

<!-- START COPILOT CODING AGENT TIPS -->
---

✨ Let Copilot coding agent [set things up for
you](https://github.com/a2aproject/A2A/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot)
— coding agent works faster and does higher quality work when set up for
your repo.

---------

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: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Darrel <darrmi@microsoft.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
2026-03-12 11:30:50 -05:00
Ritsuki Yamada
727168fe1f
docs(spec): Add HTTP caching guidance for Agent Card endpoints (#1479)
Closes #1478. Related to #306.

The specification provides caching guidance for Extended Agent Cards
(Sections 3.1.11 and 13.3) but has no equivalent guidance for public
Agent Cards. This creates a gap for SDK and framework implementers —
none of the five official SDKs currently implement Agent Card caching,
and framework implementers have noted the lack of protocol-level
guidance (google/adk-python#3297).

This PR adds SHOULD-level HTTP caching guidance, following the precedent
of OpenID Connect Discovery 1.0 (same `.well-known` URI pattern).

**Changes:**

- **`docs/specification.md`**: Add Section 8.6 "Caching" with normative
guidance on `Cache-Control`, `ETag`, and conditional requests. Placed
after Section 8.5 (Sample Agent Card) to avoid renumbering existing
sections and breaking anchor links.
- **`docs/topics/agent-discovery.md`**: Add "Caching Considerations"
section with practical guidance for implementers.

---------

Co-authored-by: Darrel <darrmi@microsoft.com>
2026-03-12 16:24:35 +00:00
Kuba Herczyński
149cb82d38
docs: Fixes to the "what's new in v1" docs. (#1616) 2026-03-12 16:22:50 +00:00
Mike Smith
7415773696
refactor(spec): Update HTTP+JSON error mapping to use google.rpc.Status AIP-193 (#1600)
Updates the specification to require use of `google.rpc.Status`
formatted JSON objects for error response bodies in HTTP+JSON mapping.

See related issue for reasoning.

Fixes #1596

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Darrel <darrmi@microsoft.com>
2026-03-12 09:15:26 -07:00
Sunil Prakash
0833a5f5fd
docs: add JamJet to partners list (#1615)
## Summary

- Adds [JamJet](https://github.com/jamjet-labs/jamjet) to the partners
list in alphabetical order
- JamJet is an open-source agent-native runtime with native A2A client +
server support built in Rust

Closes #1602

---------

Co-authored-by: Amye Scavarda Perrin <amye@amye.org>
2026-03-11 10:21:20 -07:00
Vinay Ramesh
e2eb7d2b4b
docs: Extension governance (#1488)
Brings extension governance from issue #1406 into A2A documentation spec

Closes #1406

---------

Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Kuba Herczyński <herczyn@google.com>
Co-authored-by: Sam Betts <1769706+Tehsmash@users.noreply.github.com>
2026-03-11 13:44:49 +01:00
Amye Scavarda Perrin
2c9bc7ecd9
docs: Update roadmap.md (#1610)
Update roadmap to forthcoming 1.0 release

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
2026-03-10 11:44:17 -07:00
Mike Smith
477a0ee304
docs: Expand details on In-Task Authorization. (#1597)
The previous wording was very barebones. We have explored this area
significantly more, and the specification now reflects further guidance
on how to handle retrieving authorizations and credentials during Task
processing.

This specifically addresses the missing guidance on how clients are
expected to respond to a Task in `TASK_STATE_AUTH_REQUIRED`.

Fixes #1582.

---------

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-03-10 13:16:01 -04:00
Ivan Shymko
601c408aec
refactor(spec): rename SendMessageConfiguration.blocking to SendMessageConfiguration.return_immediately (#1507)
As mentioned in the linked issue, defaulting to non-blocking behavior is
counterintuitive and is implemented the opposite way in the SDKs.

Renaming it to `return_immediately` makes default behavior simpler while
advanced scenario requires an extra flag.

---
Previos proposals:
1. `polling` has inaccurate meaning in this context as pointed out in
the comments.
2. `non_blocking` is a negative boolean which leads to confusing
conditional expressions (`not non_blocking`).

Fixes #1453

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
2026-03-10 17:06:43 +01:00
Kuba Herczyński
dec790aa06
fix(docs): Clearer wording around context id. (#1588)
client side context id passing can be supported, server can choose to
reject, client's should know how to fallback accordingly
if server accepts, server must respond with the context id
if server cannot accept client side context id it MUST respond with an
error (i.e. it SHOULD not respond with a task with a different context
id?)
servers may not accept a client side context id for a number of reasons:
clashes, validation errors, not supporting context ids

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
2026-03-05 12:33:36 +01:00
AgentTrust.ai
dbb1bf8e60
docs: add AgentTrust to partners list (#1568)
This PR adds [AgentTrust](https://agenttrust.ai) to the partners list,
alphabetically between AG2AI and AI21 Labs.

**About AgentTrust:**
AgentTrust is trust and identity infrastructure for agentic
collaboration. We provide hosted A2A endpoints with Agent Card
discovery, Ed25519 message signing, human-in-the-loop escalation, and
prompt injection detection.

**What we've built:**
- Hosted A2A endpoints — agents get a public A2A identity at
`/a2a/{slug}` without running a server
- Standard Agent Card served at `/.well-known/agent.json` per agent
- Direct A2A JSON-RPC ingress (`tasks/send`) with allowlist,
InjectionGuard, and HITL rules
- Ed25519 message signing — cryptographic identity verification between
agents
- Negotiation lifecycle extending A2A task states via metadata
extensions (`propose_complete`, `disputed`, `rejected`)
- MCP server with 13 tools —
[npm](https://www.npmjs.com/package/@agenttrust/mcp-server) |
[GitHub](https://github.com/agenttrust/mcp-server)
- Webhook delivery with HMAC-SHA256 signatures

**Links:**
- Website: https://agenttrust.ai
- MCP Server: https://github.com/agenttrust/mcp-server
- npm: https://www.npmjs.com/package/@agenttrust/mcp-server

Built on Google's A2A protocol. We fill the identity and trust gap — A2A
defines how agents talk, AgentTrust helps them prove who they are.

---------

Co-authored-by: AgentTrust <hello@agenttrust.ai>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Amye Scavarda Perrin <amye@amye.org>
2026-03-02 15:09:02 -08:00
Pinchwork
789bc73d8b
docs: add Pinchwork to partners list (#1498)
Hi Amye and team,

Following up on issue #1443 ("Add Pinchwork as A2A-compatible agent
marketplace") — thank you for the warm welcome and for pointing us to
the partners list!

This PR adds [Pinchwork](https://pinchwork.dev) to the partners list,
alphabetically between Personal AI and Poppulo.

**About Pinchwork:**
Pinchwork is an agent-to-agent task marketplace where AI agents can post
tasks, pick up work, and earn credits — all via a simple API. We have a
live A2A endpoint at `/.well-known/agent-card.json` and a JSON-RPC A2A
endpoint at `/a2a`, supporting `message/send`, `tasks/get`, and
`tasks/cancel`.

We're excited to be part of the A2A ecosystem and look forward to
contributing to interoperability between agents.

Resolves #1443

Co-authored-by: Pinchwork <hello@pinchwork.dev>
Co-authored-by: Amye Scavarda Perrin <amye@amye.org>
2026-03-02 14:45:10 -08:00
Holt Skinner
4890b77d6f
docs: Fix embedded version of AgentExtension in extensions (#1550) 2026-02-26 13:14:05 -06:00
Gijs Walraven
629190aea9
docs: wrap Task in result.task in life-of-a-task examples (#1492)
## Issue

Closes #1368 — Clarify whether JSON-RPC result should wrap Task/Message
objects

## Problem

Both response examples in `docs/topics/life-of-a-task.md` returned Task
fields directly inside `result`:

```json
"result": {
  "id": "task-boat-gen-123",
  "status": { ... },
  "artifacts": [ ... ]
}
```

The v1.0 specification defines `SendMessageResponse` as:

```
oneof response {
  Task task = 1;
  Message message = 2;
}
```

This means the result **must** contain either a `"task"` or `"message"`
wrapper key, not direct Task fields.

## Fix

Both response examples now correctly wrap the Task:

```json
"result": {
  "task": {
    "id": "task-boat-gen-123",
    "status": { ... },
    "artifacts": [ ... ]
  }
}
```

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Gijs Walraven <gijs.walraven@delaware.pro>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
2026-02-18 16:13:47 +00:00
Gijs Walraven
8bf133addc
docs: use correct v1.0 method name "SendMessage" in life-of-a-task example (#1491)
## Summary

The follow-up scenario example in \`docs/topics/life-of-a-task.md\` used
\`"message.send"\` (dot notation) for the first request, while the
second request in the same example correctly used \`"SendMessage"\`
(v1.0 PascalCase). This made the file internally inconsistent and showed
a method name that doesn't exist in any version of the protocol.

## Change

\`\`\`diff
- "method": "message.send",
+ "method": "SendMessage",
\`\`\`

**File:** \`docs/topics/life-of-a-task.md\`

## Related

- Closes #1493
- Related to #1367 (method name inconsistencies across documentation)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Gijs Walraven <gijs.walraven@delaware.pro>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-02-18 10:12:17 -06:00
Gijs Walraven
7245512250
docs: correct Part discriminator values and remove stale v0.3.x type names (#1490)
## Summary

Fixes documentation inconsistencies related to Part discriminator field
values, identified in #1365.

## Changes

### `docs/specification.md` — Appendix A.2.1

- **Legacy Part `kind` values**: corrected from PascalCase (`"kind":
"TextPart"`, `"kind": "FilePart"`, `"kind": "DataPart"`) to lowercase
(`"kind": "text"`, `"kind": "file"`, `"kind": "data"`), consistent with
what `whats-new-v1.md` documents as the v0.3.0 format
- **Legacy FilePart structure**: added the missing nested `file` object
wrapper
- **Legacy streaming event `kind` values**: corrected from PascalCase
(`TaskStatusUpdateEvent`, `TaskArtifactUpdateEvent`) to camelCase
(`taskStatusUpdate`, `taskArtifactUpdate`)
- **Current `DataPart` migration target**: removed incorrect
double-wrapping (`{ "data": { "data": {...} } }` → `{ "data": {...},
"mediaType": "application/json" }`)
- **Current streaming event member names**: aligned with
`whats-new-v1.md` (`taskStatusUpdate` / `taskArtifactUpdate`)

### `docs/topics/key-concepts.md`

- Updated Part description to use v1.0 terminology, removing references
to the removed `TextPart`, `FilePart`, and `DataPart` types

### `docs/tutorials/python/8-next-steps.md`

- Replaced reference to removed `DataPart` type with v1.0 Part field
names

### `CONTRIBUTING.md`

- Added **Documentation Guidelines** section with correct v1.0 Part
examples (member-presence pattern) and guidance on the correct v0.3.x
lowercase `kind` discriminator values for migration docs

## Related

- Closes #1365
- External community site fix:
https://github.com/sing1ee/a2a-directory/pull/12

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Gijs Walraven <gijs.walraven@delaware.pro>
2026-02-18 10:11:37 -06:00
Sam Betts
857a995a3d
docs(spec): Correct wording around blocking=true (#1398)
This corrects the wording so that blocking=True includes terminal and
interrupted states as triggers for returning to the client.

Fixes: #1264

---------

Signed-off-by: Sam Betts <1769706+Tehsmash@users.noreply.github.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
2026-02-17 18:06:57 +00:00
Yaroslav
cf735cb870
fix(spec)!: pluralize configs in ListTaskPushNotificationConfigs (#1486)
Pluralize PushNotificationConfig in ListTaskPushNotificationConfig
request and responses.

This is consistent with ListTasks.

Part of #1451

---------

Co-authored-by: Kuba Herczyński <herczyn@google.com>
Co-authored-by: Darrel <darrmi@microsoft.com>
2026-02-17 09:40:07 -08:00
Ivan Shymko
73d5f59a32
docs(spec): Fix whats-new-v1.md (#1460)
Changes below as they appear in the file.

- `blocking` flag existed in 0.3:
[source](https://a2a-protocol.org/v0.3.0/specification/#712-messagesendconfiguration-object)
- `SendMessage`: remove "MAY return Message"/"MUST return Task" which
are not in the spec, remove service parameters mention as they are
covered above
- streaming was specified for gRPC in proto definition as `returns
(stream StreamResponse)`
- `SubscribeToTask` is not a new operation
- blocking has no effect for streaming operations:
[source](https://a2a-protocol.org/latest/specification/#322-sendmessageconfiguration)
- `TaskNotCancelableError` was mentioned in 0.3:
[source](https://a2a-protocol.org/v0.3.0/specification/#82-a2a-specific-errors)
- RFC 7515 was mentioned for Agent Card signatures in 0.3:
[source](https://a2a-protocol.org/v0.3.0/specification/#556-agentcardsignature-object),
kept only RFC 8785 for canonicalization which wasn't
- `agentId` field does not exist and never did
- extension declarations (AgentExtension object) did not change between
[0.3](https://a2a-protocol.org/v0.3.0/specification/#5521-agentextension-object)
and
[1.0](https://a2a-protocol.org/latest/specification/#444-agentextension)
- Mutual TLS existed in 0.3:
[source](https://a2a-protocol.org/v0.3.0/specification/#553-securityscheme-object)
- subscribing to tasks not originally created via streaming is not a
behavior change and is not explicitly mentioned in 1.0
- `token` is not removed from `PushNotificationConfig`:
[source](https://a2a-protocol.org/latest/specification/#431-pushnotificationconfig)
- `configId` does not exist in `PushNotificationConfig`
([source](https://a2a-protocol.org/latest/specification/#431-pushnotificationconfig))
and `id` was there in 0.3
([source](https://a2a-protocol.org/v0.3.0/specification/#68-pushnotificationconfig-object))
- `PushNotificationNotSupportedError` existed in 0.3:
[source](https://a2a-protocol.org/v0.3.0/specification/#82-a2a-specific-errors)
- `SendMessageRequest` example fixed to match the spec
- `createdAt` and `lastModified` do not exist in `Task`:
[source](https://a2a-protocol.org/latest/specification/#411-task)
- changes to nested `Task` objects removed as they are covered in
respective sections (`TaskStatus`, `Message`, `Artifact`)
- `timestamp` was not added to `Message`:
[source](https://a2a-protocol.org/latest/specification/#414-message)
- there is no "stricter typing" for `metadata`
- "retained" should not be in the changelog
- `createdAt` was not added to `Artifact`:
[source](https://a2a-protocol.org/latest/specification/#417-artifact)
- `signatures` field was there in 0.3:
[source](https://a2a-protocol.org/v0.3.0/specification/#55-agentcard-object-structure)

Re #1436.

Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: Darrel <darrmi@microsoft.com>
2026-02-17 16:28:14 +00:00
Holt Skinner
fde2bd8da8
ci(docs): Update llms-full.txt script to include text versions of sdk docs and updated proto path (#1476) 2026-02-17 10:11:23 -06:00
Yaroslav
05603f973f
docs(spec): minor spec corrections (#1482)
* Removed outdated part format from examples
* Added a missing TaskNotFoundError to non-streaming rpc errors list
* Removed outdated final flag from status update examples

The referenced issues has some other things:
1. Should ListTaskPushNotificationConfig be pluralized into
ListTaskPushNotificationConfigs?
2. Should all request operating on push configs settle on either
configID or ID naming. Create vs (Delete|List|Get) RPCs differ at the
moment.
3. In CreateRequest we have ID based on the request root level and in
config payload. Should the former be removed?

https://github.com/a2aproject/A2A/issues/1451
2026-02-17 10:07:02 -06:00
Holt Skinner
7cf67271cf
docs: Add DeepLearning.AI Course to README and docs (#1469) 2026-02-11 10:39:23 -06:00
Holt Skinner
a3d78dcad3
docs(spec): Convert Proto Table display in specification to use existing libraries (#1427)
Convert bespoke `macros.py` to use `proto-schema-parser` and `tabulate`
to display tables

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
2026-02-10 13:19:52 -06:00
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