Grouped Agents and Orchestrators That Can Spawn Sub-Agents With Different Models

Feature request for product/service

Cursor IDE

Describe the request

When building multi-phase workflows, I often split the work into separate phases and manually spin up sub-agents for each one. That matters because each phase has different complexity requirements. Some need high-level reasoning from a more capable model, while others can be handled by a cheaper model.

Right now, this is cumbersome for two reasons.

First, it would be very helpful to support grouped agents in the UI. Instead of showing every sub-agent in one long flat list, related agents could live under a single parent view. That would make multi-phase workflows much easier to navigate and manage, especially when several sub-agents belong to the same plan.

Second, I’d like a main orchestrator agent to be able to spin up sub-agents using different models. In my workflow, each phase has its own complexity level. One phase may require deep reasoning from a top-tier model, while another may only need a lightweight, inexpensive model. Today, I have to create each sub-agent manually and assign the model one by one.

It would be much more powerful if the orchestrator could read a plan file, understand the model requirements for each phase, and automatically spawn the right sub-agents with the right models.

Why this would help
• Better organization for multi-agent workflows
• Easier navigation across related sub-agents
• Lower cost by matching model capability to task complexity
• Less manual setup for phased plans
• More scalable orchestration for complex projects

In short, I’d love support for:
1. Grouped agent views for related sub-agents
2. An orchestrator that can spawn sub-agents with different models based on phase complexity

Operating System (if it applies)

MacOS

1 Like