Source: GitHub Blog

Welcome to GitHub Copilot CLI for Beginners!

In this series (available in video and blog format), we’ll give you everything you need to get started using GitHub Copilot CLI, from your first prompt to tips for navigating the command line like a pro!

• Video playlist: GitHub Copilot CLI for Beginners (YouTube)
• Blog series: GitHub Copilot CLI for Beginners (GitHub Blog)
• Product page: GitHub Copilot CLI

What You’ll Learn

In this blog post we’ll cover the two main modes of the CLI:

1. Interactive mode – a REPL‑style experience where you can iteratively refine prompts.
2. Non‑interactive mode – a one‑shot command that runs a single prompt and returns the result.

You’ll learn:

• The differences between the two modes.
• How to enter each mode.
• When each mode is most useful.

Let’s Dive In!

Ready to start? Continue reading to explore interactive vs. non‑interactive usage and become a Copilot CLI pro.

What Is GitHub Copilot CLI Interactive Mode?

Interactive mode provides a back‑and‑forth, chat‑like experience with Copilot CLI.
When you launch the CLI with the copilot command, you are automatically placed in interactive mode—the default behavior.

• Interactive mode – a persistent session where you can ask questions, review responses, and follow up with additional prompts.
• Non‑interactive mode – a one‑off request that returns a single answer without opening a session (covered later).

How to Enter Interactive Mode

1. Start the session

   copilot

2. Grant folder access (if prompted) – Copilot needs permission to read and modify files in the current directory.
3. Ask a question – e.g.,

   How do I run this project locally?

4. Review the response – Copilot will provide step‑by‑step instructions.
5. Optional: Ask Copilot to execute – e.g.,

   Can you run it for me?

   Copilot will analyze the project, start the server, and show the result.
6. Iterate – Continue reviewing, requesting changes, or asking new questions—all within the same session.

This mode is ideal for developers who want a hands‑on, iterative workflow with Copilot.

What Is GitHub Copilot CLI Non‑Interactive Mode?

Non‑interactive mode is built for speed and simplicity.
Instead of opening a full Copilot session, you supply a single prompt directly on the command line and receive an immediate response—no follow‑up interaction required.

When to Use It

• Quick, one‑shot tasks – e.g., summarizing a repository, generating a small code snippet.
• Automation – integrate Copilot into scripts or CI pipelines without leaving the shell.
• Stay in your terminal – get the answer and continue working without context switches.

How to Run It

1. Make sure you’re at a regular shell prompt (exit any interactive Copilot session).

2. Execute the command, passing your prompt with -p:

   copilot -p "Quickly summarize what this repository does and the key folders."

3. Copilot scans the project files and returns a concise answer right in the terminal. ✨

Together with interactive mode, non‑interactive mode lets you choose the right workflow:

• Interactive – for exploratory, deeper work.
• Non‑interactive – for fast, focused results when you already know exactly what you need.

How to Resume a Previous Copilot Session

Sometimes you want to pick up right where you left off in a previous Copilot session while retaining all the context from that conversation.

• Interactive mode: Type /resume at the command line and Copilot will show a list of previous sessions.
• Non‑interactive mode: Run copilot --resume to launch the session picker directly.

A single command is all it takes to get back into the conversation you need—perfect when you already know which session you want to continue.

Tip: GitHub Copilot CLI’s interactive and non‑interactive modes are the fastest ways to prompt Copilot directly from your terminal. Switching between back‑and‑forth coding and quick prompting lets you work with Copilot the way you want.

Keep an eye out for more videos in the GitHub Copilot CLI for Beginners series, where we’ll explore:

• Copilot CLI slash commands
• Using MCP servers with Copilot CLI
• And more!

Happy coding!

Looking to try GitHub Copilot CLI?

• Read the Docs
• Get started

More resources to explore

• GitHub Copilot CLI for Beginners video series
• Getting started with GitHub Copilot CLI
• GitHub Copilot CLI 101: How to use Copilot from the command line
• **Best practices for GitHub Copilot CLI

Written by

Kayla Cinnamon – Senior AI Developer Tools Advocate

Related posts

Explore more from GitHub

• Docs – Everything you need to master GitHub, all in one place.
• GitHub – Build what’s next on GitHub, the place for anyone from anywhere to build anything.
• Customer stories – Meet the companies and engineering teams that build with GitHub.
• The GitHub Podcast – Catch up on the podcast covering topics, trends, stories, and culture in the open‑source developer community.