I don't know how people steer multiple agent sessions in parallel. The constant cognitive switching is exhausting and you miss moments unless you are cli jumping. It is like being an operator.

I have been thinking about this and I think it might work well for established code bases that already exhibit specific patterns that are used over and over again. E.g. a CRUD app with a OpenAPI spec, a controller layer, a service layer, a repository layer, or even good old MVC for that matter. With these established patterns it wouldn't be unthinkable to provide an orchestrator agent a set of requirements that are detailed enough for a group of agents to implement, each agent focusing on a different type of task including an Q/A agent. I'd imagine you end up with one or more PRs for you to review and squash & merge when you're happy with it.

Edit: What I mean is that these agents would work autonomously until their task is accomplished. They can ask for clarification if they require it.