GitHub Copilot CLI Tips & Tricks — Part 3: Parallelizing Work

GitHub Copilot CLI's /fleet command enables parallel task execution by breaking complex requests into subtasks handled by separate subagents simultaneously. The typical workflow involves creating a plan in plan mode (Shift+Tab), then either accepting autopilot with /fleet or manually invoking /fleet. The /tasks command provides a control panel to monitor, inspect, or kill subagent tasks. /fleet works best for naturally parallelizable work like writing test suites, applying consistent changes across modules, or generating boilerplate for multiple components. It's less suited for tasks with sequential dependencies, ambiguous goals, or small single-file jobs.