Hey, that’s expected behavior, not a bug. The model can’t switch itself to a different model within the same session, but you’ve got two options for this use case:
-
Plan Mode, best fit for your case:
Turn on Plan Mode, draft the plan with Opus 4.7, then switch the model to Composer 2.5 and run execution. The plan context stays in the chat. This is the workflow you’re describing, draft a plan then execute with another model. More details: Plan Mode | Cursor Docs -
Subagents via the Task tool:
The parent agent, Opus 4.7, can spawn subagents via the Task tool. By default they run on Composer 2.5. One important detail is that a subagent only gets the task description, not the full parent chat context, so for complex tasks Plan Mode usually works better. More details: Subagents | Cursor Docs
So when Opus said I have no way to pass to composer, that’s technically true for an automatic switch, but it didn’t mention these two mechanisms.
A full inter model handoff in one session with shared context is a known request. There are a few related threads: I want to change the model used by Subagent system, Subagents are not useful if we cant select their model. There’s no ETA yet.
Try Plan Mode and let me know if it fits your workflow.