This is a submission for the Google Cloud NEXT Writing Challenge I watched every hour of Google Cloud NEXT '26. And like everyone else, I was dazzled by the Gemini Enterprise Agent Platform rebrand, the 8th-gen TPUs, and the Workspace Studio demos. Two protocols. A2A and MCP. And how Google just bet the entire agentic era on both of them. A Quick Reality Check First MCP: You Probably Already Know This One A2A: The Protocol Nobody Is Talking About Agent A (Gemini, on Google Cloud) These three agents — built on completely different models, by different teams, running on different clouds — can now hand off tasks, share context, and collaborate. Without any of them needing to understand each other's internals. My Honest Take: The Risks The Bigger Picture NEXT '26 was framed around one phrase: "The era of the pilot is over. The era of the agent is here." Kurian was talking about enterprise adoption. But for developers, I'd reframe it: the era of building single-model, single-platform AI features is giving way to something messier and more powerful — networks of agents, built by different teams, running on different infrastructure, coordinating in real time. The Gemini Enterprise Agent Platform is Google's bet on how you'll build those networks. A2A and MCP are the invisible foundation that makes it possible to build them without surrendering to a single vendor. That's the story I'll be watching unfold. And it started quietly, in the keynote, in a slide most people skimmed past.