[bot] Update Learning Hub with recent Copilot CLI features (v1.0.23–v1.0.30)#1421
Merged
aaronpowell merged 1 commit intostagedfrom Apr 20, 2026
Conversation
…1.0.30) - copilot-configuration-basics.md: Add /ask, /env, /statusline commands and --mode/--autopilot/--plan startup flags - automating-with-hooks.md: Document preToolUse modifiedArgs/updatedInput and additionalContext fields for modifying tool arguments - understanding-mcp-servers.md: Add /mcp install registry section and note that type field is optional for remote MCP servers - installing-and-using-plugins.md: Add copilot plugin marketplace update command and deprecation notice for repo/URL/path installs - using-copilot-coding-agent.md: Add Remote Control section (replaces steering feature) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
aaronpowell
approved these changes
Apr 20, 2026
aaronpowell
deleted the
learning-hub-copilot-updates-april-2026-3779ff6eb41acc67
branch
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Learning Hub documentation to reflect GitHub Copilot CLI feature changes introduced in v1.0.23–v1.0.30 (April 9–16, 2026), keeping CLI command/reference pages current.
Changes:
- Documented new/updated CLI session commands and startup flags in configuration basics.
- Expanded hooks documentation to cover
preToolUseargument modification and additional context injection. - Added MCP registry install flow, plugin marketplace updates/deprecations, and a new coding agent “Remote Control” section.
Show a summary per file
| File | Description |
|---|---|
| website/src/content/docs/learning-hub/using-copilot-coding-agent.md | Adds “Remote Control” documentation and updates lastUpdated. |
| website/src/content/docs/learning-hub/understanding-mcp-servers.md | Adds /mcp install registry install guidance and notes on remote server type; updates lastUpdated. |
| website/src/content/docs/learning-hub/installing-and-using-plugins.md | Adds plugin install deprecation notice and plugin marketplace update; updates lastUpdated. |
| website/src/content/docs/learning-hub/copilot-configuration-basics.md | Adds /ask, /env, /statusline, plus CLI startup flags; updates lastUpdated. |
| website/src/content/docs/learning-hub/automating-with-hooks.md | Adds preToolUse argument modification example/description; updates lastUpdated. |
Copilot's findings
- Files reviewed: 5/5 changed files
- Comments generated: 4
| # Strip the --no-sandbox flag if present | ||
| SAFE_COMMAND=$(echo "$COMMAND" | sed 's/--no-sandbox//g') | ||
|
|
||
| echo "{\"modifiedArgs\": {\"command\": \"$SAFE_COMMAND\"}, \"additionalContext\": \"Command was sanitized by security policy.\"}" |
There was a problem hiding this comment.
The example builds JSON via shell string interpolation (echo "{...$SAFE_COMMAND...}"), which will produce invalid JSON if the command contains quotes, backslashes, or newlines. Use a JSON-safe construction method (e.g., jq -nc with --arg) so modifiedArgs.command is properly escaped.
Suggested change
| echo "{\"modifiedArgs\": {\"command\": \"$SAFE_COMMAND\"}, \"additionalContext\": \"Command was sanitized by security policy.\"}" | |
| jq -nc \ | |
| --arg command "$SAFE_COMMAND" \ | |
| --arg additionalContext "Command was sanitized by security policy." \ | |
| '{modifiedArgs: {command: $command}, additionalContext: $additionalContext}' |
Comment on lines
+102
to
+103
| A picker will list available servers from the registry. After selecting one, the CLI prompts for any required configuration values (connection strings, API keys, etc.) and writes the completed entry to your persistent MCP config automatically. | ||
|
|
There was a problem hiding this comment.
This section says MCP servers are configured per-workspace via .mcp.json/.vscode/mcp.json, but here /mcp install is described as writing to a “persistent MCP config”. Please clarify where the install flow writes (workspace file vs user-level persistent registry), and how that interacts with the per-workspace config order described above.
Suggested change
| A picker will list available servers from the registry. After selecting one, the CLI prompts for any required configuration values (connection strings, API keys, etc.) and writes the completed entry to your persistent MCP config automatically. | |
| A picker will list available servers from the registry. After selecting one, the CLI prompts for any required configuration values (connection strings, API keys, etc.) and writes the completed entry into the current workspace's MCP configuration file automatically. | |
| In other words, `/mcp install` updates the same per-workspace configuration described above (for example, `.vscode/mcp.json` or `.mcp.json`), rather than storing the server in a separate user-level registry. Once written, the server is discovered using the same workspace config lookup and precedence order described earlier in this article. |
| /plugin install database-data-management@awesome-copilot | ||
| ``` | ||
|
|
||
| > **Deprecation notice**: Installing plugins directly from a GitHub repository URL, raw URL, or local file path (e.g., `copilot plugin install github/awesome-copilot`) is deprecated and will be removed in a future release. Use marketplace-based installation instead. |
There was a problem hiding this comment.
The deprecation notice mentions repository URL/raw URL/local path installs, but the example (copilot plugin install github/awesome-copilot) is neither a URL nor a local path. Consider updating the example to match the deprecated forms and/or explicitly distinguish between adding a marketplace from a repo/path (still documented above) vs installing a plugin directly from a repo/path (deprecated).
Suggested change
| > **Deprecation notice**: Installing plugins directly from a GitHub repository URL, raw URL, or local file path (e.g., `copilot plugin install github/awesome-copilot`) is deprecated and will be removed in a future release. Use marketplace-based installation instead. | |
| > **Deprecation notice**: Installing plugins directly from a GitHub repository URL, raw URL, or local file path is deprecated and will be removed in a future release. For example, commands such as `copilot plugin install https://github.com/github/awesome-copilot`, `copilot plugin install https://raw.githubusercontent.com/github/awesome-copilot/main/.github/plugin/plugin.json`, or `copilot plugin install ./plugins/awesome-copilot` are deprecated. Use marketplace-based installation instead, such as `copilot plugin install database-data-management@awesome-copilot`. |
Comment on lines
+503
to
+505
| copilot --mode agent # start in agent mode (autonomous tool use) | ||
| copilot --autopilot # alias for --mode autopilot (allow-all) | ||
| copilot --plan # start in plan mode (propose without executing) |
There was a problem hiding this comment.
This section uses copilot --mode ... but the preceding flag example uses gh copilot --effort .... If both entrypoints are valid, consider adding a brief note that copilot is an alias/wrapper for gh copilot; otherwise, please standardize the command prefix so readers don’t copy a non-working command.
Suggested change
| copilot --mode agent # start in agent mode (autonomous tool use) | |
| copilot --autopilot # alias for --mode autopilot (allow-all) | |
| copilot --plan # start in plan mode (propose without executing) | |
| gh copilot --mode agent # start in agent mode (autonomous tool use) | |
| gh copilot --autopilot # alias for --mode autopilot (allow-all) | |
| gh copilot --plan # start in plan mode (propose without executing) |
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
Reviewed the GitHub Copilot CLI changelog for releases v1.0.23–v1.0.30 (April 9–16, 2026) and updated five Learning Hub pages with features not yet documented.
New features / changes found
/askcommand — quick question without affecting history/envcommand — show loaded environment details/statuslinecommand — customize status bar items--mode/--autopilot/--planstartup flagspreToolUsehooks:modifiedArgs/updatedInput+additionalContext/mcp install)typefield optional (defaults tohttp)copilot plugin marketplace updatecommandSections updated
copilot-configuration-basics.md/ask,/env, and/statuslinecommand descriptions to the CLI Session Commands section--mode,--autopilot, and--planautomating-with-hooks.mdmodifiedArgs/updatedInputandadditionalContextoutput fields (v1.0.24)understanding-mcp-servers.md/mcp installguided flowtypefield is optional for remote MCP servers (defaults tohttp)installing-and-using-plugins.mdcopilot plugin marketplace updatecommand to the managing plugins sectionusing-copilot-coding-agent.md--remote//remotefeature, resume picker integration, and per-scenario benefits; noted that it replaces the earlier "steering" featureSources