opencode-a2a and codex-a2a
These are ecosystem siblings—both are A2A adapters that expose different code execution backends (OpenCode vs. Codex) through identical server/client architectures, allowing users to choose their preferred code engine while using the same communication protocol.
About opencode-a2a
Intelligent-Internet/opencode-a2a
Expose OpenCode through A2A with an inbound server surface and embedded outbound client.
Implements bidirectional A2A (agent-to-agent) communication by wrapping OpenCode's runtime with REST/JSON-RPC endpoints, session management, and streaming support. Enables peer-to-peer agent orchestration through an embedded `a2a_call` tool that allows outbound calls to other A2A services, with configurable bearer or basic auth for upstream peer access. Designed as a thin deployment boundary layer—handles inbound A2A requests, routes tool calls to OpenCode, and manages task storage via SQLite, leaving multi-tenant isolation and process supervision to the operator.
About codex-a2a
liujuanjuan1984/codex-a2a
Expose Codex through A2A with an inbound server surface and embedded outbound client.
Provides A2A HTTP+JSON and JSON-RPC endpoints to expose a local Codex runtime with inbound request handling, streaming, and session continuity, while embedding an outbound A2A client for autonomous peer calling via the `a2a_call` tool. Supports bearer/basic auth, SSE streaming with normalized blocks, and transport selection for peer interactions, with clear single-tenant deployment boundaries between portable A2A methods and Codex-specific control plane extensions.
Scores updated daily from GitHub, PyPI, and npm data. How scores work