The post GitHub Copilot CLI Slash Commands Get Full Reference Guide appeared on BitcoinEthereumNews.com. Jessie A Ellis Jan 21, 2026 17:36 GitHub releases comprehensiveThe post GitHub Copilot CLI Slash Commands Get Full Reference Guide appeared on BitcoinEthereumNews.com. Jessie A Ellis Jan 21, 2026 17:36 GitHub releases comprehensive

GitHub Copilot CLI Slash Commands Get Full Reference Guide



Jessie A Ellis
Jan 21, 2026 17:36

GitHub releases comprehensive cheat sheet for Copilot CLI slash commands, covering session management, directory access, model selection, and MCP configuration.

GitHub published a detailed reference guide for slash commands in Copilot CLI on January 21, giving developers a complete rundown of the terminal-based AI assistant’s command structure for the first time.

The guide arrives one week after GitHub made OpenCode official and expanded Copilot’s model garden access for terminal-native developers. For the growing number of coders who prefer working in the command line over IDEs, this documentation fills a gap that’s existed since Copilot CLI entered public preview last September.

What Slash Commands Actually Do

Unlike natural language prompts that can produce variable results, slash commands trigger predictable, repeatable actions. Type /clear and you wipe your session context—every time, same result. That consistency matters when you’re debugging at 2 AM and need Copilot to stop referencing code from three tasks ago.

The command set breaks into four categories:

Session management handles the basics: /clear resets context, /session and /usage show metrics like total duration and code changes, and /exit ends your session cleanly.

Directory and file access controls what Copilot can see. /add-dir grants access to specific directories while /list-dirs shows current permissions—useful for teams with compliance requirements who need auditable trails of file access.

Configuration commands let you swap AI models on the fly with /model, which presents options including Claude Sonnet 4.5, GPT-5.1, and Gemini 3 Pro. /theme adjusts terminal display, and /terminal-setup enables multiline inputs for complex prompts.

External services is where things get interesting. /delegate creates AI-generated pull requests without leaving your terminal. /mcp manages Model Context Protocol server configurations for CI/CD integration. /share exports entire sessions as markdown files or GitHub Gists for async handoffs.

The Three Commands Worth Memorizing

GitHub’s own advice: start with /clear, /cwd, and /model. The first prevents context bleed between projects. The second confirms or changes your working directory—critical when navigating large codebases. The third lets you experiment with different AI models when responses aren’t hitting the mark.

The /user command addresses a real pain point for developers juggling personal and enterprise accounts. /user switch rotates between GitHub accounts without the usual dance of logging out and back in.

Who This Matters For

Copilot CLI requires an active paid subscription, so this isn’t a free tier feature. But for subscribers who’ve been piecing together workflows from scattered documentation, having a single reference changes the calculus on terminal-based AI coding.

The timing aligns with GitHub’s January 14 announcement of enhanced agents and improved context management for Copilot CLI—suggesting the company sees terminal-native development as a serious growth vector rather than a niche use case.

Full documentation is available on GitHub’s blog, with the complete command reference table covering 17 slash commands and their use cases.

Image source: Shutterstock

Source: https://blockchain.news/news/github-copilot-cli-slash-commands-cheat-sheet

Market Opportunity
Everclear Logo
Everclear Price(CLEAR)
$0.0043
$0.0043$0.0043
0.00%
USD
Everclear (CLEAR) Live Price Chart
Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact [email protected] for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.

You May Also Like

The Channel Factories We’ve Been Waiting For

The Channel Factories We’ve Been Waiting For

The post The Channel Factories We’ve Been Waiting For appeared on BitcoinEthereumNews.com. Visions of future technology are often prescient about the broad strokes while flubbing the details. The tablets in “2001: A Space Odyssey” do indeed look like iPads, but you never see the astronauts paying for subscriptions or wasting hours on Candy Crush.  Channel factories are one vision that arose early in the history of the Lightning Network to address some challenges that Lightning has faced from the beginning. Despite having grown to become Bitcoin’s most successful layer-2 scaling solution, with instant and low-fee payments, Lightning’s scale is limited by its reliance on payment channels. Although Lightning shifts most transactions off-chain, each payment channel still requires an on-chain transaction to open and (usually) another to close. As adoption grows, pressure on the blockchain grows with it. The need for a more scalable approach to managing channels is clear. Channel factories were supposed to meet this need, but where are they? In 2025, subnetworks are emerging that revive the impetus of channel factories with some new details that vastly increase their potential. They are natively interoperable with Lightning and achieve greater scale by allowing a group of participants to open a shared multisig UTXO and create multiple bilateral channels, which reduces the number of on-chain transactions and improves capital efficiency. Achieving greater scale by reducing complexity, Ark and Spark perform the same function as traditional channel factories with new designs and additional capabilities based on shared UTXOs.  Channel Factories 101 Channel factories have been around since the inception of Lightning. A factory is a multiparty contract where multiple users (not just two, as in a Dryja-Poon channel) cooperatively lock funds in a single multisig UTXO. They can open, close and update channels off-chain without updating the blockchain for each operation. Only when participants leave or the factory dissolves is an on-chain transaction…
Share
BitcoinEthereumNews2025/09/18 00:09
Superstate Raises Over $82 Million to Develop Onchain Capital Markets

Superstate Raises Over $82 Million to Develop Onchain Capital Markets

Superstate announced that it has raised $82.5 million in a Series B funding round. The capital will be used to develop infrastructure for issuing and trading shares
Share
Incrypted2026/01/23 00:13
Valicor Brings Financial Education to Second High School in Underserved Community

Valicor Brings Financial Education to Second High School in Underserved Community

Partnership with Ramsey Education expands from Cincinnati to Michigan, equipping students with essential money management skills. MONROE, Ohio., Jan. 22, 2026 /
Share
AI Journal2026/01/22 23:50