Frontier agent can not hand on tasks to composer 2.5

Ideas Feature Requests
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Frontier model is not able to pass a drafted plan to another model for execution (asked specifically, answered not possible specifically)

Steps to Reproduce

Tell frontier agent (i.e. opus 4.7) to draft a plan and also ask frontier agent (i.e. opus 4.7 ) to instruct composer 2.5 model agent to execute it.
this is necessary for us, composer 2.5 is too fast (apparently it picks a line without verifying too much) and needs instead in order to work decently to follow point by point a plan and be re-verified by frontier.
we’re exploring if composer 2.5 can be of any help for coding complex code or if it needs frontier to check everything (hence still not viable)

Expected Behavior

the model type is switched in the IDE or we’re instructed to flip manually in order to kick the composer 2.5 work start

Operating System

Linux

Version Information

Version: 3.4.20
VSCode Version: 1.105.1
Commit: 0cf8b06883f54e26bb4f0fb8647c9500ccb43310
Date: 2026-05-15T02:26:10.351Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Linux x64 6.8.0-111-generic

For AI issues: which model did you use?

opus 4.7 (extra high)

Additional Information

The frontier agents when asked specifically answers "I have no way to pass to composer or check if I’ve passed to it: in order to do that you must open another session and task directly composer).
this obviously create a session without context making composer even more unusable

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

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:

  1. 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

  2. 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.