Update Learning Hub for July 2026 Copilot releases

- Add grok-4.5 model to building-custom-agents model selection table (CLI v1.0.76+)
- Document granular plugin enable/disable controls in installing-and-using-plugins (CLI v1.0.76+)
- Add subagent visibility improvements to agents-and-subagents (VS Code 1.131+)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

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-07-30
 estimatedReadingTime: '9 minutes'
 tags:
   - agents
@@ -109,6 +109,16 @@ Then summarize the findings into one recommendation.
 
 By default, subagents do not keep spawning additional subagents. In VS Code, recursive delegation is controlled by the `chat.subagents.allowInvocationsFromSubagents` setting, which is off by default.
 
+### 5. Monitor subagent progress *(VS Code 1.131+)*
+
+VS Code 1.131 added improved subagent visibility directly in the chat interface. While a subagent is active, you can see:
+
+- **Model**: which AI model the subagent is using
+- **Elapsed time**: how long the subagent has been running
+- **Active tool call**: the tool the subagent is currently executing
+
+This makes it easier to understand what's happening during complex orchestrated tasks without needing to dig into logs or wait for the subagent to finish before getting feedback.
+
 ## Launch subagents in Copilot CLI
 
 In GitHub Copilot CLI, the clearest end-user entry point is **`/fleet`**. Fleet acts as an orchestrator that decomposes a larger objective, launches multiple background subagents, respects dependencies, and then synthesizes the final result.

website/src/content/docs/learning-hub/building-custom-agents.md

@@ -3,7 +3,7 @@ title: 'Building Custom Agents'
 description: 'Learn how to create specialized GitHub Copilot agents with custom personas, tool integrations, and domain expertise.'
 authors:
   - GitHub Copilot Learning Hub Team
-lastUpdated: 2026-07-09
+lastUpdated: 2026-07-30
 estimatedReadingTime: '10 minutes'
 tags:
   - agents
@@ -259,6 +259,7 @@ The agent can then query your database, analyze query plans, and suggest optimiz
 | Code generation, tool-driven agentic work | GPT-5.6 *(v1.0.70+)* |
 | Code generation, refactoring | GPT-4.1 |
 | Code-specialized tasks, large context | kimi-k2.7-code *(v1.0.68+)* |
+| Fast response, broad knowledge | grok-4.5 *(v1.0.76+)* |
 | Quick analysis, simple tasks | Claude Haiku or GPT-4.1-mini |
 | Large codebase understanding | Models with larger context windows |
 

website/src/content/docs/learning-hub/installing-and-using-plugins.md

@@ -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-07-13
+lastUpdated: 2026-07-30
 estimatedReadingTime: '8 minutes'
 tags:
   - plugins
@@ -232,6 +232,32 @@ copilot --plugin-dir /path/to/my-plugin
 
 Plugins loaded this way appear in `/plugin list` under a separate **External Plugins** section, clearly distinguished from marketplace-installed plugins. This is useful for testing local plugins in development or loading private plugins that aren't published to any marketplace.
 
+### Enabling and Disabling Plugin Components *(v1.0.76+)*
+
+After installing a plugin, you can selectively enable or disable individual components without uninstalling the whole plugin. This lets you use only the parts of a plugin that are relevant to your current work:
+
+```
+/plugins          # open the plugin management panel
+```
+
+From the panel, you can toggle on or off:
+- Individual **agents** from a plugin
+- Individual **skills**
+- **Instructions** bundled with the plugin
+- **Hooks** and **LSP servers**
+
+You can also manage components from the CLI:
+
+```bash
+# Disable a specific agent from a plugin
+copilot plugin disable my-plugin/agents/api-architect
+
+# Re-enable it later
+copilot plugin enable my-plugin/agents/api-architect
+```
+
+This granular control is useful when a plugin ships multiple agents but you only need one, or when a plugin's hooks conflict with your local configuration.
+
 ### Where Plugins Are Stored
 
 - **Marketplace plugins**: `~/.copilot/installed-plugins/MARKETPLACE/PLUGIN-NAME/`