UAT: Server-mode A2A HTTP transport and endpoint are stubs #6276

New issue

Open

opened 2026-04-09 19:46:04 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-09 19:46:04 +00:00

Owner

Summary

Server-mode transport and endpoint are still stubs: A2aHttpTransport raises A2aNotAvailableError for every operation, and the CLI agents server connect command only persists config with a "stubbed" warning.
The packaged ASGI app (cleveragents.a2a.asgi:app) serves only /, /live, /ready, /health health probes and never exposes a JSON-RPC 2.0 endpoint for _cleveragents/* methods.

Spec references

docs/specification.md §§23536-23538, 23598-23607: "CleverAgents adopts the Agent-to-Agent Protocol ... every client operation flows through A2A regardless of deployment mode ... In server mode the client connects via HTTP to the CleverAgents A2A server. All methods (standard + extensions) flow through the single A2A JSON-RPC 2.0 endpoint."

Evidence

# src/cleveragents/a2a/transport.py
class A2aHttpTransport:
    def send(...):
        raise A2aNotAvailableError("A2A HTTP transport is not available in local mode")
    def connect(...):
        raise A2aNotAvailableError(...)

# src/cleveragents/cli/commands/server.py
_STUB_WARNING = "Server connection is not yet implemented..."
server_connect(...) -> persists config then reports status "stubbed".

# src/cleveragents/a2a/asgi.py
app(...) -> only GET /, /live, /ready, /health responses; no JSON-RPC handler.

No HTTP entry point exists for _cleveragents/plan/*, registry, context, or sync methods, so the documented A2A server-mode flow cannot work.

Impact

Server mode cannot be exercised or tested: clients cannot POST JSON-RPC requests, no SSE events, and no LangGraph delegation path exists.

Suggested Fix

Implement the JSON-RPC 2.0 HTTP endpoint (routing to the same facade/services), provide a working A2aHttpTransport, and remove the stub warning so server mode matches the spec sequence diagram.

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Summary - Server-mode transport and endpoint are still stubs: `A2aHttpTransport` raises `A2aNotAvailableError` for every operation, and the CLI `agents server connect` command only persists config with a "stubbed" warning. - The packaged ASGI app (`cleveragents.a2a.asgi:app`) serves only `/`, `/live`, `/ready`, `/health` health probes and never exposes a JSON-RPC 2.0 endpoint for `_cleveragents/*` methods. ## Spec references - docs/specification.md §§23536-23538, 23598-23607: "CleverAgents adopts the Agent-to-Agent Protocol ... every client operation flows through A2A regardless of deployment mode ... In server mode the client connects via HTTP to the CleverAgents A2A server. All methods (standard + extensions) flow through the single A2A JSON-RPC 2.0 endpoint." ## Evidence ```python # src/cleveragents/a2a/transport.py class A2aHttpTransport: def send(...): raise A2aNotAvailableError("A2A HTTP transport is not available in local mode") def connect(...): raise A2aNotAvailableError(...) ``` ```python # src/cleveragents/cli/commands/server.py _STUB_WARNING = "Server connection is not yet implemented..." server_connect(...) -> persists config then reports status "stubbed". ``` ```python # src/cleveragents/a2a/asgi.py app(...) -> only GET /, /live, /ready, /health responses; no JSON-RPC handler. ``` No HTTP entry point exists for `_cleveragents/plan/*`, registry, context, or sync methods, so the documented A2A server-mode flow cannot work. ## Impact - Server mode cannot be exercised or tested: clients cannot POST JSON-RPC requests, no SSE events, and no LangGraph delegation path exists. ## Suggested Fix - Implement the JSON-RPC 2.0 HTTP endpoint (routing to the same facade/services), provide a working `A2aHttpTransport`, and remove the stub warning so server mode matches the spec sequence diagram. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

Rows
Columns