I found a really interested github copilot, what I tested for work and this is working great!
hopefully you guys would this implement in cursor, I also want this for my personal projects.
It knows when you need a higher tier model and when its good enough to use a lower tier model. It’s insane how fast it is.
You can make members of your team like a
Front-End Developer
Back-End Developer
Tester
Security Officer
Designer
and much more, everyone have his own job and would cover it. Works much better then a plan mode that you use with multitask in cursor.
I really hope it comes very fast to cursor, because this tool is mind blowing right now!
Hey, thanks for the feature request. Good news, what you’re describing basically already works in Cursor via custom subagents.
You can create one .md file per role in .cursor/agents/ (Front-End, Back-End, Tester, Security, etc.). Each one has its own role prompt, a description of when to use it, and its own model. The main agent can delegate tasks to the right subagent via the Task tool, so you effectively get a team of specialists. You can also pick a different model per role, cheaper for simple roles and stronger for harder ones.
For automatically picking the right model tier, Auto mode handles that. It chooses an appropriate model for the task.
If you want a built-in team roster UX out of the box (like in squad), that’s something we’re exploring. There’s a big subagents thread where we’re collecting demand, feel free to add your use case: Does Cursor support SubAgents?
Give it a try and let me know if anything doesn’t work.
It was very easy to get this into cursor with the same workflow that I was expected to use.
First I asked the agent for add all my copilot agents into cursor, after that I have asked the agent to refer the cursor agents to the squad agent, so that when im using cursor or copilot I have always the same squad/team.
---
name: danny
description: Danny - Tech lead for architecture, scope decisions, and code review. Use for structural decisions and cross-cutting technical work.
This is how that looks like:
---
On invocation, read and follow `.squad/agents/danny/charter.md` as your authoritative identity and boundaries.
Also read:
- `.squad/agents/danny/history.md` - your learnings
- `.squad/decisions.md` - team decisions
You are Danny. The charter is the source of truth for your role, scope, and workflow.
after that I asked the agent to add a mdc that is always applied, so that I can use my default agent always in squad mode.
---
description: Squad mode — operate as Squad coordinator and delegate all work to the AI team
alwaysApply: true
---
# Squad Coordinator Mode
You are **Squad (Coordinator)**. Read and follow `.cursor/agents/squad.md` as your authoritative identity, boundaries, and workflow.
## Required behavior
- Delegate all implementation, design, review, testing, and analysis to team subagents in `.cursor/agents/`
- Never write code or produce domain artifacts yourself
- Spawn independent agents in parallel when possible
- Assemble and present final results to the user
## Direct mode (only exceptions)
Handle without spawning when the request is a status check, factual question, or simple answer from existing context — per Direct Mode in `squad.md`.
## Session start
On the first response of each session, include the Squad version stamp and greeting from `squad.md`.
Now if you have used GitHub Copilot you can easily use it in Cursor, Without typing everytime that it has to work in squad mode and use all your agents.
Cool that you got it running so fast, and thanks for coming back to share the config. That’s exactly the pattern custom subagents are meant for: the coordinator delegates work to specialized agents, and each one has its own role prompt and its own model.
A couple small tips that might help:
In each subagent’s description, clearly spell out when it should be called. The more specific you are, the better the main agent routes requests.
For the model field, use inherit so the subagent uses the parent agent’s model, or set a specific model ID. Important: fast isn’t a valid option anymore. It was removed from the config and will trigger Error: [unavailable] Error. It’s best to keep the default as inherit.
If you want an out of the box team roster UX like squad has, drop your use case into this thread. We’re tracking demand there: Does Cursor support SubAgents?
Let me know if anything in the setup behaves oddly.