![[2602.17675] Mind the Boundary: Stabilizing Gemini Enterprise A2A via a Cloud Run Hub Across Projects and Accounts](https://arxiv.org/static/browse/0.3.4/images/arxiv-logo-fb.png){kind=logo}
[2602.17675] Mind the Boundary: Stabilizing Gemini Enterprise A2A via a Cloud Run Hub Across Projects and Accounts
Summary
The article discusses the implementation of a Cloud Run Hub for stabilizing Gemini Enterprise A2A interactions across multiple projects and accounts, focusing on secure and reproducible orchestration of backend agents.
Why It Matters
As enterprises increasingly rely on conversational UIs that integrate various backend systems, ensuring seamless and secure communication across different projects and accounts is crucial. This research provides insights into overcoming interoperability challenges, which is essential for enhancing user experience and operational efficiency in enterprise environments.
Key Takeaways
- The A2A Hub orchestrator enables efficient routing of queries across different projects and accounts.
- Interoperability is influenced by both protocol compliance and UI constraints.
- Implementing a text-only compatibility mode can prevent UI errors during agent interactions.
- The research confirms stable UI responses through deterministic routing in a benchmark test.
- Reproducibility of experiments is ensured with a tagged repository snapshot.
Computer Science > Distributed, Parallel, and Cluster Computing arXiv:2602.17675 (cs) [Submitted on 26 Jan 2026] Title:Mind the Boundary: Stabilizing Gemini Enterprise A2A via a Cloud Run Hub Across Projects and Accounts Authors:Takao Morita View a PDF of the paper titled Mind the Boundary: Stabilizing Gemini Enterprise A2A via a Cloud Run Hub Across Projects and Accounts, by Takao Morita View PDF HTML (experimental) Abstract:Enterprise conversational UIs increasingly need to orchestrate heterogeneous backend agents and tools across project and account boundaries in a secure and reproducible way. Starting from Gemini Enterprise Agent-to-Agent (A2A) invocation, we implement an A2A Hub orchestrator on Cloud Run that routes queries to four paths: a public A2A agent deployed in a different project, an IAM-protected Cloud Run A2A agent in a different account, a retrieval-augmented generation path combining Discovery Engine and Vertex AI Search with direct retrieval of source text from Google Cloud Storage, and a general question answering path via Vertex AI. We show that practical interoperability is governed not only by protocol compliance but also by Gemini Enterprise UI constraints and boundary-dependent authentication. Real UI requests arrive as text-only inputs and include empty accepted output mode lists, so mixing structured data into JSON-RPC responses can trigger UI errors. To address this, we enforce a text-only compatibility mode on the JSON-RPC endpoint while separa...
