Looking to try GitHub Copilot CLI? Read the docs and get started today.
Mastering slash commands allows engineers to maintain high terminal productivity by managing AI context, switching models for specific tasks, and ensuring security permissions are kept tidy without context-switching between different tools.
Welcome back 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. So far in this series, we’ve covered how to get started and when to use interactive and non-interactive modes. In this edition, we’ll learn what slash commands are, why they matter, and how to use slash commands to control GitHub Copilot efficiently. You can complete tasks like switching models, checking token usage, and resuming past sessions right from your terminal.
Let’s dive in!
When working in Copilot CLI, one of the most powerful concepts to learn early on is slash commands. Slash commands are built-in controls that you can access directly from the command line. Acting as your control surface within Copilot CLI, slash commands allow you to:
Slash commands can be thought of as your command center for interacting with Copilot CLI. To look at all of the options available, just type / in the command line for a scrollable list of all currently supported slash commands.
Let’s take a look at some of the most popular ones.
Different models are optimized for different kinds of work. If you want to switch models, type /model into the command line. This will display a list of available models, along with key details like:
Choosing the right model can significantly impact both speed and results.
Copilot CLI operates within a context window, which determines how much information it can “remember” during a session. If you want to check your current usage, type /context to learn how many tokens you have left, along with system usage and available buffer.
If you find that you’re running low on space, you can free up space by typing /compact in the command line. This summarizes your current conversation so you can continue without having to start a new session. Copilot CLI will do this automatically when you approach the limit, but you can also do this manually if you want to transition to a new task or clean up context mid-session.
If you’d rather start fresh and completely reset your environment, you can use /clear to clear the session entirely.
If you want to resume a previous session, you can type /resume. This will bring up a list of previous sessions you’ve had, including both local and remote sessions. Entering a previous session will show you your session history, and you can pick up right where you left off.
As you work with Copilot to make changes to your project, it’s important to keep track of what’s changed. If you want to see what the changes are, run /diff to see recent updates. This gives you a clear view of what modifications were made during your session, so you can validate changes before moving forward.
If you want to work across repositories or directories, you don’t have to exit Copilot. You can type /cwd to change your working directory to another repository. This allows you to scope Copilot’s work to a specific part of your project and helps you stay efficient while multitasking across codebases.
In the past, you might have granted Copilot CLI permission to perform actions like editing files. Say you’re switching to a repository you want to be more careful in and want to reset those permissions: you can do so by running /reset-allowed-tools.
Using these slash commands gives you even better control over Copilot CLI—and the more familiar you become with them, the more deliberate your workflow becomes.
Whether you’re switching models, managing context, or navigating across projects, using slash commands in CLI gives you the tools you need to stay in control. And if you haven’t already: open up your terminal, type /, and explore! There are many more slash commands to discover.
Happy coding!
Looking to try GitHub Copilot CLI? Read the docs and get started today.
More resources to explore:
The post GitHub Copilot CLI for Beginners: Overview of common slash commands appeared first on The GitHub Blog.
Continue reading on the original blog to support the author
Read full articleUnderstanding the trade-off between pre-built AI harnesses and raw API access helps engineers optimize for development speed versus custom control. It clarifies how to manage LLM costs and token efficiency while leveraging existing SDLC integrations.
This article demonstrates that better tools don't guarantee better AI performance. Aligning agent instructions with specific human workflows is crucial for optimizing token costs and accuracy in automated engineering tasks.
The efficiency of an AI agent depends heavily on its orchestration harness. GitHub's harness reduces token costs and latency while maintaining high accuracy, enabling more cost-effective and responsive AI-driven development workflows for engineers.
Optimizing LLM efficiency through prompt caching and intelligent routing reduces latency and costs while maintaining high-quality outputs. For engineers, this means faster agentic workflows and better resource utilization without manual model configuration.