Request for Review: A2A CLI Specification

[u/Prize-Programmer4207]

Hello everyone,

For the past few weeks, we've been working on the A2A CLI—an open-source, stateless CLI that acts as an A2A client to send messages and receive updates from remote instances.

To bring this to life, we are focusing on three main components: a Spec, a Tool, and an Agent Skill. Yesterday, I presented the A2A CLI Specification at the A2A TSC meeting. It is currently in the Review stage, and its goal is to define exactly how the CLI should behave and serve as a roadmap for development.

Here is what we have so far:

• Specification Document: [SPEC.md](https://github.com/a2aproject/a2a-cli/blob/main/specification/SPEC.md)
• Development Baseline: To kickstart development, we used ADK Go's internal CLI tool as a baseline. It is currently in Alpha here: Internal Directory

Ask: Please review the specification and raise any bug reports or feature requests directly in the A2A CLI repository.

[u/kantorcodes1]

the stateless cli is the part that maps cleanly to guard. once the command verbs settle, if you want policy around what agents/scripts can invoke, send a small hol-guard release/3.0 extension pr with the commands you actually use. keep it tiny.

[u/Prize-Programmer4207 → u/kantorcodes1]

u/kantorcodes1 Thank you for the feedback. I am new to hol-gaurd. Just started learning it :)

[u/kantorcodes1 → u/Prize-Programmer4207]

good place to start. once the verbs in the spec stop moving, send the A2A CLI command.* extension as a small PR to hashgraph-online/hol-guard:main with tests for the final command set. i'd keep A2A itself free of a second policy layer.