From 6b13f26afb9fbbc4aecc0f38048b66d014cb9911 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 3 Sep 2026 02:44:54 +0000 Subject: [PATCH] Update Learning Hub: Customize, Agent Merge, VS Code Agents window updates (#2917) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- .../docs/learning-hub/agents-and-subagents.md | 8 +++++++- .../docs/learning-hub/github-copilot-app.md | 12 +++++++++++- .../github-copilot-terminology-glossary.md | 16 +++++++++++++++- 3 files changed, 33 insertions(+), 3 deletions(-) diff --git a/website/src/content/docs/learning-hub/agents-and-subagents.md b/website/src/content/docs/learning-hub/agents-and-subagents.md index 6d85ee8c..f257986b 100644 --- a/website/src/content/docs/learning-hub/agents-and-subagents.md +++ b/website/src/content/docs/learning-hub/agents-and-subagents.md @@ -3,7 +3,7 @@ title: 'Agents and Subagents' description: 'Learn how delegated subagents differ from primary agents, when to use them, and how to launch them in VS Code and Copilot CLI.' authors: - GitHub Copilot Learning Hub Team -lastUpdated: 2026-07-01 +lastUpdated: 2026-09-02 estimatedReadingTime: '9 minutes' tags: - agents @@ -194,6 +194,12 @@ That means you should think about delegation features in product-specific terms: If you share agent files across surfaces, document those differences so users know which behaviors are portable and which are editor-specific. +## Tracking delegated work in VS Code (v1.136+) + +When an agent delegates work to multiple chats, VS Code's **Agents window** now shows those chats as children of their parent session in the sessions list, so you can see which chats belong together instead of managing a flat list of unrelated sessions. Each chat row shows its own title, status, and pending approvals. A delegated request also includes a source link (for example **Sent by another session**) so you can jump straight back to whichever session or chat initiated it. + +This pairs with **improved workspace resolution**: agents can resolve a workspace by project name (for example, "run this in the vscode workspace") in addition to absolute paths, which simplifies prompts that hand off work across multiple repositories. + ## Common questions **Do users always invoke subagents directly?** diff --git a/website/src/content/docs/learning-hub/github-copilot-app.md b/website/src/content/docs/learning-hub/github-copilot-app.md index c99fae47..f17a689b 100644 --- a/website/src/content/docs/learning-hub/github-copilot-app.md +++ b/website/src/content/docs/learning-hub/github-copilot-app.md @@ -3,7 +3,7 @@ title: 'Getting Started with the GitHub Copilot app' description: 'Learn about the GitHub Copilot app, a desktop experience built for agent-native development. Understand its key features and who it''s for.' authors: - GitHub Copilot Learning Hub Team -lastUpdated: 2026-08-28 +lastUpdated: 2026-09-02 estimatedReadingTime: '8 minutes' tags: - copilot-app @@ -82,6 +82,16 @@ Closing the app's main window keeps it running in the background instead of quit For a hands-on guide to building canvases with `/create-canvas`, see [Working with Canvas Extensions](../working-with-canvas-extensions/). +### Customize + +**Customize** *(v1.1.13+)* is a single place in the Copilot app to browse and manage everything that extends your agents: plugins, skills, MCP servers, and canvases. Instead of hunting through separate settings pages, open **Customize** to: + +- Browse **Featured** integrations (for example Azure DevOps or Figma) and install them with one click +- See what's already **Installed**, with consistent icons and source labels across plugin, skill, MCP server, canvas, and connector types +- Create, edit, or remove your own **personal skills** directly in the app, without hand-authoring a `SKILL.md` file + +This makes Customize a good starting point if you want to extend the app's capabilities but don't need the full `copilot plugin` CLI workflow described in [Installing and Using Plugins](../installing-and-using-plugins/). + ### Agent Merge **Agent Merge** is a feature that can carry your pull requests through the entire workflow: diff --git a/website/src/content/docs/learning-hub/github-copilot-terminology-glossary.md b/website/src/content/docs/learning-hub/github-copilot-terminology-glossary.md index 93920053..a143ebfb 100644 --- a/website/src/content/docs/learning-hub/github-copilot-terminology-glossary.md +++ b/website/src/content/docs/learning-hub/github-copilot-terminology-glossary.md @@ -3,7 +3,7 @@ title: 'GitHub Copilot Terminology Glossary' description: 'A quick reference guide defining common GitHub Copilot and platform-specific terms.' authors: - GitHub Copilot Learning Hub Team -lastUpdated: 2026-04-02 +lastUpdated: 2026-09-02 estimatedReadingTime: '8 minutes' tags: - glossary @@ -247,6 +247,20 @@ An installable package that extends GitHub Copilot CLI with a bundled set of age --- +### Agent Merge + +A feature available in both the GitHub Copilot app and VS Code's Agents window (v1.136+, Preview) that automates carrying a pull request to completion. It monitors CI/CD checks, addresses review feedback and failing tests, resolves merge conflicts, reruns workflows, and can merge the pull request once everything passes—repeating the cycle until the PR is ready. + +**Example**: Enabling Agent Merge on a session so that once its PR is opened, Copilot keeps addressing CI failures and reviewer comments without you manually re-prompting it. + +**When to use**: For routine PR follow-through where you want Copilot to handle the iterative fix-review-merge loop instead of you monitoring it manually. + +**Learn more**: [Getting Started with the GitHub Copilot app](../github-copilot-app/) + +**Related terms**: [Coding Agent](#coding-agent), [Agent](#agent) + +--- + ### Tools Capabilities that GitHub Copilot can invoke to perform actions or retrieve information. Tools fall into two categories: