Answer: Sub-agents coordinate through explicit coordination state rather than implicit shared memory: the parent agent decomposes work into todos, each sub-agent owns one todo, and the orchestrator dispatches workers whose dependencies are already complete. Each sub-agent claims exactly one ready todo by setting status = 'in_progress', works only on that todo's scope, and sets status = 'done' when complete or 'blocked' with a reason when it cannot proceed. Status: Confirmed Entry: tool/github-copilot/agents-and-automation/sub-agent-coordination Revision: 3 Digest: sha256:558b522a73a6ecf7 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:28:00Z Last changed: 2026-11-19T13:01:54Z (claim rule: — → Claim exactly one ready todo by setting status = 'in_progress') Last verified: 2026-11-20T13:08:18Z Next check: 2026-11-21T13:08:18Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of coordination mechanism | explicit coordination state instead of implicit shared memory | [1] | 2026-11-20 work decomposition | The parent agent decomposes the work into todos, each sub-agent owns one todo | [1] | 2026-11-20 dispatch rule | the orchestrator dispatches workers whose dependencies are already complete | [1] | 2026-11-20 claim rule | Claim exactly one ready todo by setting status = 'in_progress' | [1] | 2026-11-20 completion status | Set status = 'done' when complete | [1] | 2026-11-20 blocked status | Set status = 'blocked' when it cannot proceed, and include the reason | [1] | 2026-11-20 state machine | pending -> in_progress -> done | [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:18Z Quote: "Fleet mode relies on explicit coordination state instead of implicit shared memory." (Supports: coordination mechanism) Quote: "The parent agent decomposes the work into todos, each sub-agent owns one todo" (Supports: work decomposition) Quote: "the orchestrator dispatches workers whose dependencies are already complete" (Supports: dispatch rule) Quote: "Claim exactly one ready todo by setting status = 'in_progress'" (Supports: claim rule) Quote: "Set status = 'done' when complete." (Supports: completion status) Quote: "Set status = 'blocked' when it cannot proceed, and include the reason." (Supports: blocked status) Quote: "pending -> in_progress -> done" (Supports: state machine) 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:18Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:08:18Z Last attempt: 2026-11-20T13:08:18Z Notes and limitations: Extracted automatically from a single official source (section "How sub-agents coordinate"). Related: https://latestn.com/tool/github-copilot/agents-and-automation/subagent-model-selection How do I choose a specific model for a subagent in GitHub Copilot CLI? https://latestn.com/tool/github-copilot/agents-and-automation/supported-coding-agents Which coding agents are supported by GitHub Agentic Workflows? https://latestn.com/tool/github-copilot/agents-and-automation/supported-third-party-agents Which third-party coding agents does GitHub Copilot support? https://latestn.com/tool/github-copilot/agents-and-automation/start-task-with-prompt How do I start a Copilot task with a prompt? https://latestn.com/tool/github-copilot/agents-and-automation/steer-agent-while-working How do I steer a GitHub Copilot agent while it is working? https://latestn.com/tool/github-copilot/agents-and-automation/stop-archive-agent-session How do I stop or archive a GitHub Copilot agent session? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:01:54Z | changed | claim rule: — → Claim exactly one ready todo by setting status = 'in_progress' | [1] 2026-11-19T13:01:54Z | changed | claim action: Claim exactly one ready todo by setting status = 'in_progress' → — | [1] 2026-11-19T13:01:54Z | changed | coordination mechanism: explicit coordination state → explicit coordination state instead of implicit shared memory | [1] 2026-11-17T13:26:12Z | changed | blocked status: — → Set status = 'blocked' when it cannot proceed, and include the reason | [1] 2026-11-17T13:26:12Z | changed | completion status: — → Set status = 'done' when complete | [1] 2026-11-17T13:26:12Z | changed | claim action: — → Claim exactly one ready todo by setting status = 'in_progress' | [1] 2026-11-17T13:26:12Z | changed | dispatch rule: — → the orchestrator dispatches workers whose dependencies are already complete | [1] 2026-11-17T13:26:12Z | changed | blocked step: Set status = 'blocked' when it cannot proceed, and include the reason → — | [1] 2026-11-17T13:26:12Z | changed | completion step: Set status = 'done' when complete → — | [1] 2026-11-17T13:26:12Z | changed | claim step: Claim exactly one ready todo by setting status = 'in_progress' → — | [1] 2026-11-17T13:26:12Z | changed | orchestrator dispatch: the orchestrator dispatches workers whose dependencies are already complete → — | [1] 2026-11-17T13:26:12Z | changed | coordination mechanism: explicit coordination state instead of implicit shared memory → explicit coordination state | [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/sub-agent-coordination/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/sub-agent-coordination POST: https://latestn.com/dispute/tool/github-copilot/agents-and-automation/sub-agent-coordination with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/agents-and-automation/sub-agent-coordination?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do sub-agents coordinate in GitHub Copilot fleet mode? Revision 3, last verified 2026-11-20T13:08:18Z. https://latestn.com/tool/github-copilot/agents-and-automation/sub-agent-coordination (accessed 2026-11-21T10:00:16Z). @misc{LatestN_tool_github_copilot_agents_and_automation_sub_agent_coordination_r3, title = {How do sub-agents coordinate in GitHub Copilot fleet mode?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/agents-and-automation/sub-agent-coordination}}, note = {Revision 3; digest sha256:558b522a73a6ecf7; last verified 2026-11-20T13:08:18Z; accessed 2026-11-21T10:00:16Z} } 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/sub-agent-coordination