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

[github-actions]

What's new

Reviewing the GitHub Copilot CLI releases from the past 7 days (v1.0.11 through v1.0.13, covering 2026-03-23 to 2026-03-30), the following features were not yet documented in the Learning Hub:

1. /session rename auto-naming (v1.0.12) — when called without a name argument, the command now auto-generates a session name from conversation history
2. /clear preserves MCP servers (v1.0.12) — MCP servers remain active after /clear starts a new session
3. Microsoft Entra ID authentication (v1.0.13) — MCP servers using Entra ID no longer show the consent screen on every login; and OAuth with non-standard Dynamic Client Registration URLs is handled automatically
4. Plugin uninstall cleanup (v1.0.13) — uninstalling a plugin now removes its cached data from disk

The rest of the recent changes (monorepo discovery, /rewind timeline picker, /allow-all on/off/show, personal skills directory, extension hooks merging, sessionStart additionalContext, model picker full-screen, .claude/settings.json, plugin hook env vars, MCP sampling, MCP allowlist) were already documented in the Learning Hub.

Pages updated

copilot-configuration-basics.md

• Added /session rename auto-name generation section under CLI Session Commands
• Updated the /clear row in the session commands table to note MCP servers are preserved

understanding-mcp-servers.md

• Added new Authentication section covering OAuth, Microsoft Entra ID (no repeat consent screens), API keys via env vars, \$\{input:} prompts, and Dynamic Client Registration at non-standard URLs

installing-and-using-plugins.md

• Updated the "What happens if I uninstall a plugin?" FAQ to note that cached plugin data is also removed

Sources

• https://github.com/github/copilot-cli/releases/tag/v1.0.13
• https://github.com/github/copilot-cli/releases/tag/v1.0.12
• https://github.com/github/copilot-cli/releases/tag/v1.0.11

Generated by Learning Hub Updater · ◷

[Copilot]

Pull request overview

Updates Learning Hub documentation to reflect GitHub Copilot CLI v1.0.11–v1.0.13 changes, focusing on new/updated session behavior, MCP server authentication, and plugin uninstall cleanup.

Changes:

• Documented new MCP server authentication details (OAuth, Entra ID behavior, API key patterns, Dynamic Client Registration edge case).
• Updated CLI session docs to note /clear preserves MCP servers and added /session rename auto-naming behavior.
• Updated plugin uninstall FAQ to state cached plugin data is cleaned up on uninstall.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
website/src/content/docs/learning-hub/understanding-mcp-servers.md	Adds an Authentication section for MCP servers and updates lastUpdated.
website/src/content/docs/learning-hub/installing-and-using-plugins.md	Updates uninstall FAQ to mention cached data cleanup; updates lastUpdated.
website/src/content/docs/learning-hub/copilot-configuration-basics.md	Updates /clear description and adds /session rename auto-naming docs; updates lastUpdated.

[Copilot]

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]

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]

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**.