From 556dac41e45122cf21ccd212fc7b305f35ec2d67 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Sat, 29 Aug 2026 20:45:13 +0000
Subject: [PATCH] Update Learning Hub for /plugins dashboard removal and hook
 OTel trace context

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
 .../docs/learning-hub/automating-with-hooks.md        | 11 +++++++++++
 .../docs/learning-hub/installing-and-using-plugins.md | 10 +++++++---
 2 files changed, 18 insertions(+), 3 deletions(-)

diff --git a/website/src/content/docs/learning-hub/automating-with-hooks.md b/website/src/content/docs/learning-hub/automating-with-hooks.md
index 8864598f55..01e1a6ddf8 100644
--- a/website/src/content/docs/learning-hub/automating-with-hooks.md
+++ b/website/src/content/docs/learning-hub/automating-with-hooks.md
@@ -176,6 +176,17 @@ You can also use these as **template variables** directly in the `bash` or `powe
 
 This makes it straightforward to write plugin hooks that are portable across machines and projects without hardcoding paths.
 
+### OpenTelemetry Trace Context (v1.0.81+)
+
+Hooks can now receive the current OpenTelemetry trace context so their work can be correlated with the session's telemetry spans. Hook inputs gain a `traceparent` field (plus `tracestate` when the active span carries vendor-specific state), and command hooks also receive these as environment variables:
+
+| Variable | Description |
+|----------|-------------|
+| `TRACEPARENT` | The W3C Trace Context `traceparent` header value for the current span |
+| `TRACESTATE` | The W3C Trace Context `tracestate` header value, when present |
+
+This lets hook scripts emit their own OpenTelemetry spans as children of the session's trace, making it possible to see hook execution alongside tool calls and model requests in your observability backend.
+
 ### Event Configuration
 
 Hooks support two types: `"command"` for running local shell scripts, and `"http"` for sending JSON payloads to a URL.
diff --git a/website/src/content/docs/learning-hub/installing-and-using-plugins.md b/website/src/content/docs/learning-hub/installing-and-using-plugins.md
index 65952b5fef..bd6267089a 100644
--- a/website/src/content/docs/learning-hub/installing-and-using-plugins.md
+++ b/website/src/content/docs/learning-hub/installing-and-using-plugins.md
@@ -239,13 +239,17 @@ copilot plugin uninstall my-plugin
 
 ### Enabling and Disabling Plugin Components
 
-*(v1.0.76+)* The `/plugins` command (or `copilot plugin list` in non-interactive mode) now includes **enable/disable toggles** for individual plugin components. You can turn off specific agents, instructions, hooks, LSP servers, or entire plugins without uninstalling them:
+*(v1.0.81+)* The former `/plugins` command has been replaced by the **plugins dashboard**, now available to everyone via `/plugin`, `/mcp`, or `/skills` — there is no separate `/plugins` command anymore. Each entry point opens the same dashboard, scoped to the relevant resource type:
 
 ```
-/plugins
+/plugin
 ```
 
-This opens an interactive list where each installed plugin and its components are shown with a toggle. Disabling a component hides it from Copilot without removing it from disk — useful for temporarily deactivating a hook that is too noisy, or turning off a plugin's instructions when working on a different type of project. Re-enable the component at any time from the same `/plugins` menu.
+This opens an interactive list where each installed plugin and its components are shown with a toggle so you can turn off specific agents, instructions, hooks, or entire plugins without uninstalling them. Disabling a component hides it from Copilot without removing it from disk — useful for temporarily deactivating a hook that is too noisy, or turning off a plugin's instructions when working on a different type of project. Re-enable the component at any time from the same dashboard.
+
+> **Note**: Enabling and disabling hooks and LSP servers directly is temporarily unavailable — those toggles previously lived only in the removed `/plugins` dashboard.
+
+The dashboard also flags installed plugins and marketplaces that have a newer version upstream, with an **Update** action to pull it directly from the list.
 
 ### Loading Plugins from a Local Directory