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 8864598f..062a402d 100644 --- a/website/src/content/docs/learning-hub/automating-with-hooks.md +++ b/website/src/content/docs/learning-hub/automating-with-hooks.md @@ -3,7 +3,7 @@ title: 'Automating with Hooks' description: 'Learn how to use hooks to automate lifecycle events like formatting, linting, and governance checks during Copilot agent sessions.' authors: - GitHub Copilot Learning Hub Team -lastUpdated: 2026-07-13 +lastUpdated: 2026-08-30 estimatedReadingTime: '8 minutes' tags: - hooks @@ -641,6 +641,15 @@ echo "Pre-commit checks passed ✅" - Test scripts manually before adding them to hooks.json - Use reasonable timeouts—formatting a large codebase may need 30+ seconds +### OpenTelemetry Trace Context in Hooks + +*(v1.0.81+)* Hooks can now receive the current OpenTelemetry trace context, letting hook scripts emit spans that are correlated with the agent session's own tracing: + +- Hook inputs gain a `traceparent` field (plus `tracestate` when the span carries vendor-specific state). +- Command hooks also receive these values as environment variables, so a script can pass them straight to any OpenTelemetry-instrumented tooling it shells out to. + +This is useful if your organization already exports Copilot CLI traces and wants hook-triggered automation (lint runs, deployments, notifications) to show up as child spans in the same trace, rather than as disconnected events. + ## Best Practices - **Keep hooks fast**: Hooks run synchronously, so slow hooks delay the agent. Set tight timeouts and optimize scripts. 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 7951ecaf..6d0e8d7e 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-07 +lastUpdated: 2026-08-30 estimatedReadingTime: '8 minutes' tags: - copilot-app @@ -159,6 +159,8 @@ Each session runs in its own worktree with its own isolated environment. You can ### Launching Sessions from the Terminal with Deep Links +*(v1.0.81+)* You can also open the GitHub Copilot app directly from Copilot CLI by running `copilot app` in a repository directory — this launches (or focuses) the app and opens a session scoped to the current directory, without needing to construct a deep link manually. + The GitHub Copilot app supports URL deep links. This is useful when you want to open the app or start a session directly from your terminal workflow. Supported schemes: 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 65952b5f..c51439a4 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 @@ -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-08-19 +lastUpdated: 2026-08-30 relatedArticles: - ./building-custom-agents.md - ./creating-effective-skills.md @@ -237,15 +237,19 @@ copilot plugin uninstall my-plugin > **Auto-update for first-party plugins** *(v1.0.78+)*: Plugins sourced from the official `copilot-plugins` marketplace automatically update to their latest version at the start of each session. You do not need to run `copilot plugin update` for first-party plugins — updates are applied silently on startup. Community plugins from `awesome-copilot` and other marketplace registries still require a manual `copilot plugin update` command. +> **Update notifications** *(v1.0.81+)*: The `/plugin` dashboard now flags installed plugins and marketplaces that have a newer version upstream, and offers an **Update** action to pull the latest version directly from the dashboard — no need to remember to run `copilot plugin update` manually. + ### 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 standalone `/plugins` command has been **removed**. Its functionality now lives in the always-on **plugins dashboard**, accessible via `/plugin`, `/mcp`, or `/skills` (or `copilot plugin list` in non-interactive mode). Use `/subagents` for agents and `/instructions` for instruction files: ``` -/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 dashboard where each installed plugin and its components are shown with **enable/disable toggles**. You can turn off specific agents, instructions, hooks, LSP servers, or entire plugins without uninstalling them — disabling a component hides it from Copilot without removing it from disk, which is useful for temporarily deactivating a noisy hook 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**: The `PLUGINS_DASHBOARD` opt-out environment variable (introduced in v1.0.76) has also been removed in v1.0.81 — the dashboard is now available to everyone by default, and toggling individual hooks/LSP servers off is temporarily unavailable following this change. ### Loading Plugins from a Local Directory diff --git a/website/src/content/docs/learning-hub/understanding-mcp-servers.md b/website/src/content/docs/learning-hub/understanding-mcp-servers.md index 3e02a142..acd82509 100644 --- a/website/src/content/docs/learning-hub/understanding-mcp-servers.md +++ b/website/src/content/docs/learning-hub/understanding-mcp-servers.md @@ -3,7 +3,7 @@ title: 'Understanding MCP Servers' description: 'Learn how Model Context Protocol servers extend GitHub Copilot with access to external tools, databases, and APIs.' authors: - GitHub Copilot Learning Hub Team -lastUpdated: 2026-07-13 +lastUpdated: 2026-08-30 estimatedReadingTime: '8 minutes' tags: - mcp @@ -213,6 +213,10 @@ Some MCP servers require authentication to connect to protected resources. GitHu > **Tip**: If your MCP server uses OAuth with Dynamic Client Registration but hosts its authorization metadata at a non-standard URL (as some enterprise servers like Atlassian Rovo do), Copilot CLI handles this automatically. +> **Windows Entra ID broker sign-in** *(v1.0.81+)*: On Windows, remote MCP servers protected by Microsoft Entra ID can now sign in through the OS authentication broker (WAM), usually with no prompt at all. Other platforms, the `--device-code` flag, and machines without the broker library continue to use the existing browser-based flow. + +> **MCP spec support** *(v1.0.81+)*: Copilot CLI, the SDK, IDE integrations, and in-memory clients now support the **MCP 2026-07-28** specification revision, keeping pace with the latest protocol capabilities. + ## How Agents Use MCP Tools When an agent declares an MCP server in its `tools` array, Copilot can invoke that server's capabilities during conversation: