AI / GitHub Copilot CLI Fundamentals Interview Questions
What is the /fleet slash command and what problem does it solve?
The /fleet command allows Copilot CLI to spawn multiple subagents that work in parallel on different parts of a complex implementation plan. This dramatically speeds up multi-step tasks that would otherwise need to be executed sequentially.
# Example: implement a feature with multiple independent components /fleet # Copilot divides the work into parallel sub-tasks: # Subagent 1: Update the database schema # Subagent 2: Write unit tests # Subagent 3: Update API documentation # All run simultaneously - dramatically faster than sequential # You can monitor progress from GitHub.com or mobile # while /fleet coordinates the subagents in the background
How /fleet works:
- Copilot analyses your task and identifies parts that can be worked on in parallel
- It spawns subagents, each with their own context and tool access
- Results are coordinated and merged
- You stay in control - you can monitor, steer, and merge from GitHub.com or GitHub Mobile
Typical use case: large features that span multiple files or subsystems - e.g. adding a new API endpoint (requires schema change + controller + tests + docs). Without fleet, Copilot does these sequentially; with fleet, they run in parallel.
What is the primary benefit of using the /fleet command in GitHub Copilot CLI?
While /fleet is coordinating subagents in the background, from where can you monitor and steer the work?
More Related questions...
