Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Agent2Agent Protocol (A2A)

developers.googleblog.com

Post reply on HN
Print view View original

21–30 of 293 posts

Re: The Agent2Agent Protocol (A2A)

#21

Post by simonw »

_pdp_ wrote: post #7

Link to repo: https://github.com/google/A2A Docs: https://google.github.io/A2A/#/documentation I think they are trying to ride the MCP hype as well with their own implementation that is also meh. MCP itself is also an over-engineered implementation of AI plugins by OpenAI. Obviously the end game is control over a standard which can act as a strategic tool for boosting valuations or even better product positioning. Th…

"The better approach is to simply use open standards that already exists"

Which ones?

Re: The Agent2Agent Protocol (A2A)

#22

Post by Maxious »

skeeter2020 wrote: post #8
sharemywin wrote: post #5

on it's face this kind of seems dumb. aren't agents supposed to be adaptable enough to handle any protocol?

yeah - I don't get it. I'm all for abstraction but the entire point of using agents at the UX-level is you didn't need a single agreed-upon protocol to make it work. Feels like they're using the old Microsoft fire and motion strategy to keep people busy on their tech, or artificially introduce structure & coupling that - suprise - benefits the maker of shovels, not the diggers.

> In infantry battles, he told us, there is only one strategy: Fire and Motion. You move towards the enemy while firing your weapon. The firing forces him to keep his head down so he can’t fire at you.

https://www.joelonsoftware.com/2002/01/06/fire-and-motion/

Re: The Agent2Agent Protocol (A2A)

#23

Post by dleeftink »

> Hiring a software engineer can be significantly simplified with A2A collaboration

Why not abstract away the applicant altogether, outsourcing the search for talent that make these very systems tick. Let the candidate microtrading really take off, there's always a better candidate in the pipeline after all

Re: The Agent2Agent Protocol (A2A)

#27

Post by riku_iki »

mindcrime wrote: post #13

Great, another Agent 2 Agent protocol. One more of those and we'll have a complete set! OK, I'm being a little bit facetious. But there has been an awful lot of work in this space (or closely related space). Going back to FIPA[1], KQML[2], DAML+OIL[3], etc., up through the more recent AGNTCY[4] and Agent Communication Protocol[5] stuff, there's a lot "out there". [1]: http://www.fipa.org/ [2]: https://en.wikipedia.or…

Now we can have 4 router startups on top of this

Re: The Agent2Agent Protocol (A2A)

#28

Post by burningion »

_pdp_ wrote: post #7

Link to repo: https://github.com/google/A2A Docs: https://google.github.io/A2A/#/documentation I think they are trying to ride the MCP hype as well with their own implementation that is also meh. MCP itself is also an over-engineered implementation of AI plugins by OpenAI. Obviously the end game is control over a standard which can act as a strategic tool for boosting valuations or even better product positioning. Th…

MCP was originated at Anthropic, and has been adopted by OpenAI, Github, Cloudflare, and more.

It's completely open, with active engagement and direction from the community:

https://github.com/modelcontextprotocol/modelcontextprotocol

I don't think it would have such wide adoption so rapidly if it were an "over-engineered implementation".

Re: The Agent2Agent Protocol (A2A)

#30

Post by AndrewKemendo »

These protocols are to put handlers between you and your own data so they can sell it back to you via “search.”

Companies who are betting their future on LLMs realized a few years ago that the data they can legally use is the only long term difference between them, aka “moat.”

Now that everyone has more or less the same public data access, and a thin compute moat is still there, the goal is to transfer your private textual data to them forever so they have an ever updating and tuned set of models for your data

Post reply on HN