Subagent Delegation Not Working in Cloud Agents

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Issue

When I trigger a orchestration rule to call subagents in the cloud, I got this comment back from the LLM:

I’ve detected the @test-subagents trigger phrase. However, as a cloud agent, I don’t have access to Cursor’s subagent delegation system (the /agent-name syntax that would invoke other agent definitions).

This setup works correctly in local Cursor editor sessions.

Setup

Trigger: @test-subagents in .cursor/rules/test-subagents.mdc (alwaysApply: true)

Subagents (in .cursor/agents/):

  • test-agent-sonnet.md (model: claude-4.5-sonnet-thinking)
  • test-agent-opus.md (model: claude-4.6-opus-high-thinking)
  • test-agent-composer.md (model: composer-1)

Expected: When trigger detected, orchestrator delegates via /test-agent-sonnet, /test-agent-opus, /test-agent-composer

Actual: Cloud Agent cannot invoke subagents using /agent-name syntax

Documentation Reference

The docs at Subagents | Cursor Docs state: “You can use subagents in the editor, CLI, and Cloud Agents.”

Question

Have I set something up incorrectly, or is subagent delegation not yet supported in Cloud Agents despite the documentation?

Steps to Reproduce

Try to call an agent with /agent-name in the cloud.

Operating System

MacOS

Version Information

Version: 2.4.28
VSCode Version: 1.105.1
Commit: f3f5cec40024283013878b50c4f9be4002e0b580
Date: 2026-02-03T00:56:18.293Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. You’ve got everything set up correctly. This is the same class of error we’re tracking for the CLI too: Subagents not working in Cursor CLI.

I’ve shared this with the team. We don’t have an ETA yet, but your report helps us prioritize. I’ll post an update here if we get any news.

1 Like

I’m also interested in this resolution, please look into it, it’s very important for long-term development and cloud + orchestration.

Hey all!

This should be working now. Thanks again for the reports.