Skip to main content

Github Copilot on the command line

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 copilot in 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 /login to 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!

More information

GitHub Copilot CLI: How to get started - The GitHub Blog

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more