The terminal footnote — Copilot CLI

This is the shortest lesson in the chapter on purpose. There’s one more surface to mention and then close the book on: the Copilot CLI, a terminal-native way to reach the same assistant.

It is, deliberately, a footnote. This course is IDE-first because that’s where the enterprise audience lives and where the agent features are fullest — and nothing about the CLI changes that. But it exists, and it’s worth a paragraph so you’re not surprised when a colleague mentions it.

The thing to understand is that it’s the same Copilot, not a separate tool to learn. Same GitHub account, same Copilot plan, and — the part that matters for everything you’ve built — it reads the same rules files. The AGENTS.md at the root of orders-service or shared-lib applies in the terminal exactly as it does in VS Code and JetBrains. There’s nothing new to configure and no second copy of your conventions to maintain; you already did that work, and the CLI inherits it.

So when would you reach for it? When you’re already in the terminal and it would be friction to move. You’re in a shell, mid-flow on a git operation or a quick check inside orders-service, and you want to ask the agent something or hand off a small task without switching windows to the editor. That’s the niche: terminal-native moments, not a primary workspace. For the careful, multi-file, review-heavy work this course is built around, you’ll still want the editor — the modes, the diff review, the plan surface all live there.

That’s the whole footnote. Don’t overbuild a CLI habit; treat it as the same assistant answering the door when you happen to already be standing in the terminal.

And that closes the surfaces. You’ve now seen Copilot as the same assistant across VS Code, JetBrains, and the terminal — one account, one set of conventions, three places to stand. Everything left is putting it together into a working rhythm. Next chapter: the daily workflow.