Plan-defined model switching per step (let plans route actions to different models)

Feature request for product/service

Cursor IDE

Describe the request

I’d love a way to define model routing inside the plan itself. Right now I can create a plan and then select one model to execute it. What I want is: once the plan is created, it should already specify which model to use for which actions/steps — and the executor should be able to switch models accordingly while running the plan.

What I’m looking for:

Plans can declare a default model and allowlisted models.

Individual steps/actions can override the model (e.g. web_search → model B, coding → model C, final_response → model A).

The executor can switch models automatically based on these rules (and optionally request a switch, but only within the plan’s allowlist).

Execution logs show which model ran each step for traceability.

Why I want this:

Use specialized models where they’re strongest.

Reduce cost by routing simpler steps to cheaper models.

Make multi-model workflows first-class and predictable.

1 Like