Disable sub-agents or enable editing default model

Ideas Feature Requests
,
1

Describe the request

Currently, some models start sub-agents by themselves (ex: opus 6 does it a lot).

There is no direct way to either disable that behaviour or select which model the sub-agent should use.

Maybe there could be a way to set a “default” model for sub-agents that are launched by agents.
→ Here I do not mean launching sub-agents that use a pre-configured agent file (which I know we can set the model there), I mean the sub-agents that are created fully autonomously by the main agent.

Current behaviour forces the usage of the “Composer 1.5” model by sub-agents. This model is very expensive and IMO not great.

This causes unexpected costs coming from sub-agents and overall bad quality results from forced model selection.

I know a similar thread exists: Subtasks use composer 1.5, but what I’m asking is different.

Thanks.

(If something exists already for this, please point me to it, couldn’t find anything related to this)

Operating System (if it applies)

MacOS

2 Likes
3

I want to disable subagent too

4

me too

5

Same! how do we disable it?

Do you know which models don’t start them automatically? @b_c

6

Honestly this is very frustating specially as a legacy customer, I am forcer to use maxmode and have 100$ bills if not I will need to suffer from Opus calling composer 1.5 subagents. Sorry but they are BAD. This is very buggy cause sometimes it calls sonnet 4.5 but I cannot seem to control that.
I’m building a 3D-Agent and testing various workflows with Blender-MCP. What I’ve found through my daily tasks — especially with Next.js projects — is that creating a rule to disable subagents entirely produces better results. Opus no longer spawns any subagents, which is an improvement, but still not ideal.

Cursor, please give us the ability to enable, disable, and actually control subagents. Stop forcing Composer on us.

Here is the rule that I have been using to stop subagents, since I cannot control which model it uses better not to.

---

description: CRITICAL - Prevents all subagent usage to avoid Composer model downgrade

alwaysApply: true

---




# MANDATORY: DO NOT SPAWN SUBAGENTS




You MUST NOT use the Task tool under any circumstances. Subagents are forced to use Composer which produces unacceptable results.




Do all work directly:

- Search code: use Glob, Grep, SemanticSearch, Read directly

- Run commands: use Shell directly

- Research docs: use WebSearch and WebFetch directly

- Browser tasks: use MCP browser tools directly

- Complex tasks: handle them yourself in this context, do NOT delegate




This rule has NO exceptions. Never launch a subagent. Never use the Task tool. Do everything in the main agent context.