Sub-agent uses wrong model despite Composer 2.5 being set

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor version: 3.15.6 (Cursor > About Cursor)

Operating system: macOS 26.5.2 (Darwin 25.5.0)

Steps to reproduce:

  1. Configure a sub-agent to use Composer 2.5 as its model.
  2. Run a task that invokes that sub-agent (e.g. via the Task tool or sub-agent workflow).
  3. Check which model the sub-agent actually used.

Expected behavior:
The sub-agent should run on Composer 2.5, matching the model selected in its configuration.

Actual behavior:
The sub-agent ran on cursor-grok-4.6-high-fast instead of Composer 2.5, despite Composer 2.5 being set in the sub-agent configuration.

Screenshots or screen recordings:
(Optional — add a screenshot of the sub-agent model setting and/or the model shown in the sub-agent run if you have one.)

Request ID: 74454024-2344-4a00-8401-73a42ed767a9

Additional context (optional to include):
Sub-agent model selection appears to be ignored or overridden; the run used a different model than configured.

Steps to Reproduce

Steps to reproduce:

Configure a sub-agent to use Composer 2.5 as its model.
Run a task that invokes that sub-agent (e.g. via the Task tool or sub-agent workflow).
Check which model the sub-agent actually used.

Expected Behavior

The sub-agent should run on Composer 2.5, matching the model selected in its configuration.

Screenshots / Screen Recordings

Screenshot 2026-08-13 at 5.41.31.png
Screenshot 2026-08-13 at 5.41.31.png1338×146 7.83 KB
Screenshot 2026-08-13 at 9.40.33.png
Screenshot 2026-08-13 at 9.40.33.png1822×850 55.6 KB

Operating System

MacOS

Version Information

Operating system: macOS 26.5.2 (Darwin 25.5.0)

Cursor version: 3.15.6 (Cursor > About Cursor)

For AI issues: add Request ID with privacy disabled

74454024-2344-4a00-8401-73a42ed767a9

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @Or_Anaki
Thanks for the report - this isn’t your config. When the main agent names a model itself while spawning a subagent, that choice currently wins over your Explore Subagent Model setting.

So to keep Explore on Composer 2.5 today, run the main chat on Composer 2.5 too. Turning off models you don’t want under Cursor Settings → Models helps as well, though not when it’s the model the main chat is already running on.

This is an issue we’re tracking - same behavior in this thread: Wrong subagent model chosen automatically. I’ll post here when there’s an update.