Answer: Use fleet mode when the work can be decomposed before execution and each unit can run without waiting for the others, such as multi-file refactors, batch reviews, parallel research, documentation refreshes, and migration tasks. Avoid it for sequential tasks, tightly coupled edits, small tasks, and tasks requiring continuous shared reasoning. Status: Confirmed Entry: tool/github-copilot/agents-and-automation/when-to-use-fleet-mode Revision: 3 Digest: sha256:1627ab14c12e45fc (changes whenever the content changes) Timeline: Created: 2026-11-13T03:28:00Z Last changed: 2026-11-19T13:01:53Z (Best conditions: — → the parent session can create clear units of work, assign one owner per unit, and define what each worker must return) Last verified: 2026-11-20T13:08:17Z Next check: 2026-11-21T13:08:17Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of When to use | when the work can be decomposed before execution and each unit can run without waiting for the others | [1] | 2026-11-20 Good fit: multi-file refactors | Multi-file refactors where each worker owns a file, package, or language SDK | [1] | 2026-11-20 Good fit: batch reviews | Batch reviews where each worker checks a separate diff, module, or alert group | [1] | 2026-11-20 Good fit: parallel research | Parallel research across independent repositories, services, or feature areas | [1] | 2026-11-20 Good fit: documentation refreshes | Documentation refreshes where each worker owns a page or topic | [1] | 2026-11-20 Good fit: migration tasks | Migration tasks where each worker can validate its own slice and report back | [1] | 2026-11-20 When to avoid | Sequential tasks where step 2 needs the concrete output from step 1 | [1] | 2026-11-20 Best conditions | the parent session can create clear units of work, assign one owner per unit, and define what each worker must return | [1] | 2026-11-20 Sources: [1] GitHub. "Fleet mode - GitHub Docs". https://docs.github.com/en/copilot/how-tos/copilot-sdk/features/fleet-mode Role: primary. Accessed: 2026-11-20T13:08:17Z Quote: "Fleet mode is useful when the work can be decomposed before execution and each unit can run without waiting for the others." (Supports: When to use) Quote: "Multi-file refactors where each worker owns a file, package, or language SDK." (Supports: Good fit: multi-file refactors) Quote: "Batch reviews where each worker checks a separate diff, module, or alert group." (Supports: Good fit: batch reviews) Quote: "Parallel research across independent repositories, services, or feature areas." (Supports: Good fit: parallel research) Quote: "Documentation refreshes where each worker owns a page or topic." (Supports: Good fit: documentation refreshes) Quote: "Migration tasks where each worker can validate its own slice and report back." (Supports: Good fit: migration tasks) Quote: "Sequential tasks where step 2 needs the concrete output from step 1." (Supports: When to avoid) Quote: "Fleet mode works best when the parent session can create clear units of work, assign one owner per unit, and define what each worker must return." (Supports: Best conditions) Snapshot SHA-256: 1d15aa855750749299ff6a21d7bda42c2675c70e28081ca308c7a1b46a7b3b28 (captured 2026-11-18T13:03:21Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T13:03:22Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:08:17Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:08:17Z Last attempt: 2026-11-20T13:08:17Z Notes and limitations: Extracted automatically from a single official source (section "When to use fleet mode"). Related: https://latestn.com/tool/github-copilot/agents-and-automation/when-to-use-multiple-agents When should I use multiple GitHub Copilot agents instead of a single agent? https://latestn.com/tool/github-copilot/agents-and-automation/where-to-use-agent-skills Where can I use GitHub Copilot agent skills? https://latestn.com/tool/github-copilot/agents-and-automation/where-to-use-agents Where can I use GitHub Copilot agents? https://latestn.com/tool/github-copilot/agents-and-automation/what-is-agent What is a GitHub Copilot agent? https://latestn.com/tool/github-copilot/agents-and-automation/when-new-tools-take-effect When do new tools take effect after I change them in the GitHub Copilot SDK? https://latestn.com/tool/github-copilot/agents-and-automation/when-to-use-copilot-cloud-refactoring When should I use GitHub Copilot in the cloud for large-scale refactoring? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:01:53Z | changed | Best conditions: — → the parent session can create clear units of work, assign one owner per unit, and define what each worker must return | [1] 2026-11-19T13:01:53Z | changed | When to avoid: — → Sequential tasks where step 2 needs the concrete output from step 1 | [1] 2026-11-19T13:01:53Z | changed | Avoid: tightly coupled edits: Tightly coupled edits where workers would contend for the same files → — | [1] 2026-11-19T13:01:53Z | changed | Avoid: sequential tasks: Sequential tasks where step 2 needs the concrete output from step 1 → — | [1] 2026-11-19T13:01:53Z | changed | When to use: the work can be decomposed before execution and each unit can run without waiting for the others → when the work can be decomposed before execution and each unit can run without waiting for the others | [1] 2026-11-17T13:26:11Z | changed | Avoid: tightly coupled edits: — → Tightly coupled edits where workers would contend for the same files | [1] 2026-11-17T13:26:11Z | changed | Avoid: sequential tasks: — → Sequential tasks where step 2 needs the concrete output from step 1 | [1] 2026-11-17T13:26:11Z | changed | Good fit: migration tasks: — → Migration tasks where each worker can validate its own slice and report back | [1] 2026-11-17T13:26:11Z | changed | Good fit: documentation refreshes: — → Documentation refreshes where each worker owns a page or topic | [1] 2026-11-17T13:26:11Z | changed | Good fit: parallel research: — → Parallel research across independent repositories, services, or feature areas | [1] 2026-11-17T13:26:11Z | changed | Good fit: batch reviews: — → Batch reviews where each worker checks a separate diff, module, or alert group | [1] 2026-11-17T13:26:11Z | changed | Good fit: multi-file refactors: — → Multi-file refactors where each worker owns a file, package, or language SDK | [1] 2026-11-17T13:26:11Z | changed | Best condition: the parent session can create clear units of work, assign one owner per unit, and define what each worker must return → — | [1] 2026-11-17T13:26:11Z | changed | Avoid: Sequential tasks where step 2 needs the concrete output from step 1 → — | [1] 2026-11-17T13:26:11Z | changed | Good fit: Multi-file refactors where each worker owns a file, package, or language SDK → — | [1] 2026-11-13T03:28:00Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/agents-and-automation/when-to-use-fleet-mode/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/agents-and-automation/when-to-use-fleet-mode POST: https://latestn.com/dispute/tool/github-copilot/agents-and-automation/when-to-use-fleet-mode with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/agents-and-automation/when-to-use-fleet-mode?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). When should I use fleet mode in GitHub Copilot? Revision 3, last verified 2026-11-20T13:08:17Z. https://latestn.com/tool/github-copilot/agents-and-automation/when-to-use-fleet-mode (accessed 2026-11-21T10:02:25Z). @misc{LatestN_tool_github_copilot_agents_and_automation_when_to_use_fleet_mode_r3, title = {When should I use fleet mode in GitHub Copilot?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/agents-and-automation/when-to-use-fleet-mode}}, note = {Revision 3; digest sha256:1627ab14c12e45fc; last verified 2026-11-20T13:08:17Z; accessed 2026-11-21T10:02:25Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/agents-and-automation/when-to-use-fleet-mode