# a2a Published articles for a2a. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A2A Is Now an Open Standard. The Data Layer Underneath It Isn't. DevFeed: [A2A Is Now an Open Standard. The Data Layer Underneath It Isn't.]() Original publisher: [Read original article]() Author: Quentin Packard Published: 2026-08-19T00:00:00Z Content type: opinion Language: en Sources: [Cockroach Labs]() Topics: [agent to agent communication](), [Multi Agent Systems](), [Model Context Protocol](), [Database](), [Artificial Intelligence]() Tags: [a2a](), [agent-to-agent-communication](), [agentic](), [agents](), [ai](), [architecture](), [database](), [mcp](), [model-context-protocol](), [multi-agent-systems](), [protocol](), [standards]() ### AI overview The article argues that A2A standardizes communication between agents but leaves the underlying data and state layer undefined. It contrasts A2A's horizontal agent-to-agent communication with MCP's vertical connection between an agent and external tools or data, and argues that production systems need both alongside a database-centered state architecture. AGENTS.md is presented as another interface standard that leaves durable state outside its scope. ### Source excerpt In April 2025, Google released a protocol for agent-to-agent communication. Within three months, Google had donated it to the Linux Foundation... ## How AI Agents Actually Talk to Each Other DevFeed: [How AI Agents Actually Talk to Each Other]() Original publisher: [Read original article]() Author: Byte-Sized Design Published: 2026-08-06T06:31:30Z Content type: opinion Language: en Sources: [Byte-Sized Design]() Topics: [Artificial Intelligence](), [Model Context Protocol]() Tags: [a2a](), [agents](), [ai](), [ai-agents](), [mcp]() ### AI overview The article discusses how AI agents communicate and argues that framing MCP and A2A as competing technologies describes a conflict that does not exist. ### Source excerpt And why "MCP vs A2A" is a fight that doesn't exist ## Adapting open source practices to an AI-first world: A retrospective on 2025 DevFeed: [Adapting open source practices to an AI-first world: A retrospective on 2025]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-08-03T18:30:00Z Content type: article Language: en Sources: [Google Open Source Blog]() Topics: [Open Source](), [Google](), [A2A protocol](), [interoperability](), [GitHub](), [linux foundation](), [Protocol (disambiguation)](), [LLVM](), [Rust](), [vllm](), [gRPC](), [Kubernetes]() Tags: [2025](), [a2a](), [a2a-protocol](), [agents](), [ai](), [ai-agents](), [github](), [google-open-source](), [interoperability](), [kubernetes](), [linux](), [linux-foundation](), [open-source](), [report-card](), [retrospective](), [rust](), [security](), [vllm]() ### AI overview Google reviews Alphabet's 2025 open source activity, including employee and external contributions, collaboration on the Agent2Agent protocol, and the maintenance and launch of public repositories and tools. ### Source excerpt by Sophia Vargas, Google Open Source Even as AI adoption accelerates and transforms the global technology landscape, open source remains foundational to how Alphabet builds, uses, and collaborates on products for billions of users. Our commitment to open source remains broad and consistent, including sharing our work year-over-year, and reflecting on what we've learned. In 2025: Roughly 10% of Alphabet's full-time workforce actively contributed to open source projects. This contribution ratio has remained steady over the past five years, scaling to match our growth. These open source contributions are not just solely focused on Google. Our top projects by unique contributors at Alphabet include community-led projects such as LLVM, vLLM, Envoy, and Rust, as well as Google-initiated projects like Kubernetes, Apache Beam, and gRPC. In addition, Alphabet projects received commits from more than 20,000 non-Alphabet affiliated user accounts. Working together on emerging standards Open source communities continue to provide vital collaborative spaces to define emerging standards, ensuring the interoperability and extensibility for the next generation of technologies. In 2025, we worked with more than 50 partners on the Agent2Agent (A2A) protocol to enable AI agents to communicate with each other, securely exchange information, and coordinate actions on top of various enterprise platforms and applications. Within weeks of our initial announcement, Google donated the A2A project to the Linux Foundation as part of our long-standing commitment to develop "open, collaborative ecosystem - offering greater autonomy and multiplying productivity." Launching tools with transparency Open source licenses provide a framework for anyone to explore, test, fork and expand on our technologies. Over the last 15 years, Google has created more than 15,000 public repositories on GitHub. Today, Google continues to maintain more than 5,000 public repositories on GitHub, and more than 1,500 publi ## A2A Protocol - Deep Dive DevFeed: [A2A Protocol - Deep Dive]() Original publisher: [Read original article]() Author: Eric Roby Published: 2026-06-26T13:43:17Z Content type: article Language: en Sources: [System Design Newsletter]() Topics: [Protocol (disambiguation)](), [Artificial Intelligence]() Tags: [a2a](), [a2a-protocol](), [agents](), [ai](), [ai-agents](), [deep-dive](), [protocol]() ### AI overview A deep dive into the A2A Protocol and how AI agents collaborate to solve complex tasks. ### Source excerpt #158: How AI agents collaborate to solve complex tasks ## Demystifying A2UI: How to Make AI Agents "Speak UI" in Your App DevFeed: [Demystifying A2UI: How to Make AI Agents "Speak UI" in Your App]() Original publisher: [Read original article]() Author: Devin Chasanoff Published: 2026-06-26T09:01:02Z Content type: tutorial Language: en Sources: [Angular]() Topics: [Protocol (disambiguation)](), [ui](), [Artificial Intelligence](), [Angular](), [Large Language Model](), [Web](), [web applications](), [Architecture & Design](), [Front end]() Tags: [a2a](), [a2ui](), [adk](), [agentic](), [agents](), [ai](), [ai-agents](), [angular](), [architecture](), [frontend](), [genuis](), [how-to](), [in-app-experiences](), [llm](), [protocol](), [ui](), [web](), [web-app]() ### AI overview This tutorial explains A2UI, a protocol that lets AI agents generate rich, interactive user interfaces for web, mobile, and desktop applications without executing arbitrary code. It presents a developer-oriented mental model covering the protocol's architecture, client-server communication, and rendering flexibility. ### Source excerpt I've spent a fair amount of time experimenting with A2UI, a protocol for building agentic interfaces. Why? Quite simply, because I think the idea of dynamically generating user interfaces is awesome, and despite the fact that this is a relatively new protocol (currently 1.0 RC), I wanted to answer a fundamental question: "How do I incorporate A2UI into my own app?" If you're new to working with generative UIs, it may be challenging to wrap your head around the core concepts. This post is my mental model for how everything works from a developer's implementation perspective so that you can start using it in your own applications. I'm incredibly excited about the future of web apps. So much so that last November, I hosted a livestream called Exploring the future of web apps during which I built my own framework for generating agentic web apps with Angular. A Quick Side Note: While the framework I built for that livestream isn't nearly as flexible or extensible (to use with other web frameworks, for example) as A2UI, the architectural patterns are very similar. If you're still struggling to understand the high-level concepts after reading the A2UI docs and this blog post, give that livestream a watch. The shared concepts will help make it click.What is A2UI? A2UI enables AI agents to generate rich, interactive user interfaces that render natively across web, mobile, and desktop -- without executing arbitrary code. This is exciting to me because A2UI enables: Seamless in-app experiences: Interfaces that adapt dynamically to user intent. Portable UIs: Views that can appear virtually anywhere, serving as a vital part of Gemini web app experiences. Protection: No arbitrary code execution. But to understand A2UI, you first have to understand what it isn't. It's not a framework; it's a protocol. The implications of this are massive. Because it's a protocol, using GenUI doesn't lock you into a single stack. It defines how an LLM agent and a client application communicate about ## A2A in Java: hands on Embabel DevFeed: [A2A in Java: hands on Embabel]() Original publisher: [Read original article]() Author: Aneshka Goyal Published: 2026-06-21T07:01:03Z Content type: tutorial Language: en Sources: [Amex GBT Technology]() Topics: [Embabel](), [A2A protocol](), [Java](), [MCP](), [Spring AI](), [Maven](), [bedrock](), [Large Language Model]() Tags: [a2a](), [agent](), [ai](), [embabel](), [java](), [maven](), [mcp-server](), [software-engineering](), [spring-ai]() ### AI overview A hands-on tutorial for building a Java agent with Embabel. It demonstrates LLM-based story generation and review, Amazon Bedrock integration, a local Spring AI MCP server for word counts, Maven dependency management, and A2A-compliant endpoints. ### Source excerpt Part 2: Hands on with Embabel! In Part 1, we discussed how Embabel works internally. In Part 2, we'll now try to get an application started that has an LLM interaction, talks to local MCP server (for tools), and helps us achieve a goal. This time, we'll also make sure we use A2A protocol for our agent (something Embabel makes easier to do allowing us to focus on core business logic and offloading boilerplate code to Embabel). We'll use the project creator to create a skeleton project for us with some Embabel dependencies and code. uvx --from git+https://github.com/embabel/project-creator.git project-creator Please note we can use Java or Kotlin as our preferred language, I would be leveraging Java. This is a simple story teller agent who writes a story and gets it reviewed (both story generation and review comes from LLM). We'd be using Bedrock for connection to our LLM model. For fetching the word count for a topic, it uses an MCP server which is a Spring AI MCP server running locally. Dependency management is handled using Maven, and the POM file looks like this: 4.0.0 org.springframework.boot spring-boot-starter-parent 3.5.9 com.example.demo-city-agent Demo-city-agent 0.1.0-SNAPSHOT jar My first agent Generated agent project 21 0.3.1 com.embabel.agent ) Original publisher: [Read original article]() Author: Aneshka Goyal Published: 2026-06-16T08:44:44Z Content type: tutorial Language: en Sources: [Amex GBT Technology]() Topics: [Embabel](), [A2A protocol](), [Java](), [Spring AI](), [Agent Framework](), [interoperability](), [Artificial Intelligence](), [Large Language Model]() Tags: [a2a](), [a2a-protocol](), [agent-framework](), [ai](), [embabel](), [interoperability](), [java](), [large-language-models-llms](), [software-engineering](), [spring-ai]() ### AI overview This hands-on article introduces A2A in Java and explores Embabel, a Java agent framework built on Spring AI. It explains how A2A enables interoperability among agents across languages, frameworks, vendors, and platforms, and describes Embabel's use of goal-oriented action planning with existing Java domain logic and structured code. ### Source excerpt Part 1: What is Embabel? A2A, or Agent-to-Agent Protocol, is an open standard (now under the Linux Foundation) that provides a common language for diverse AI agents to communicate, collaborate, and share tasks, enabling interoperability across different frameworks, vendors, and platforms. You can read more about A2A here. A2A makes agents framework and tech stack agnostic, which means agents developed in Python will be able to connect to other agents in Java or any other programming language of choice (given we have A2A protocol compliance). We currently have ADK (Python) and other Python specific frameworks that simplify the development of A2A compliant agents (as you'll read in this blog). This initiative explores creating a comparable Java-specific framework to enable building A2A-compliant agentic applications in Java. Brief about Spring AI Before learning about Embabel, it's important to discuss and know about Spring AI which provides the foundation for Embabel framework. The Spring AI project aims to streamline the development of applications that incorporate artificial intelligence functionality without unnecessary complexity. This project draws inspiration from notable Python projects, such as LangChain and LlamaIndex, but Spring AI isn't a direct port of those projects. The project was founded with the belief that the next wave of generative AI applications will not only be for Python developers but ubiquitous across many programming languages. Spring AI can be used without Embabel (or any other high level framework like ADK java) to create agents and agentic applications. For more info around how to use Spring AI, check out Part 1 and Part 2. What is Embabel? Embabel is an agent framework built on Spring AI, designed to integrate Large Language Models (LLMs) with existing domain logic and structured code in Java applications. It utilizes a Goal-Oriented Action Planning (GOAP) mechanism to allow agents to dynamically determine the sequence of actions needed ## Google introduces the A2Family of open source protocols and tools for AI agents DevFeed: [Google introduces the A2Family of open source protocols and tools for AI agents]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-04-23T18:30:00Z Content type: article Language: en Sources: [Google Open Source Blog]() Topics: [A2A protocol](), [Artificial Intelligence](), [interoperability](), [Model Context Protocol](), [Open Source](), [linux foundation]() Tags: [a2a](), [a2a-protocol](), [a2ui](), [adk](), [agent2agent](), [agents](), [ai](), [ai-agents](), [ap2](), [interoperability](), [linux-foundation](), [open-source]() ### AI overview Google presents the A2Family, a suite of open source protocols and tools for building, connecting, and scaling AI agents. The article describes A2A for agent interoperability, its relationship with MCP and skills, and A2UI for rendering interactive interfaces without executing arbitrary code. ### Source excerpt by Daryl Ducharme, Google Open Source & Alan Blount, Cloud AI At Google, we know that building on open source gives teams the freedom and flexibility to use meaningful technologies faster. Openness drives innovation and security, and it is core to our mission. As we look toward the future of computing, we want to ensure that developers across all open source communities have the foundational tools they need to build secure and collaborative AI systems. That is why we are excited for you to get to know the "A2Family"--a suite of open source protocols and tools designed to help you build, connect, and scale your AI agents. A2A: The cornerstone of agent interoperability The Agent2Agent (A2A) Protocol is an open standard designed to enable seamless communication and collaboration between AI agents. It provides the definitive common language for agent interoperability in a world where agents are built using diverse frameworks and by different vendors. Originally developed by Google, A2A has now been donated to the Linux Foundation. As a famous open source aphorism reminds us: "If you want to go fast, go alone. If you want to go far, go together." A2A brings this collaborative philosophy to AI, allowing agents to delegate sub-tasks, exchange information, and coordinate actions to solve complex problems that a single agent cannot. MCP & Skills: Agents need tools and skills Since day one A2A has loved MCP, and we love skills too ♥. Agents discover, negotiate, converse, make plans, adapt when those plans don't work out - that's a different interaction pattern than a tool and that's what A2A was built for. But for your agents to function, they need access to tools, and instructions on how to use those tools safely and securely. While MCP and A2A might not be from the same origin story, they are a family that works better together. When you're not sure - if it's a quick deterministic resource or action, it's a tool, but if you may end up with a conversation, it's an agent. Ano ## A year of open collaboration: Celebrating the anniversary of A2A DevFeed: [A year of open collaboration: Celebrating the anniversary of A2A]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-04-16T20:55:00Z Content type: opinion Language: en Sources: [Google Open Source Blog]() Topics: [A2A protocol](), [Artificial Intelligence](), [Google](), [interoperability](), [Open Source](), [linux foundation](), [Security](), [Load Balancing]() Tags: [a2a](), [a2a-protocol](), [a2april](), [agent2agent](), [agents](), [ai](), [ai-agents](), [amazon](), [amazon-web-services](), [cisco](), [cryptographic](), [interoperability](), [linux-foundation](), [load-balancing](), [microsoft](), [open-source](), [sap](), [security](), [specifications](), [standard]() ### AI overview Google reflects on the first year of the Agent2Agent (A2A) protocol, including its donation to the Linux Foundation, the growth of its supporting ecosystem, and the release of A2A Protocol v1.0. The article highlights security, enterprise architecture, and interoperability improvements for multi-agent workflows. ### Source excerpt by Patricia Cruz, Google Open Source One year ago, on April 9th, 2025 Google announced the Agent2Agent(A2A) protocol. We saw the need for a "common language" that allows AI agents built on different frameworks to collaborate well across diverse systems. Then, on June 23, 2025 at the Open Source Summit North America in Denver, Mike Smith stood on stage to share a pivotal moment for the future of AI interoperability when Google officially donated the A2A protocol to the Linux Foundation, establishing it as a vendor-neutral, community-governed standard. This move was driven by a core belief: for AI agents to truly transform how we work and live, they must be able to communicate across framework boundaries and organizational silos without being locked into a single provider's ecosystem. By placing A2A under the neutral stewardship of the Linux Foundation, we opened the doors for the entire industry to build, contribute, and innovate together. A Foundation of Partners The formation of the A2A Project was made possible through the support of our founding members, including Amazon Web Services, Cisco, Microsoft, Salesforce, SAP, and ServiceNow. Over the past twelve months, this coalition has grown, with over 100 technology companies now supporting the project. From Prototype to Production The momentum since the donation has been remarkable. What began as a Google-led initiative has evolved into critical infrastructure for horizontal, peer-to-peer collaboration. Just one month ago, in March, the project reached a major milestone with the release of A2A Protocol v1.0, the first stable, fully production-ready version of the standard. Key achievements from the community this year include: Enhanced Security: The implementation of Signed Agent Cards for cryptographic identity verification, ensuring trust in multi-agent workflows. Web-Aligned Architecture: Refined specifications that support familiar load-balancing and security patterns for enterprise-scale deployments. Ecosystem ## Building Agents With Heroku AI and Pydantic AI DevFeed: [Building Agents With Heroku AI and Pydantic AI]() Original publisher: [Read original article]() Author: Anush DSouza Published: 2025-08-08T16:33:37Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [Heroku](), [Pydantic](), [AI Agent](), [Agent Framework](), [Model Context Protocol](), [A2A protocol](), [Python]() Tags: [a2a](), [agents](), [ai](), [ai-agent](), [claude](), [fastapi](), [heroku](), [heroku-ai](), [managed-inference-and-agents](), [mcp-on-heroku](), [model-context-protocol](), [model-context-protocol-mcp](), [news](), [product-features](), [python]() ### AI overview This tutorial explains how to build production-grade AI agents with Heroku Managed Inference and Agents and the Pydantic AI Python framework. It covers Claude model integration, secure code execution, OpenAI-compatible APIs, environment-variable configuration, MCP client and server support, and exposing agents through the A2A protocol. ### Source excerpt Building production-grade AI applications can be complex, but with Heroku and Pydantic AI, developers gain a powerful and reliable solution for integrating advanced AI capabilities. Heroku makes it easy to integrate AI into your applications with Heroku Managed Inference and Agents. With a single click, you can attach powerful Large Language Models like Anthropic's Claude [...] The post Building Agents With Heroku AI and Pydantic AI appeared first on Heroku. ## Serverless A2A with Spin DevFeed: [Serverless A2A with Spin]() Original publisher: [Read original article]() Author: Matt Butcher Published: 2025-07-07T12:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Serverless](), [WebAssembly]() Tags: [a2a](), [agent](), [build](), [how-to](), [serverless](), [webassembly]() ### AI overview A tutorial on how A2A works and how to build serverless agent-to-agent applications with Spin and WebAssembly agents. ### Source excerpt Build serverless agent-to-agent (A2A) apps with Spin. Learn how A2A works and how to build serverless WebAssembly agents.