2.2. The GitHub Copilot CLI
💡 First Principle: The Copilot CLI brings the full agentic model to the terminal, where a huge amount of real work already happens — running commands, wiring scripts, managing files. It is not merely "suggest a command"; it plans, builds, reviews, and remembers across sessions without leaving the shell.
Why this matters: an entire syllabus subgroup is dedicated to the CLI, so expect multiple questions. They test what the CLI is, how it's installed, its commands and session model, and how it generates scripts and manages files. Knowing the CLI is a terminal-native agent (not the old thin command-suggester) is the key framing.
The mental model: a capable shell-savvy colleague who lives in your terminal. You describe an outcome in plain language; they propose and (with your approval) run the commands, write the scripts, and keep track of what you were doing across the session.
⚠️ Common Misconception: "The Copilot CLI is just the old gh copilot suggest/explain extension." The modern GitHub Copilot CLI went GA in February 2026 as a full agentic environment with plan mode, autopilot, parallel sub-agents, and persistent session memory — far beyond one-shot command suggestion.