Cursor 2.4: Subagents

New in Cursor! · Full changelog · Main announcement

We’re excited to introduce Subagents! Subagents are independent agents specialized to handle discrete parts of a parent agent’s task.

How it works

Subagents run in parallel, use their own context, and can be configured with custom prompts, tool access, and models. The result is faster overall execution, more context in your main conversation, and specialized expertise for each subtask.

Cursor includes default subagents for researching your codebase and executing parallel work streams. These will automatically start improving the quality of your agent conversations

You can also define custom subagents. Learn more in our docs.

Useful for

  • Parallel execution: break a complex plan into parallel work streams
  • Deep research: spin up multiple subagents to explore different parts of your codebase

We’d love your feedback!

  • How are subagents handling your complex tasks?
  • Have you tried creating custom subagents yet?
  • What specialized subagent configurations would be useful for your workflow?

If you’ve found a bug, please post it in Bug Reports instead, so we can track and address it properly, but also feel free to drop a link to it in this thread for visibility.

4 Likes

Amazing! Is there a way to override/modify the default subagents? I see in the docs project-defined overrides user-defined, but I cannot find the default subagents anywhere, they are not listed in cursor settings either.

4 Likes

For the moment, no. We will be closely listening for feedback on this (so thank you for sharing!)

The hope is that using models like Composer for subagents (like “Explore”) will significantly speed up tasks that don’t require high-latency models that, despite excelling in certain areas, are slower to respond. This has proved out really well in our testing!

1 Like

The hope is that using models like Composer for subagents (like “Explore”) will significantly speed up tasks that don’t require high-latency models that, despite excelling in certain areas, are slower to respond. This has proved out really well in our testing!

That would be cool if we can switch explore agent to use Gemini 3 Flash instead of overpriced Composer 1 :slight_smile:

4 Likes

By the way, it works well and quickly (at least my Senior Agent didn’t complain)

The FAQ says:

Subagents inherit all tools from the parent, including MCP tools from configured servers.

But the “Specialized expertise” card at the top of the docs says

Configure subagents with custom prompts, tool access, and models for domain-specific tasks.

and the configuration fields only seems to list readonly as being relevant to tools. Which is it?

Subagents do not receive User Rules. So for each Subagent you write down its name, description for the calling Agent, model and its personal rules of conduct.

It’s on par with gemini 3 flash, but costs 3x of gemini

Can a specific model be assigned to sub-agents?
Is it possible to make them use the same model that I’m using in the main conversation?

cant wait to use it :slight_smile:

1 Like

I need my superpowers!

1 Like

Do I need to use specific model in order to make subagents working? It seems subagents won’t be used if I select “Auto” model.

not work(

1 Like

Hey @Able1991

We will be pushing out a fix for this soon. In the meantime, other models (like Sonnet, Opus) should be able to use subagents.

1 Like

For your own subagents, yes! Just make sure model is defined in the frontmatter.

For built in ones (like Explore), not today / not yet.

Can you elaborate on the documentation. If you want to use a claude sub-agent, can you use both .cursor and .claude? I’m used to putting everything in my .cursor folder, but now I see you have .claude and .codex locations. Will the sub-agent not pick to use a claude model if it’s defined in .cursor folder?

Project subagents .cursor/agents/ Current project only
.claude/agents/ Current project only (Claude compatibility)
.codex/agents/ Current project only (Codex compatibility)

Doesn’t seem like i can use the /council command specified here

I don’t see more than 1 agent doing it. Yes i have installed the command. Model compose 1

Hey @Matt_Vagnoni1

From the docs:

When multiple locations contain subagents with the same name, .cursor/ takes precedence over .claude/ or .codex/ .

Hey @sedghi