Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
As of earlier today, all subagents stopped working in Cursor. Cursor now states that it doesn’t have the ability to use Subagents, no matter the model. This happens in both the Editor and the Agents window.
Steps to Reproduce
Ask for any subagent to be spun up, or perform an action which usually spins up a subagent, such as the code-reviewer agent from the superpowers plugin.
Expected Behavior
Cursor should be able to use subagents, as it did previously.
Screenshots / Screen Recordings
Operating System
MacOS
Version Information
Version: 3.1.17
For AI issues: which model did you use?
composer-2, Opus 4.7, Opus 4.6, GPT 5.4
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
Hi @Napoleone_Piani,
On Enterprise teams with request-based plans, subagents are internally forced to use Composer models, regardless of which model you select as your primary. This means that even if you’re using Opus 4.7 or GPT 5.4, subagents still try to run on Composer under the hood. If your team admin has blocked Composer in the model configuration, the subagent capability is removed entirely.
This would explain both the “as of earlier today” timing (if a model configuration change was made recently) and the “no matter the model” behavior.
Two ways to restore subagents:
-
Enable Max Mode – with Max Mode, subagents use your selected model directly instead of being forced to Composer, bypassing the restriction
-
Ask your team admin to unblock Composer – if Composer is allowed again, subagents will work without needing Max Mode
Could you check with your team admin whether Composer models were recently restricted?
A similar report was discussed in this thread with the same root cause.
For full details, see the Subagents docs, specifically the FAQ on “Why is my subagent using a different model?”
That seemed to be the issue. Thanks @mohitjain .
