GitHub Copilot: When to Use /fleet or a Dynamic Workflow
Updating docs across several modules and running the same release checklist every week both take many steps. Which one belongs in /fleet, and which deserves a workflow written in code?
- /fleet asks Copilot to distribute work among subagents.
- A dynamic workflow puts the steps and handoffs in code.
- Keep its extension outside the session to reuse it, and test limits on a small run.
Let Copilot divide the task, or give it a defined process
Choose /fleet for independent work that Copilot can split up, such as updating documentation across modules. Choose a dynamic workflow when checks must run in a particular sequence and stop at a review checkpoint.
| Job | Fit | Process owner |
|---|---|---|
| A question or small edit | Normal chat | Copilot follows the request. |
| Distributing independent work | /fleet | Copilot decides the division. |
| Reusing steps and conditions | Dynamic workflow | The author defines the program. |
GitHub’s fleet guide emphasizes natural parallelism. A small, sequential edit leaves little work to distribute and adds coordination overhead.
A release check repeats the procedure, not the answer
The October 1 announcement gives release checks as an example: execute checks, have an agent assess failures, then pause for human review. A workflow can combine ordinary commands with agent judgment and pass results between stages.
It can use one agent or several. Inputs and findings can change the route through the program, and generated conclusions can vary. A repeatable procedure does not make AI output deterministic.
Creation and registration do not start a run
In CLI, enable experimental features with /experimental on or the --experimental startup option. Describe the required steps and ask Copilot to create the workflow. Then list available workflows and request a run by name, as the usage guide explains.
The default extension is session-scoped. For reuse, move its directory containing extension.mjs into ~/.copilot/extensions/, or into the repository’s .github/extensions/ for teammates. This shares the definition, not saved progress. Check its availability in a new session.
Test a small run before expanding it
Workflow limits cover concurrent and total agents, active time and approximate AI credits. Credit usage is reported after work has run, so work already underway can overshoot the credit limit.
The feature remains in public preview. Current documentation excludes existing annual Pro and Pro+ subscribers still on legacy premium request billing. Check access and storage scope before making a workflow part of a recurring team process.