[bot] Document Copilot CLI v1.0.15 features in Learning Hub#1258
Merged
aaronpowell merged 1 commit intostagedfrom Apr 1, 2026
Merged
Conversation
- Add postToolUseFailure hook event to automating-with-hooks.md: clarify that postToolUse now only fires on success, add new event to the events table, and add a practical example with migration note - Add /mcp auth command and device code flow (RFC 8628) to understanding-mcp-servers.md authentication section - Add mcp.config.list/add/update/remove server RPCs section to understanding-mcp-servers.md - Add /share html command to copilot-configuration-basics.md CLI Session Commands section - Update lastUpdated dates to 2026-04-01 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aaronpowell
approved these changes
Apr 1, 2026
aaronpowell
deleted the
learning-hub/copilot-cli-v1.0.15-updates-b034b93b6c15850d
branch
Contributor
There was a problem hiding this comment.
Pull request overview
Documents recent GitHub Copilot CLI (v1.0.13–v1.0.15) changes in the Learning Hub, focusing on new CLI commands, MCP authentication/config management, and updated hook lifecycle semantics.
Changes:
- Updates hook event documentation to reflect
postToolUseas success-only and addspostToolUseFailure, including a migration note/example. - Expands MCP server documentation with device-code OAuth fallback,
/mcp auth, and a new section describing persistent MCP config RPCs. - Adds
/share htmldocumentation to session commands.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
website/src/content/docs/learning-hub/understanding-mcp-servers.md |
Adds MCP auth updates and documents new persistent MCP config RPCs. |
website/src/content/docs/learning-hub/copilot-configuration-basics.md |
Documents /share html session export behavior. |
website/src/content/docs/learning-hub/automating-with-hooks.md |
Updates hook lifecycle events and adds a tool-failure handling example. |
| /share html | ||
| ``` | ||
|
|
||
| The exported file contains everything needed to view the session without a network connection and can be shared with teammates or stored for later reference. This complements `/share` (which shares via URL) for cases where an offline or attached format is preferred. |
There was a problem hiding this comment.
/share is referenced as “shares via URL”, but this doc doesn’t define /share anywhere, and it conflicts with the Learning Hub “CLI for beginners” guide (which describes /share as exporting to markdown/GitHub gist). Please either document /share in this section and align the description, or reword this sentence to avoid making a potentially incorrect claim about /share’s behavior.
Suggested change
| The exported file contains everything needed to view the session without a network connection and can be shared with teammates or stored for later reference. This complements `/share` (which shares via URL) for cases where an offline or attached format is preferred. | |
| The exported file contains everything needed to view the session without a network connection and can be shared with teammates or stored for later reference. This is useful when you want an offline or easily attachable format. |
Comment on lines
+104
to
+105
| In addition to file-based configuration, GitHub Copilot CLI exposes **server RPCs** that let MCP servers and tooling scripts manage the persistent MCP server registry at runtime. This enables programmatic setup — for example, an installer script that registers a server without requiring you to hand-edit a JSON file. | ||
|
|
There was a problem hiding this comment.
This section introduces a “persistent MCP server registry” managed via RPCs, but earlier the page states MCP servers are configured per-workspace and lists a file-based load order. Please clarify where this persistent configuration is stored and how it interacts with/overrides file-based configuration (including precedence), so readers can predict which server definition will be used.
Suggested change
| In addition to file-based configuration, GitHub Copilot CLI exposes **server RPCs** that let MCP servers and tooling scripts manage the persistent MCP server registry at runtime. This enables programmatic setup — for example, an installer script that registers a server without requiring you to hand-edit a JSON file. | |
| In addition to per-workspace, file-based configuration, GitHub Copilot CLI exposes **server RPCs** that let MCP servers and tooling scripts manage a **persistent MCP server registry** at runtime. This registry is stored in the Copilot CLI user configuration (not in your workspace) and is shared across all workspaces for that user on the machine. It enables programmatic setup — for example, an installer script that registers a server without requiring you to hand-edit a JSON file. | |
| At startup, Copilot first loads MCP servers from the workspace configuration files in the order described above, then merges in any servers from the persistent registry that do not already exist in the workspace configuration. If a server with the same name is defined both in a workspace config file and in the persistent registry, **the workspace (file-based) definition takes precedence**, and the persistent entry is ignored for that server. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's New
Based on Copilot CLI releases from the past 7 days (v1.0.13–v1.0.15, March 27–April 1, 2026), the following new features were found and documented:
New features found
postToolUseFailurehook event (v1.0.15) — New lifecycle event that fires when a tool call fails.postToolUsenow only fires on successful tool calls. This is a behavioral change that could affect existing hooks./share htmlcommand (v1.0.15) — Export sessions and research reports as self-contained interactive HTML files./mcp authcommand (v1.0.15) — Re-authentication UI for MCP OAuth servers with account switching support, usable without restarting a session.mcp.config.list,mcp.config.add,mcp.config.update, andmcp.config.removeserver RPCs for programmatic management of persistent MCP server configuration.Sections updated
automating-with-hooks.mdpostToolUsenow marked as success-only; addedpostToolUseFailurerow. Added practical example with migration note.understanding-mcp-servers.md/mcp authand device code flow entries. Added new "Managing Persistent MCP Configuration via Server RPCs" section with RPC reference table.copilot-configuration-basics.md/share htmlcommand to the CLI Session Commands section.Source announcements