You can now build a plugin once and use it across all compatible agent clients. We published Agent Plugins 1.0 on August 6 with AWS, Anysphere, Microsoft, OpenAI, and Vercel.…
The post Agent Plugins 1.0 in VS Code, Copilot CLI, and the Copilot app appeared first on The GitHub Blog.
You can now build a plugin once and use it across all compatible agent clients. We published Agent Plugins 1.0 on August 6 with AWS, Anysphere, Microsoft, OpenAI, and Vercel. Google also joined as a core maintainer on the same day. Agent Plugins 1.0 is an open standard that packages agent skills and MCP servers into one installable plugin that is governed independently of any single vendor.
Publishing a plugin for several agents was already possible, but it cost you duplication. A plugin can bundle a skill with an MCP server, such as a deployment runbook and its tool integration. While the skill and the server underneath were the same for every client, the packaging around them wasn’t, so you maintained a separate manifest and directory layout for each one.
Support is generally available in VS Code, Copilot CLI, the GitHub Copilot SDK, and the GitHub Copilot app, on all Copilot plans.
What you can doIf you maintain a plugin, adopting the spec is mostly manifest work:
$schema to plugin.jsonskills/ and MCP configuration in mcp.jsoncom.github.copilot/ directory, which other clients ignoreThat last step is what keeps a plugin portable without giving anything up. The spec standardizes skills and MCP servers, so Copilot capabilities beyond those live in the namespaced directory. Custom agents, commands, rules, and hooks load from there across VS Code, Copilot CLI, and the Copilot app, and the CLI and app also load extensions such as canvases. One package stays portable and keeps its Copilot behavior.
See Build an Agent Plugin for the minimal package and where each component goes, or start from the example plugin and migration guide.
Govern plugins with the settings you already useAs plugins become portable across tools, organizations need a consistent way to manage which plugins are available to developers. Copilot Business and Enterprise customers can use existing enterprise managed settings across VS Code, Copilot CLI, the GitHub Copilot app, and Copilot cloud agent.
In managed-settings.json, use enabledPlugins to automatically install or block specific plugins, extraKnownMarketplaces to add marketplaces available to developers, and strictKnownMarketplaces to restrict installation to managed marketplaces. Enterprise values establish a baseline, and plugin and marketplace settings combine additively with approved team-specific overrides. To learn more, see our docs on setting overrides for specific teams.
If you already manage these plugin settings for supported Copilot clients, they also apply to Agent Plugins 1.0. No separate Agent Plugins policy is required.
Plugins can also carry MCP server configurations, so pair this with MCP allowlists, which approve or block individual servers by URL, command, or name.
Learn more| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | GitHub Copilot weekly releases — August 10 | 0 | 8.51 | 14-08-2026 |
| 2 | От MCP к Agent Plugins 1.0: зачем бизнесу переносимые плагины для ИИ-агентов | 0 | 16.92 | 12-08-2026 |
| 3 | Grok 4.6 is now available in GitHub Copilot | 0 | 11.88 | 14-08-2026 |
| 4 | Gemini 3.7 Flash is now available in GitHub Copilot | 0 | 7.68 | 13-08-2026 |
| 5 | 2026 release wave 1 plans for Microsoft Dynamics 365, Microsoft Power Platform, and Copilot Studio offerings | 0 | 11.66 | 18-03-2026 |
| 6 | GitHub Enterprise Server 3.22 release candidate | 0 | 12.84 | 11-08-2026 |
| 7 | Naumen ускоряет переход контакт-центров к применению ИИ-агентов | 5 | 7 | 13-07-2026 |
| 8 | Naumen ускоряет переход контакт-центров к применению ИИ-агентов | 5 | 7 | 13-07-2026 |
| 9 | Simplify Debug Configuration for Every Project | 0 | 7.52 | 12-08-2026 |
| 10 | Anybody gone down the Copilot Studio route? | 0 | 5 | 08-07-2026 |