Skip to content

[bot] Update Learning Hub for CLI v1.0.11–v1.0.13 changes #1229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
aaronpowell merged 1 commit into from
Mar 30, 2026
+25 −5
Merged

[bot] Update Learning Hub for CLI v1.0.11–v1.0.13 changes #1229

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions website/src/content/docs/learning-hub/copilot-configuration-basics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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-03-28
lastUpdated: 2026-03-30
estimatedReadingTime: '10 minutes'
tags:
- configuration
Expand Down Expand Up @@ -412,10 +412,19 @@ GitHub Copilot CLI has two commands for managing session state, with distinct be
| Command | Behaviour |
|---------|-----------|
| `/new [prompt]` | Starts a fresh conversation while keeping the current session backgrounded. You can switch back to backgrounded sessions. |
| `/clear [prompt]` | Abandons the current session entirely and starts a new one. Backgrounded sessions are not affected. |
| `/clear [prompt]` | Abandons the current session entirely and starts a new one. Backgrounded sessions are not affected. MCP servers configured in your project are preserved in the new session. |

Both commands accept an optional prompt argument to seed the new session with an opening message, for example `/new Add error handling to the login flow`.

The `/session rename` command renames the current session. When called **without a name argument**, it automatically generates a session name based on the conversation history:

```
/session rename # auto-generate a name from conversation history
/session rename "My feature" # set a specific name
```

Auto-generated names help you find sessions quickly when switching between multiple backgrounded sessions.

The `/rewind` command opens a timeline picker that lets you roll back the conversation to any earlier point in history, reverting both the conversation and any file changes made after that point. You can also trigger it by pressing **double-Esc**:

```
Expand Down
4 changes: 2 additions & 2 deletions website/src/content/docs/learning-hub/installing-and-using-plugins.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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-03-22
lastUpdated: 2026-03-30
estimatedReadingTime: '8 minutes'
tags:
- plugins
Expand Down Expand Up @@ -258,7 +258,7 @@ A: Yes. You can create a private plugin marketplace in an internal GitHub reposi

**Q: What happens if I uninstall a plugin?**

A: The plugin's agents, skills, and hooks are removed from Copilot. Any work already done with those tools is unaffected — only future sessions lose access.
A: The plugin's agents, skills, and hooks are removed from Copilot, and any cached plugin data stored on disk is also cleaned up. Any work already done with those tools is unaffected — only future sessions lose access.

## Next Steps

Expand Down
13 changes: 12 additions & 1 deletion website/src/content/docs/learning-hub/understanding-mcp-servers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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-03-27
lastUpdated: 2026-03-30
estimatedReadingTime: '8 minutes'
tags:
- mcp
Expand Down Expand Up @@ -139,6 +139,17 @@ Example `.mcp.json` or `.vscode/mcp.json`:

> **Security tip**: Use `${input:variableName}` for sensitive values. VS Code will prompt for these at runtime rather than storing them in the file.

### Authentication

Some MCP servers require authentication to connect to protected resources. GitHub Copilot CLI supports several authentication approaches:

- **OAuth**: MCP servers can use the OAuth flow to authenticate with external services. The CLI handles the browser redirect and token storage automatically. This also works when running in ACP (Agent Coordination Protocol) mode.
Copy link

Copilot AI Mar 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The OAuth bullet introduces “ACP (Agent Coordination Protocol) mode”, but ACP isn’t referenced or defined anywhere else in the Learning Hub docs. This makes the guidance hard to understand for readers; consider either linking to a page that defines ACP or removing the ACP mention here.

Suggested change
- **OAuth**: MCP servers can use the OAuth flow to authenticate with external services. The CLI handles the browser redirect and token storage automatically. This also works when running in ACP (Agent Coordination Protocol) mode.
- **OAuth**: MCP servers can use the OAuth flow to authenticate with external services. The CLI handles the browser redirect and token storage automatically.

Copilot uses AI. Check for mistakes.
- **Microsoft Entra ID (Azure AD)**: MCP servers that authenticate via Microsoft Entra ID are fully supported. Once you complete the initial login, the CLI caches the authentication and **will not show the consent screen on subsequent connections** — you authenticate once per session rather than every time the server reconnects.
Copy link

Copilot AI Mar 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Entra ID bullet goes beyond the PR description/release-note summary by claiming “you authenticate once per session rather than every time the server reconnects.” Unless the cache scope is explicitly documented, consider rephrasing to the observable behavior (e.g., no repeated consent prompts on subsequent connections) without asserting the exact cache lifetime.

Suggested change
- **Microsoft Entra ID (Azure AD)**: MCP servers that authenticate via Microsoft Entra ID are fully supported. Once you complete the initial login, the CLI caches the authentication and **will not show the consent screen on subsequent connections** — you authenticate once per session rather than every time the server reconnects.
- **Microsoft Entra ID (Azure AD)**: MCP servers that authenticate via Microsoft Entra ID are fully supported. Once you complete the initial login, the CLI caches the authentication and **will not show the consent screen on subsequent connections**.

Copilot uses AI. Check for mistakes.
- **API keys via environment variables**: Pass secrets through the `env` field in the MCP server configuration (see examples above). Never hardcode credentials in `.mcp.json`.
- **`${input:variableName}` prompts**: VS Code will prompt for these values at runtime, keeping secrets out of committed files.
Copy link

Copilot AI Mar 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section says “GitHub Copilot CLI supports” ${input:...} prompts, but then explains behavior specific to VS Code (“VS Code will prompt…”). Please clarify whether ${input:...} prompting is supported by Copilot CLI itself, VS Code only, or both, and adjust the wording to avoid implying CLI behavior that may not apply.

Suggested change
- **`${input:variableName}` prompts**: VS Code will prompt for these values at runtime, keeping secrets out of committed files.
- **`${input:variableName}` prompts in VS Code**: When you use `${input:...}` in your MCP configuration inside VS Code, the editor will prompt for these values at runtime, keeping secrets out of committed files. When Copilot CLI is launched from VS Code, those values are resolved before the CLI runs.

Copilot uses AI. Check for mistakes.

> **Tip**: If your MCP server uses OAuth with Dynamic Client Registration but hosts its authorization metadata at a non-standard URL (as some enterprise servers like Atlassian Rovo do), Copilot CLI handles this automatically.

## How Agents Use MCP Tools

When an agent declares an MCP server in its `tools` array, Copilot can invoke that server's capabilities during conversation:
Expand Down
Loading