Agent / foldkit-agent-a2a

Task states and completion outcomes

message/send creates a task readable with tasks/get and abortable with tasks/cancel. The adapter distinguishes rejected (declined before running) from failed (accepted, then failed during completion):

OutcomeA2A task state
Unknown skillrejected
Input fails capability schemarejected
Caller unauthorizedrejected
Capability unavailable in Modelrejected
Declared failure Message arrivesfailed
Completion times out after dispatchfailed
Invocation cancelledcanceled
Validated dispatch without completion contractcompleted
Correlated success Message arrivescompleted

Capabilities without a completion contract finish at validated dispatch; capabilities with one wait until their correlated success/failure Message, timeout, or cancellation settles the task.

Supported A2A features and limits

The generated Agent Card advertises only what the adapter implements:

  • streaming: false and pushNotifications: false (message/stream is refused).
  • Multi-turn input-required / auth-required flows, file parts, and artifacts are omitted.

Choose an agent adapter

Where the agent runsAdapter
In the page beside the userfoldkit-agent-webmcp
External MCP client over stdio or HTTPfoldkit-agent-mcp
Another agent over A2Afoldkit-agent-a2a
An Agent Native hostfoldkit-agent-native

Next