mirror of
https://github.com/github/awesome-copilot.git
synced 2026-06-25 17:00:20 +00:00
docs: update Learning Hub for Copilot CLI v1.0.61-v1.0.64 (#2119)
- understanding-mcp-servers: add .github/mcp.json to config discovery table (v1.0.61) - installing-and-using-plugins: add extensions as a plugin component type (v1.0.62) - copilot-configuration-basics: add /settings, /worktree, and /diagnose commands (v1.0.61, v1.0.64); note per-model token totals in /usage (v1.0.64) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
github-actions[bot]
committed by
GitHub
GitHub
parent
ab44e41dbb
commit
87c6d5f258
@@ -3,7 +3,7 @@ title: 'Copilot Configuration Basics'
|
||||
description: 'Learn how to configure GitHub Copilot at user, workspace, and repository levels to optimize your AI-assisted development experience.'
|
||||
authors:
|
||||
- GitHub Copilot Learning Hub Team
|
||||
lastUpdated: 2026-06-23
|
||||
lastUpdated: 2026-06-24
|
||||
estimatedReadingTime: '10 minutes'
|
||||
tags:
|
||||
- configuration
|
||||
@@ -414,6 +414,14 @@ The model picker opens in a **full-screen view** with inline reasoning effort ad
|
||||
|
||||
### CLI Session Commands
|
||||
|
||||
The `/settings` command (v1.0.61+) opens an interactive dialog to browse and edit all user settings in one place. Use it to discover available settings, toggle options, and update values without manually editing your config file:
|
||||
|
||||
```
|
||||
/settings
|
||||
```
|
||||
|
||||
The settings dialog supports search — type to filter settings by name. Changes take effect immediately.
|
||||
|
||||
GitHub Copilot CLI has two commands for managing session state, with distinct behaviours:
|
||||
|
||||
| Command | Behaviour |
|
||||
@@ -485,6 +493,14 @@ The `/cd` command changes the working directory for the current session. Each se
|
||||
|
||||
This is useful when you have multiple backgrounded sessions each focused on a different project directory.
|
||||
|
||||
The `/worktree` command (v1.0.61+, also aliased `/move`) creates a new git worktree and switches into it, moving any uncommitted changes along. This lets you start working on a parallel branch without leaving your current terminal session:
|
||||
|
||||
```
|
||||
/worktree my-feature-branch
|
||||
```
|
||||
|
||||
After the command runs, the session is inside the new worktree. Use this when you want to work on a second task in parallel without stashing changes or opening a new terminal. In v1.0.64+ you can also use the experimental `--worktree` flag at startup (`copilot -w [name]`) to create or reuse a worktree under `<repo>.worktrees/` before the session begins.
|
||||
|
||||
The `/share html` command exports the current session — including conversation history and any research reports — as a **self-contained interactive HTML file**:
|
||||
|
||||
```
|
||||
@@ -503,6 +519,14 @@ Chronicle tracks which files were created, modified, or deleted during the sessi
|
||||
|
||||
> **Note**: Session history, file tracking, and the `/chronicle` command were previously experimental features. As of v1.0.40, they are available to all users without enabling experimental mode.
|
||||
|
||||
The `/diagnose` command (v1.0.64+) analyzes the current session's logs and surfaces diagnostic information to help troubleshoot unexpected behavior, performance issues, or errors:
|
||||
|
||||
```
|
||||
/diagnose
|
||||
```
|
||||
|
||||
Use `/diagnose` when a session is behaving unexpectedly — it inspects session logs and reports what it finds, making it easier to share diagnostics with support or understand what happened internally.
|
||||
|
||||
**Keyboard shortcuts for queuing messages**: Use **Ctrl+Q** or **Ctrl+Enter** to queue a message (send it while the agent is still working). **Ctrl+D** no longer queues messages — it now has its default terminal behavior. If you have muscle memory for Ctrl+D queuing, switch to Ctrl+Q.
|
||||
|
||||
**Background running tasks**: Press **Ctrl+X → B** to move the current running task or shell command to the background. The task continues executing while you can type a new message or review earlier output. This is useful for long-running commands where you want to interact with the agent while waiting for the result.
|
||||
@@ -525,7 +549,7 @@ The `/context` command shows a visualization of the current conversation's conte
|
||||
/context
|
||||
```
|
||||
|
||||
The `/usage` command displays session metrics such as the number of tokens consumed, API calls made, and any quota information for the current session:
|
||||
The `/usage` command displays session metrics such as the number of tokens consumed, API calls made, and any quota information for the current session. In v1.0.64+, `/usage` also shows per-model token totals when you have used multiple models in a session:
|
||||
|
||||
```
|
||||
/usage
|
||||
|
||||
@@ -3,7 +3,7 @@ title: 'Installing and Using Plugins'
|
||||
description: 'Learn how to find, install, and manage plugins that extend GitHub Copilot CLI with reusable agents, skills, hooks, and integrations.'
|
||||
authors:
|
||||
- GitHub Copilot Learning Hub Team
|
||||
lastUpdated: 2026-04-27
|
||||
lastUpdated: 2026-06-24
|
||||
estimatedReadingTime: '8 minutes'
|
||||
tags:
|
||||
- plugins
|
||||
@@ -33,6 +33,7 @@ A plugin bundles one or more of the following components:
|
||||
| **Hooks** | Event handlers that intercept agent behavior | `hooks.json` or `hooks/` |
|
||||
| **MCP Servers** | Model Context Protocol integrations for external tools | `.mcp.json` or `.github/mcp.json` |
|
||||
| **LSP Servers** | Language Server Protocol integrations | `lsp.json` or `.github/lsp.json` |
|
||||
| **Extensions** | IDE extensions installable via the plugin marketplace (v1.0.62+) | `extensions/` |
|
||||
|
||||
A plugin might include all of these or just one — for example, a plugin could provide a single specialized agent, or an entire development toolkit with multiple agents, skills, hooks, and MCP server configurations working together.
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: 'Understanding MCP Servers'
|
||||
description: 'Learn how Model Context Protocol servers extend GitHub Copilot with access to external tools, databases, and APIs.'
|
||||
authors:
|
||||
- GitHub Copilot Learning Hub Team
|
||||
lastUpdated: 2026-06-23
|
||||
lastUpdated: 2026-06-24
|
||||
estimatedReadingTime: '8 minutes'
|
||||
tags:
|
||||
- mcp
|
||||
@@ -66,6 +66,7 @@ MCP servers are configured per-workspace. GitHub Copilot CLI discovers server de
|
||||
| File | Scope | Notes |
|
||||
|------|-------|-------|
|
||||
| `.mcp.json` | Repository root | Preferred for repo-shared configuration |
|
||||
| `.github/mcp.json` | Repository `.github/` folder | Auto-loaded workspace config (v1.0.61+) |
|
||||
| `.vscode/mcp.json` | VS Code workspace | VS Code–compatible workspace config |
|
||||
| `devcontainer.json` | Dev container | Available when running inside a container |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user