Just playing devils advocate as I think your accusation isn’t based on much merit and is quite a big claim to make.
Star counts go vertical when you launch your project and it's warmly received. ~850 stars in 11 days for an AI project doesn't seem at all crazy to me.
The README also contains a mild inducement to star the repo.
> Star Us on GitHub and Get Exclusive Day 1 Badge for Your Networks
Seems sufficient to explain any inauthentic behavior. Growth hacking tactics are certainly not typical of open source projects, but how that should factor into your judgment of this project's trustworthiness, I can't say. Caveat emptor.
This appears, to me, like an LLM-agent descendent of these earlier multi-agent systems.
I lost track of the research after I left academia -- perhaps someone here can fill in the (considerable) blanks from my overview?
Checks all the boxes of open-source software that's waiting for enshitification.
If you are a rustacean, We are building something in the a2a space as well. Tho we don't have sudden increase in stars :/
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.
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?
I can somewhat answer this to best of my knowledge.
Right now, businesses communicate with REST Apis.
That is why we have API gateways like AWS Gateway, Apigee, WSO2 (company i used to work in), Kong, etc so businesses can securly deploy and expose APIS.
As LLMS gets better, the idea is we will evenutally move to a world where ai agents do most of business tasks. And businesses will want to expose ai agents instead of APIS.
This is where protocols like a2a comes in. Google partnering with some other giants introduced a2a protocol a while ago, it is now under linux foundation.
It is a standard for one agent to talk to another agent regardless of the framework (langchain, crewai etc) that is used to build the agent.
Everyone will have their own versions of the rest endpoints, their own version of input params, and lots and lots of docs scatterd.
A standard, will help the ecosystem grow. Tooling, libraries etc.
Either the AI can figure it out, and it doesn't matter if there is a standardized protocol. Or the AI can't figure it out, and then it's probably a bad AI in the first place (not very I).
The difference between those two possibilities is a chasm far too wide to be bridged by the simple addition of a new protocol.
caryzhang1•3h ago
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.
zomux2000•3h ago
Example config: https://github.com/openagents-org/openagents/blob/develop/ex...
We are doing the final testing, and this feature should be working very soon.