A month or so ago, a colleague was running some code my team owned on his machine and hit a niche Windows kernel-related Python issue. We were debugging it together, but kept having to relay information between our coding agents, mine understood the codebase, while his had the context of the environment where it was actually failing.
At some point I realized we were basically acting as the message bus between them, copying findings and questions back and forth.
That made me wonder, why not just let the agents work together directly?
I found A2A and built toli, a local daemon that an existing agent can connect to over MCP, giving it the plumbing to discover and work with A2A peers, including another person’s toli-connected agent on another machine.
It also works locally. I use it to let two of my agents working on sister codebases collaborate on bugs and design without having to give either agent both repos.
Would love feedback:
[https://github.com/arjunvlama/toli](https://github.com/arjunvlama/toli)
Comments URL: [https://news.ycombinator.com/item?id=50194681](https://news.ycombinator.com/item?id=50194681)
Points: 1