Skip to content

docs: add "Why the A2A CLI" section to README #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
msampathkumar merged 1 commit into from
Aug 21, 2026
Merged

docs: add "Why the A2A CLI" section to README #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,17 @@ The **A2A CLI** (`a2a`) is a standardized command-line client for discovering, i
> We are formalizing and reviewing the **A2A CLI Specification**. Share feedback, questions, and contributions on the specification documents as we finalize v0.2 in **August 2026**.


## Why the A2A CLI

The `a2a` CLI is one consistent way to work with A2A agents — no throwaway scripts or raw-JSON parsing just to talk to an agent.

* **AI coding agents** delegate work to A2A agents through one command surface, driven from a bundled skill descriptor — no custom plugins per harness.
* **Developers** inspect and drive any deployed agent from the terminal — fetch a card, send a message, stream updates, list or cancel tasks, one readable command each.
* **Automation and CI** call agents from a stable, scriptable surface: protocol-native JSON (`-o json`) and predictable exit codes, no client library required.

The CLI handles the underlying complexity. It negotiates the transport (JSON-RPC, REST, or gRPC) from the agent's card, waits for a task to finish unless you tell it not to, and behaves the same across agents and languages.


## About the Project

Several community-driven CLI tools exist across languages, but they vary in coverage and behavior. To prevent fragmentation, this project defines one **standardized, officially supported CLI specification and reference implementation** — built for long-term stability, cross-transport consistency, and community alignment.
Expand Down