5 - Orchestrate multi-agent coordination (GH-600)

What is the primary objective of using the /fleet slash command in Copilot CLI?. To execute multiple independent subtasks in parallel using subagents. To bypass the need for a main orchestrator agent during complex refactoring. To automatically commit code changes to a remote repository fleet. To limit the AI's context window to prevent overwhelming the local system.

How does the main Copilot agent determine if a task should be assigned to subagents?. It assigns all tasks to subagents by default to maximize CPU usage. It only uses subagents when the user explicitly names each subagent in the prompt. It checks if the user has a 'Premium Plus' subscription tier active. It analyzes the prompt for subtasks that are independent and parallelizable.

By default, what type of AI model do subagents utilize when running tasks?. A localized model running entirely on the user's hardware. The highest-parameter model currently available in the fleet. The same model used by the main orchestrator agent. A low-cost AI model.

What is a significant advantage of subagents having their own independent context windows?. It doubles the total tokens available for a single sequential operation. It allows subagents to share sensitive variables without the main agent seeing them. It prevents the subagent from being overwhelmed by the full context of the larger task. It ensures that the main agent's history is deleted after every subtask completion.

How can a user specify that a particular subtask should be handled by a specialized custom agent?. By entering the /specialize command before the implementation plan. By setting the 'Agent Priority' variable in the CLI configuration file. By using the syntax @CUSTOM-AGENT-NAME within the prompt. By right-clicking the subtask in the plan view and selecting 'Assign Agent'.

Which factor most directly impacts the consumption of 'premium requests' when using /fleet?. The physical distance between the user and the GitHub fleet server. Only the duration of time the CLI remains open in interactive mode. The number of subagents interacting with the LLM and the multiplier of the models used. The total number of files in the user's local workspace directory.

When would the /fleet command provide the LEAST amount of benefit?. When the task involves refactoring several files at once. When a custom agent profile like Claude Opus 4.5 is selected. When the requested work is inherently sequential and cannot be decomposed. When the user is running the CLI in autopilot mode.

What is the difference between 'autopilot mode' and the '/fleet' command?. Autopilot allows for autonomous task completion, while /fleet enables parallel execution. Autopilot is a paid subscription, whereas /fleet is a free feature for all users. Autopilot only works with single-file tasks, while /fleet works with multi-module tasks. They are identical features and the terms can be used interchangeably.

Custom agents and sub-agent orchestration. Custom agent. Sub-agent. Inference. Parent session.

Which two properties are mandatory when defining a custom agent within the GitHub Copilot SDK?. prompt and infer. name and tools. displayName and description. name and prompt.

What is the default behavior if the 'tools' property is omitted from a custom agent's configuration?. The agent is restricted from using any tools. The agent can only use 'read-only' tools like grep and view. The runtime throws a configuration error at session creation. The agent inherits access to all tools configured for the session.

How does the Copilot SDK runtime primarily determine which custom agent to select for a user's request?. By selecting the agent with the longest system prompt. By checking the alphabetical order of the agent names. By analyzing the tools required by the user's prompt. By matching the user's intent against the agent's name and description.

Which property should be set to 'false' if you want an agent to be invoked only through explicit user requests rather than automatic selection?. isolated. infer. delegation. autoSelect.

In the context of sub-agent orchestration, what is the role of the 'Parent session'?. It provides a shared prompt that all agents append to their own. It defines the global model that all sub-agents must use. It is a secondary backup session used only if the sub-agent fails. It spawns the sub-agent and receives all lifecycle events.

A custom agent can be configured with its own Model Context Protocol (MCP) servers to access specialized data. False. True.

According to the 'Patterns and best practices' section, why should a developer pair a 'researcher' agent with an 'editor' agent?. To allow the agents to review each other's code in a loop. To separate read-only exploration tasks from write-capable modification tasks. To bypass the token limits of a single system prompt. Because the SDK requires at least two agents to enable orchestration.

Which field in the agent configuration is described as a 'unique identifier' for the runtime?. agentKey. displayName. id. name.

Streaming events in the Copilot SDK. Ephemeral event. Persisted event. Delta event. parentId chain.

What is the purpose of the 'parentId' field within the session event envelope?. It identifies the specific sub-agent that generated the event. It serves as a unique identifier for the specific event. It indicates the version of the SDK being used to emit the event. It points to the previous event in the chain, creating a linked list.