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):
| Outcome | A2A task state |
|---|---|
| Unknown skill | rejected |
| Input fails capability schema | rejected |
| Caller unauthorized | rejected |
| Capability unavailable in Model | rejected |
| Declared failure Message arrives | failed |
| Completion times out after dispatch | failed |
| Invocation cancelled | canceled |
| Validated dispatch without completion contract | completed |
| Correlated success Message arrives | completed |
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: falseandpushNotifications: false(message/streamis refused).- Multi-turn
input-required/auth-requiredflows, file parts, and artifacts are omitted.
Choose an agent adapter
| Where the agent runs | Adapter |
|---|---|
| In the page beside the user | foldkit-agent-webmcp |
| External MCP client over stdio or HTTP | foldkit-agent-mcp |
| Another agent over A2A | foldkit-agent-a2a |
| An Agent Native host | foldkit-agent-native |
Next
- Define capabilities, completion contracts, and audit logs:
foldkit-agent - Serve the same contract over MCP:
foldkit-agent-mcp - Read the architecture guide: Agents guide