In my continuous journey to become an AI native developer, I reserve some time every day to discover new tools and try new ways of working. Today I decided to give the new Github Copilot CLI a try.
As developers we spend a significant portion of our day in the terminal. Cloning repositories, installing dependencies, debugging issues, running builds, and navigating codebases—all without leaving the command line. But when you needed AI assistance from Github Copilot, you had to break your flow and switch to your editor or browser.
Other AI vendors like Claude Code even offers a command line first experience, but a similar experience for Github Copilot was missing. Until now.
What is GitHub Copilot CLI?
GitHub Copilot CLI brings AI-powered assistance directly to your terminal. It's a command-line tool that lets you leverage the power of GitHub Copilot without ever leaving your shell. No context switching, no workflow interruptions—just you, your terminal, and an intelligent assistant ready to help.
So far I’ve mostly used AI assistance inside an IDE, so I’m curious to find out how the experience is like.
Getting started is simple
Setting up Copilot CLI takes just a few minutes:
- Install via npm:
npm install -g @github/copilot - Launch: Run
copilotin your terminal - Copilot ask if it could trust the folder I’m running the command from. Let’s go for option 2 and hit Enter.
- Authenticate: Use
/loginto sign in with your GitHub account - Open your browser and enter the one-time code.
- You also need to confirm to which organisations it has accces to.
That's it. No API keys to manage, no complex configuration. If you have a GitHub Copilot Pro, Pro+, Business, or Enterprise plan, you're ready to go.
Requirements: Node v22+ and npm version 10 or later
Time for a simple prompt to get some feedback about our codebase:
And about a specific file:
Let’s explore some features
Editing a file
You can ask Copilot to edit files through the CLI and approve changes. Probably something where I still would prefer to use the IDE but usable to review some changes.
Slash commands and file mentions
A first nice feature I noticed is that you don’t need to remember the commands as the CLI provides autocompletion when hitting ‘/’:
Also if you want to point the CLI to a specific file, the list of files in your directory is shown when hitting ‘@’:
This already makes the command line experience a lot better and brings it close to what we are used in our IDE.
Directory control
As already mentioned in the Getting Started, you have direct control on the folders trusted by the Copilot CLI.
You can see the list of trusted directories using the /list-dirs command:
And add a new directory through the /add-dir command.
What’s next?
There is a lot more to explore, let’s continue tomorrow with a follow-up post. Stay tuned!