EPIC: A2A HTTP Transport — Real Server Connection (Not Stub) #4967

Open
opened 2026-04-08 23:40:59 +00:00 by freemo · 1 comment
Owner

Epic: A2A HTTP Transport Implementation

This Epic covers replacing the stub A2A HTTP transport with a real implementation that can connect to actual servers. Currently A2aHttpTransport raises A2aNotAvailableError on all operations.

Demonstrable Capability

When this Epic is complete, a developer can:

  1. Connect to a real A2A server via HTTP
  2. Send JSON-RPC 2.0 requests to the server
  3. Receive responses from the server
  4. Use agents server connect to configure the server connection
  5. Have the Agent Card endpoint (/.well-known/agent.json) served correctly

Child Issues

Definition of Done

  • All child issues are closed
  • A2aHttpTransport connects to real servers (not stub)
  • JSON-RPC 2.0 wire format implemented correctly
  • asgi.py serves /.well-known/agent.json Agent Card endpoint
  • asgi.py has A2A JSON-RPC endpoint (POST / or POST /a2a)
  • _cleveragents/health/check returns real service health data
  • All nox stages pass
  • Coverage >= 97%

Metadata

  • Branch Naming Convention: feat/m9/a2a-http-transport
  • Milestone: v3.8.0
  • Parent Legendary: #4947

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planner

## Epic: A2A HTTP Transport Implementation This Epic covers replacing the stub A2A HTTP transport with a real implementation that can connect to actual servers. Currently `A2aHttpTransport` raises `A2aNotAvailableError` on all operations. ### Demonstrable Capability When this Epic is complete, a developer can: 1. Connect to a real A2A server via HTTP 2. Send JSON-RPC 2.0 requests to the server 3. Receive responses from the server 4. Use `agents server connect` to configure the server connection 5. Have the Agent Card endpoint (/.well-known/agent.json) served correctly ### Child Issues <!-- Updated by automation after child issues are created --> ### Definition of Done - [ ] All child issues are closed - [ ] `A2aHttpTransport` connects to real servers (not stub) - [ ] JSON-RPC 2.0 wire format implemented correctly - [ ] `asgi.py` serves `/.well-known/agent.json` Agent Card endpoint - [ ] `asgi.py` has A2A JSON-RPC endpoint (`POST /` or `POST /a2a`) - [ ] `_cleveragents/health/check` returns real service health data - [ ] All nox stages pass - [ ] Coverage >= 97% ## Metadata - **Branch Naming Convention**: `feat/m9/a2a-http-transport` - **Milestone**: v3.8.0 - **Parent Legendary**: #4947 --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: High — A2A HTTP Transport is the core of the Server Implementation Legendary; it enables real server connections replacing the current stubs
  • Milestone: v3.8.0
  • Story Points: 34 — XXL — Epic covering A2A HTTP transport, JSON-RPC 2.0 wire format, single endpoint routing, and real server connection
  • MoSCoW: Must Have — The A2A HTTP transport is the primary mechanism for multi-user server communication; without it, the server cannot accept connections from clients
  • Parent Legendary: #4947

This Epic is valid. It is the core transport layer for the Server Implementation Legendary.


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: High — A2A HTTP Transport is the core of the Server Implementation Legendary; it enables real server connections replacing the current stubs - **Milestone**: v3.8.0 - **Story Points**: 34 — XXL — Epic covering A2A HTTP transport, JSON-RPC 2.0 wire format, single endpoint routing, and real server connection - **MoSCoW**: Must Have — The A2A HTTP transport is the primary mechanism for multi-user server communication; without it, the server cannot accept connections from clients - **Parent Legendary**: #4947 This Epic is valid. It is the core transport layer for the Server Implementation Legendary. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
HAL9000 added this to the v3.8.0 milestone 2026-04-09 00:49:55 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#4967
No description provided.