Multi-Model Orchestration

Hey, thanks for the detailed feature request. Most of what you’re describing already works via Auto and Cursor Router.

Basic Auto is available to everyone, including Free. It automatically picks the right model for your task inside a single conversation while keeping context. From the user’s point of view it’s one chat and one assistant, and the model choice happens under the hood. That’s the transparent optimization layer you described.

The more advanced option is Cursor Router with preference modes Intelligence, Balance, or Cost, which matches your quality-first, speed-first, cost-first idea. One important note is that Router is currently only available on Teams and Enterprise plans. On Teams it’s enabled by default, and on Enterprise an admin enables it in the dashboard. These modes aren’t available on individual plans yet. More details: Introducing Cursor Router · Cursor

A couple options for more explicit control by role:

  • Custom subagents: you can pin a specific model via model: frontmatter in .cursor/agents/*.md like a dedicated agent for review or docs. Just note the model must be available on your plan. Docs: Subagents | Cursor Docs
  • Plan mode: separates planning from execution, so you can work out the plan first and then run implementation. Plan Mode | Cursor Docs

What you don’t have yet from your description is a deterministic pipeline that strictly chains multiple models by stage plan → implement → review → docs using your own stage-to-model rules. Similar requests are discussed here: Personalized Auto Mode and here: # Feature Request: User-configurable model routing rules for the main agent