Both the GitHub Copilot CLI and Visual Studio Code now support calling custom subagents from the…
@burkeholland26K followers
13,813 views
33 Comments
Comments from the original post on X (Twitter)

@dylanjhall
@github @code Well done! Exactly what I was looking for.
2 likes

@burkeholland
@github @code Ty!

@MarkJohnson_SA
@github @code If I issue a single premium request that invokes subagents, am I billed for a single premium request or 1+n for each subagent?
1 like

@arun_sankr
@github @code You guys absolutely cooked with the subagents. It's a game changer!
1 like

@franzhemmer
@github @code Excellent video Burke! Thanks for sharing!!
1 like

@burkeholland
@github @code ty franz!

@Daniel00Higgins
@github @code Waiting for sub-agent beast mode lol
1 like

@Remoty_AI
Subagent orchestration is where things get really interesting for distributed teams. Imagine each team member having specialized agents that coordinate async, handling code reviews, docs updates, and deployments in parallel. This is the kind of workflow we're exploring at Remoty for remote teams. The future of dev tooling is multi-agent.
1 like

@yuvalav
@github @code Loved it!!! I just finished uploading my brand new GitHub Copilot 101 to YouTube, and I covered custom agents really quickly - LOVED the orchestrator use case!!! Here's my new copilot 101 if you'd like to check it out:
1 like

@terryaney
@github @code I haven't installed your agents yet, but tried your example 'Use Opus, Gemini, and Codes to review this code...blah blah'. Once it ignored and just reviewed with current model other time it replied with image. I see you went to terminal before you did it. Only CLI?

@burkeholland
@github @code CLI only atm if you are just doing it in the prompt. In @Code you need to specify custom agents with the model in the front matter...
1 like

@sohocine
@JamesMontemagno @github @code /fleet does feel like magic.

@draginol
@github @code Thanks to your work on the ACP we can support this in Clairvoyance. The agents will specialize out the work.

@yuvalav
@github @code Couldn't find the link in the comments for some reason so there goes:

@franzhemmer
Installing your agents Burke, I noticed that I don't have the 'memory' tool available. I remember seeing it in the built-in section at some point but it's not there atm. Using the latest VSCode Insiders. Is your memory reference to an installed MCP Server outside of the built-in ones?

@burkeholland
@github @code No it should be there. Just enable in settings ?
1 like

@franzhemmer
@github @code That was it! Thank you. Should've checked ...

@johnzabroski
@github @code This was a pretty good tutorial but shouldn't the product just do this vs. needing to teach people how to do it.

@douglasfugazi
@github @code Hey Burke, this is an awesome video! As an SDET, I would like to adapt these Orchestrators to Agents specialized in Testing. Could you please share the repository with the Architect.agent. md documentation? Thank you for sharing!

@xcrap
Oh this multi agent is a dream, I can already see asking for a design improvements using both claude and gemini3 and then use the best of them all, but this kind of use will be very expensive so out of reach, but super powerful. Even multiple agents for code review and having them check each other is amazing, but still very expensive these runs.







