Subagent does not respect model

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Subagent model is not respected and being run with current session model

Steps to Reproduce

start subagent

Expected Behavior

subagent model is used

Operating System

MacOS

Version Information

Version: 3.9.16 (Universal)
VS Code Extension API: 1.105.1
Commit: 042b3c1a4c53f2c3808067f519fbfc67b72cad80
Date: 2026-06-27T06:41:01.941Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Screenshot 2026-07-01 at 12.29.10 PM
Screenshot 2026-07-01 at 12.29.10 PM1132×318 21 KB

Screenshot 2026-07-01 at 12.30.32 PM
Screenshot 2026-07-01 at 12.30.32 PM738×276 20.9 KB

Screenshot 2026-07-01 at 12.31.57 PM
Screenshot 2026-07-01 at 12.31.57 PM980×148 4.83 KB

7

Hey, thanks for the report. This isn’t a bug, it’s the current behavior for request-based plans, including Free, without Max Mode. Subagents are forced to stay on the Composer family to control costs. So when you select GPT-5.5, it fails the check and falls back to Composer 2.5 Fast.

I agree the UX is off here. The subagent editor lets you pick GPT-5.5 even though it won’t apply on your plan, and there’s no warning. I’ll pass this along.

Allowing subagents to use a different model on request-based plans is a feature request that’s being tracked. No ETA yet.

More context in the canonical thread: Can we change the default model used by auto-spawned sub-agents?

8

thanks. confirming that switching to max mode works