Model inheritance discrepancy in sub-agent

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Although the sub-agent is set to “Model: Inherit” and the parent agent is Gemini 3.1, the system is defaulting to Composer 2 Fast. Please see the attached screenshot for the configuration mismatch.

Steps to Reproduce

Setup a sub-agent with Model: Inherit. Then invoke it from the agent-chat having chosen “gemini 3.1” as the model for the agent chat.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.3.12
VSCode Version: 1.105.1
Commit: 75c0dfd29aecf2cc208dbaf761d5cc459c601aa0
Date: 2026-05-06T03:47:52.249Z
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: Darwin arm64 24.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

I have the same thing even if I set a sub agent to a specific model it still always uses Composer 2 Fast although it does not show up as a request in my usage but I am seeing the results are not as good as when I remove the sub agent and use claude-opus-4-7-thinking-xhigh. Also if you click on the agent it opens a new tab but you can’t see what the agent is doing it just says Loading Chat

Version: 3.2.21
VSCode Version: 1.105.1
Commit: 806df57ed3b6f1ee0175140d38039a38574ec720
Date: 2026-05-03T01:46:14.413Z
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: Darwin arm64 24.6.0

Hi @Nikolay_Kolev Thanks for reaching out. This is actually intended behavior due to the enterprise plan structure that you’re on. Your enterprise plan requires Max Mode to be enabled, otherwise all subagents are routed to use Composer 2. So all you need to do is Enable Max Mode, and then your desired subagent model choice will be used.

Let me know if you have any follow-up questions!

Do you mind sharing your Cursor account with me? Feel free to DM me… your forum email doesn’t come back to an active cursor subscription

[email protected]

Hi Paul — thanks for sharing your account, which helped a lot, and sorry for the delay. I can see you’re on a legacy enterprise plan, which explains what you’re seeing. There are really two separate things going on:

1. Subagents running as “Composer 2 Fast” - On legacy enterprise plans, subagents are routed to Composer (and not billed) whenever the parent agent isn’t in Max Mode — that’s why you don’t see a request for them. The fix is to enable Max Mode and leave the subagent on model: inherit so it picks up your parent model (e.g. Opus). The current enforcement around subagent selection on your plan is stronger when you choose Inherit rather than explicitly picking a named model as your Subagent of choice.

2. The “Loading Chat” tab
That’s a separate bug we’ve already fixed. It was present on your build (3.2.21), so updating Cursor to the latest version should resolve it.