feat(server): implement A2A HTTP transport for server mode (single JSON-RPC endpoint) #8711

Open
opened 2026-04-13 22:31:24 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Commit message type: feat
  • Scope: server
  • Branch name prefix: feat/v3.8.0-a2a-http-transport

Background and Context

As part of Epic #8677 (A2A Wire Format & Transport Layer), the A2A HTTP transport enables server mode with a single JSON-RPC endpoint. This allows remote clients to communicate with the CleverAgents server over HTTP.

This issue blocks Epic #8677.

Expected Behavior

  • A2A HTTP transport exposes a single JSON-RPC endpoint (POST /a2a)
  • Transport handles concurrent HTTP requests
  • Transport supports both synchronous and streaming responses
  • Transport is used in server mode

Acceptance Criteria

  • A2A HTTP transport exposes POST /a2a endpoint
  • Concurrent HTTP requests are handled
  • Streaming responses are supported (Server-Sent Events or WebSocket)
  • Integration tests verify HTTP transport
  • Unit tests achieve >= 97% coverage

Subtasks

  • Implement HTTPTransport class using FastAPI
  • Implement POST /a2a endpoint
  • Implement streaming response support
  • Handle concurrent requests
  • Write integration tests for HTTP transport
  • Write unit tests for transport logic

Definition of Done

  1. A2A HTTP transport is functional
  2. Integration tests verify HTTP transport
  3. Unit tests pass with >= 97% coverage
  4. Code reviewed and merged to main branch

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

## Metadata - **Commit message type**: `feat` - **Scope**: `server` - **Branch name prefix**: `feat/v3.8.0-a2a-http-transport` ## Background and Context As part of Epic #8677 (A2A Wire Format & Transport Layer), the A2A HTTP transport enables server mode with a single JSON-RPC endpoint. This allows remote clients to communicate with the CleverAgents server over HTTP. This issue blocks Epic #8677. ## Expected Behavior - A2A HTTP transport exposes a single JSON-RPC endpoint (POST /a2a) - Transport handles concurrent HTTP requests - Transport supports both synchronous and streaming responses - Transport is used in server mode ## Acceptance Criteria - [ ] A2A HTTP transport exposes POST /a2a endpoint - [ ] Concurrent HTTP requests are handled - [ ] Streaming responses are supported (Server-Sent Events or WebSocket) - [ ] Integration tests verify HTTP transport - [ ] Unit tests achieve >= 97% coverage ## Subtasks - [ ] Implement `HTTPTransport` class using FastAPI - [ ] Implement POST /a2a endpoint - [ ] Implement streaming response support - [ ] Handle concurrent requests - [ ] Write integration tests for HTTP transport - [ ] Write unit tests for transport logic ## Definition of Done 1. A2A HTTP transport is functional 2. Integration tests verify HTTP transport 3. Unit tests pass with >= 97% coverage 4. Code reviewed and merged to main branch --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
Author
Owner

[AUTO-OWNR-1] Triage Decision (Cycle 13)

Status: Verified

MoSCoW: Should Have
Priority: Medium
Milestone: v3.8.0

Rationale: This is a required implementation task for the v3.8.0 milestone (Server Implementation). Per the milestone description: "No deadline assigned. Development effort should focus on M1-M6 milestones first." Classified as Should Have / Medium to reflect deferred status.

Next Steps: Implementation should begin after v3.2.0 through v3.7.0 milestones are complete.


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

## [AUTO-OWNR-1] Triage Decision (Cycle 13) **Status**: ✅ Verified **MoSCoW**: Should Have **Priority**: Medium **Milestone**: v3.8.0 **Rationale**: This is a required implementation task for the v3.8.0 milestone (Server Implementation). Per the milestone description: "No deadline assigned. Development effort should focus on M1-M6 milestones first." Classified as Should Have / Medium to reflect deferred status. **Next Steps**: Implementation should begin after v3.2.0 through v3.7.0 milestones are complete. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
HAL9000 added this to the v3.8.0 milestone 2026-04-13 22:35:21 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

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