Low findings from a2a-serve user simulation at 1b67edf

Open
#160 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
cli

Research direction

The payload names no source files, so start by reproducing the commands it lists: a2a send hi, a2a send hi --task-id "", and a2a send --bogus -o json. The -o json item may come from shared flag-parsing setup, so check how the CLI handles errors before send runs. Done means each checklist item is either fixed or split into its own issue, and the Resume: hint is left to #144.

Written by the indexing model from the issue text.

Description

Low-severity findings in the a2a CLI v0.4.0 from a user-simulation round of a2a-serve.

  • a2a send without an agent shows a hint written for AI agents. a2a send hi prints Error: either '--agent-card <ref>' or '--endpoint <url> --transport <t>' must be provided and hint: if you are an agent, your a2a skill may be out of date …. A person gets no next step, and the error doesn't name -a, which the docs use. For a stopped agent, hint: check the agent is running and the --agent-card reference is correct doesn't say how.
  • a2a send --task-id "" starts a new task and sends the answer as a prompt. An empty shell variable from a mis-pasted ID gives a new task where the model replies to "once". An unknown ID fails with task not found; an empty one should fail too.
  • Ctrl-C during a2a send prints nothing and leaves the task running. timeout -s INT 6 a2a send …: no output, and the task keeps working. Printing the task ID and how to follow or cancel it would help.
  • Flag-parse errors ignore -o json. a2a send --bogus -o json prints plain text and exits 2, while other errors print the JSON error object. The same shape shows up in a2a-serve, so the cause may be shared CLI setup.

Already tracked: the Resume: hint without -a is #144, which reproduced in 2 more lanes.

Found by user simulation (tools/sim) at 1b67edf.

Dominant language
Go
Stars
181
Forks
28
Avg merge
2d 11h
Merged PRs (30d)
22

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from a2aproject/a2a-cli

All issues in a2aproject/a2a-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.