Gemini CLI: HTTP Authentication for A2A Remote Agents
Gemini CLIGemini CLI v0.33.0 adds HTTP authentication support for discovering and connecting to remote Agent-to-Agent (A2A) endpoints, enabling connections to private and enterprise-internal A2A agents that require credentials. A2A streaming reassembly has been made more robust with a 5-minute default headers timeout.
Sources & Mentions
2 external resources covering this update
HTTP Authentication for Remote A2A Agents
The Agent-to-Agent (A2A) protocol, which allows Gemini CLI to delegate tasks to remote agent endpoints, now supports HTTP authentication when discovering and connecting to external agent cards. This makes it possible to connect to private or enterprise-internal A2A agents that require credentials, expanding the practical reach of multi-agent workflows beyond publicly accessible endpoints.
Improved A2A Reliability
A2A streaming reassembly has been made more robust, the default headers timeout has been increased to 5 minutes, and authenticated A2A agent card discovery is now supported end-to-end. These changes collectively make A2A integrations more practical for production environments where network latency, authentication handshakes, and long-running agent tasks are common.