I’m a Cursor Enterprise user, and I’d like to advocate for the ability to dynamically specify sub-agent models. While I can achieve this in Copilot, I’m currently limited in Cursor.
Here’s a simple example: I use one sub-agent for implementation and then spawn three separate sub-agents for review—each using a different model: GPT-5.5, Gemini-3.1-Pro, and Opus-4.6. In my testing, I’ve found that it’s rare for all three models to pass the implementation on the first try, which highlights why model diversity is so critical for specific tasks.
I’m aware that I could manually create three separate sub-agent files and hardcode the model in each. However, that doesn’t scale. In my actual workflow, I might have nearly a hundred sub-agents. More importantly, the choice of model shouldn’t be hardcoded within the sub-agent itself; it should be dynamically decided by the Orchestrator model based on the context.
Cursor needs to support dynamic model assignment at the time of calling a sub-agent, similar to how Copilot handles it. This level of control is essential for complex, multi-agent orchestration.