Virtual development teams made of AI agents: hype cycle or real shift in workflows?

For the past couple of months I've been reading a lot about virtual AI teams and agent orchestration in software development. The idea is straightforward: instead of one universal agent handling a task, multiple specialized roles work on it together. Architect plans, backend writes code, QA reviews the output, and so on. I was pretty skeptical at first. It felt like just another layer on top of Cursor, Codex, or Claude Code. But scrolling through a few threads here I kept seeing people mention tools like BridgeApp or AgentFlow that take a different angle entirely, full workflows with dedicated roles, approval steps, and context passed between stages rather than just one agent doing everything... As far as I can tell, in practice the virtual team lives inside each individual project: an architect agent, a CTO agent, a backend agent, a frontend agent, an analyst, and a QA agent. Any agent with whatever skill set is needed. Each one runs its own model: backend might use Claude Code, frontend might run on Codex, depending on what fits the task best. And any team member, even a non-developer like an AI engineer or a marketing manager, can choose which model their agent runs on. Sounds promising, but has anyone actually built something like this? I'm trying to get a real sense of the effectiveness and practical gains from multi-agent systems or agent orchestration in development. My current take: it looks like over the next year or two, the competition won't be between individual agents anymore, it'll be between entire AI teams and how well they collaborate within a workflow.