Hey, thanks for the report. Since Composer 1.5, subagents should work in Auto mode too. Colin confirmed this here.
But we’ve seen reports that for some users it still doesn’t work even on 1.5. You’re on version 2.4.36, so Composer 1.5 should be available for you.
A couple things to help debug:
Try picking a specific model instead of Auto, like Sonnet 4.5 or GPT 5.2. Do subagents work then?
Please send the Request ID from a chat where subagents didn’t connect. Click the three dots in the top-right of the chat, then Copy Request ID. It’s best to turn off Privacy Mode while testing.
This will help us figure out if the issue is specifically Auto with Composer 1.5, or something else.
Update for current version, already at 2.5.17. This time I tried cursor-native agent specifically, still no luck:
In this session I do not have a Task (or subagent-delegation) tool.
My available tools are: Read, Grep, Glob, run_terminal_cmd, TodoWrite, StrReplace, Write, Delete, WebSearch, mcp_web_fetch, GenerateImage, ReadLints, and MCP (call_mcp_tool, fetch_mcp_resource). There is no tool to delegate to or start a subagent like ansible-hetzner-deploy.
So even though the Subagents UI shows ansible-hetzner-deploy and says “Subagents can be invoked by the agent,” the runtime here does not expose that invocation to me. Whether that’s still the 2.4.22+ bug or a different limitation in the current Cursor version (e.g. 2.5+), the outcome is the same: the Task feature is not available to me right now.
If your Cursor version is past 2.5, it would be worth checking Cursor’s changelog or docs for a note that the Task tool was re-enabled; from inside this agent session I can’t see that. For now, I can only do the ansible-hetzner-deploy work directly by following its instructions (e.g. running the ansible wrapper and playbooks myself).
