If you’ve used slash commands in the GitHub Copilot CLI, you already know how powerful a quick can be.
In the GitHub Copilot app, slash commands take that idea further, giving you shortcuts for managing sessions, navigating projects, and customizing your Copilot workflow.
What are slash commands?
Slash commands are text shortcuts you type directly into the GitHub Copilot app’s chat composer.
Start by typing and an autocomplete menu appears, showing the commands available in your current context.
It’s a small character with a lot of potential, opening the door to shortcuts that help you work with Copilot in new ways.
If you’re coming from the CLI, here’s the key difference: CLI slash commands are designed around a terminal-first workflow.
Things like adding directories, setting your working directory, and managing terminal access happen through commands.
This makes sense, because the CLI lives inside your terminal where there’s no visual interface.
Tip: If you’ve used slash commands in the Copilot CLI, you’ll notice some familiar faces.
Commands like and work in both places.
But the GitHub Copilot app-specific commands are tailored for the multi-session workflow that the desktop app provides.
The app, on the other hand, provides a visual interface for managing context.
File access commands like or aren’t needed since the app manages project context automatically.
App slash commands are more about workflows.
You can navigate between sessions, manage projects, and control how the agent works.
Why use slash commands?
Slash commands may look like simple shortcuts, but they can change how you interact with Copilot.
They help you move faster, stay focused, and quickly access the workflows you need.
Instead of digging through options or breaking your focus to find the right tool, you can type a command and keep moving.
A single opens up the list of slash commands that can help you move faster, explore new ideas, and get the most out of the app.
Let’s take a look at some of the slash commands available in the GitHub Copilot app and how they can fit into your everyday workflows.
Before you write code, make a Good code starts with a good plan. helps you break down a task before you start writing code, think through your approach, identify potential challenges, and decide what needs to happen next.
It also switches your session into Plan mode, which you can also select from the Mode dropdown in the chat composer.
Plan a new feature.
Break down new feature ideas before jumping into implementation.
Have Copilot identify files, components, and dependencies so you have a clearer path forward.
Prepare for a large refactor.
Map out complex changes before touching your code.
Uncover potential risks and develop an incremental approach for making large changes safely.
Triage and fix bugs.
If you know something is wrong but aren’t sure where to start, can help you explore possible causes and outline the steps needed to diagnose and resolve the problem.
Let Copilot play devil’s advocate with Sometimes the best way to validate an idea is to challenge it. is like that one teammate who raises their hand and asks, “Have we thought about what happens when this goes wrong?” It helps you pressure-test your approach by having Copilot question your assumptions and point out potential risks or tradeoffs before you commit to a solution.
Here are a few ways you can use it: Validate an architecture choice.
Pitch your plan to use Redis for caching and have Copilot question your invalidation strategy, scalability, or whether another approach better fits your workload.
Compare implementation options.
Ask Copilot to debate the pros and cons of REST versus GraphQL, or synchronous versus asynchronous processing, based on your application’s requirements.
Review a migration plan.
Walk through a database migration or infrastructure change and have Copilot identify edge cases, risks,