15 comments

[ 4.1 ms ] story [ 46.5 ms ] thread
This looks great. Open-source work in multi-agent systems is still quite fragmented, so having an A2A-compatible framework feels very useful.

A question: how difficult would it be to plug in custom agent personalities or domain-specific tools? If you have a roadmap or examples, I’d love to see them.

Nice work — making multi-agent networks A2A-compatible in an open-source framework looks very promising.
Can someone please explain what this means? I'm familiar with agentic development workflows but have no clue what this means and what I can do with it? Is it something like n8n, to connect agents with some work flow and let the work flow do stuff for me?
Fancy logo, has a website, sudden rise in stars.

Checks all the boxes of open-source software that's waiting for enshitification.

> Star Us on GitHub and Get Exclusive Day 1 Badge for Your Networks

This made me close the tab.

Stars have been gamed for awhile on GitHub, but given the single demo, my best guess is that this is trying to build hype before having any real utility.

Yeah I have to say that and the comments in this thread make me feel very ... directed.
If being thorough is wrong, then what exactly is right?
I've been looking at all of the agent talk this past year with an open mind.

But I still do not know what a real use case for these would be (and don't say a travel agent). What is the point of these swarms of agents?

Can someone enlighten me?

Agents in C# seem much better than in Python or Typescript, wish we could see more frameworkers take that route.
Does anyone have any good resources on A2A in general?
What is the difference from AutoGen?
Frameworks like AutoGen are used to build individual agents or agent teams, while OpenAgents is designed to connect countless such teams and individuals into a vast, dynamic, and scalable ecosystem.