Gemini CLI adds an A2A server

Google now documents an A2A server component for Gemini CLI. The official repository contains a separate packages/a2a-server package that uses the A2A JavaScript SDK as a runtime dependency. A related development-tool RFC describes client communication with the Gemini CLI agent using the Agent-to-Agent protocol, including Agent Card, messaging and streaming mechanisms.

This matters because two protocol roles are now supported by evidence. Gemini CLI was already documented as an A2A client that can delegate tasks to compatible remote subagents. With the server package, external A2A clients can also address Gemini CLI as an agent endpoint.

For organizations and developers, this is primarily an interoperability signal. A2A is designed to let agents from different systems communicate through a standardized interface. The server package does not automatically mean every Gemini CLI installation should be exposed publicly or is production-hardened by default.

Authentication, network exposure and deployment design remain separate concerns. AgentenCode therefore records the server role as a protocol capability while keeping enterprise SLAs, security posture and concrete deployment controls as distinct evidence questions.