Can't get async subagents, nested subagents to work

Support Help
,
1

We’ve been using Cursor subagents for a few weeks now, enjoying the feature very much.

We’ve updated to your latest release (PSB details).

We’re not able to employ the new features:

  1. Async subagents:
    Not by setting is_background: true
    Not by explicitly asking Cursor to employ a background/async subagent.
    Even when explicitly stating agent should not wait for the subagent’s response.

  2. Nested subagents:
    We get the following output from our subagent: I don’t have access to a Task tool to spawn subagents. Here’s what’s ready and how to proceed.
    We’re aware of the issues with composer model, all subagents are based on Claude-4.6-opus-high.

Cursor version details:
Version: 2.5.20 (Universal)
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

4

Hi there!

If you’re using a legacy Request-based plan, please ensure Max Mode is enabled! That should unlock nested subagents.

I think you’re already in touch with our support team via [email protected], and I suggest continuing to work with them there!

6

Done a bit more testing with async subagents – try adding something to the description like “Run in background”

---
name: docs-generator
description: Generates or updates documentation for code. Run in background. Reads source files, infers purpose and usage, and produces clear, concise docs.
model: inherit
readonly: true
---
...

I’m following up with the team on why is_background: true doesn’t seem to be doing anything!

2 Likes
Cursor 2.5: Async Subagents
7

Thanks. Do report back please.

10

This will be fixed in the upcoming 2.6 (is_background: true will be respected)!