Agent orchestration seems to be the new hot problem to be solved in the ecosystem. See also Steve Yegge's most recent posts [1]. Curious to see what tools emerge as the winners of the Cambrian explosion we're probably about to see.
[1] https://steve-yegge.medium.com/the-future-of-coding-agents-e...
This is what we are looking at at one of my clients. A2A clients (Slack, Google Meet, considering email) to A2A Orchestrator server (in-house, might be open-sourced) with specialized subagents for e.g. GitHub issue creation following a specific teams patterns and conventions, hooked up to company-wide MCP gateway with federated OIDC trust for passthrough auth (https://www.gatana.ai)
Works pretty well so far. Biggest issue i foresee for success is user UX for average employee, and actually useful use-cases.
Totally. Yegge's post was fascinating and there was quite a bit of chatter about it internally at my company . I have this feeling that if I could just figure out how to effectively direct 10-20+ coding agents at once, I could supercharge my productivity and bug squashing skills. In some ways his post introducing a suite of new terminology helps to set the stage for this being a whole new world of being a SW engr.
There won't be a single orchestration winner, orchestration will just become ubiquitous in LoB systems. Slack and Github will probably be the biggest targets but it's pretty simple to create a chat bridge that supports adapters to support discord/telegram/etc and you can already do webhook orchestration easily enough.