VS Code、Copilot CLI 与 Copilot app 支持 Agent Plugins 1.0

现在，你可以只构建一次插件，并在所有兼容的 Agent 客户端中使用。我们于 8 月 6 日与 AWS、Anysphere、Microsoft、OpenAI 和 Vercel 一同发布了 Agent Plugins 1.0；Google 也在同日加入成为核心维护者。Agent Plugins 1.0 是一项开放标准，可将 Agent 技能和 MCP 服务器打包为一个可安装插件，并由独立于任何单一厂商的机制进行治理。

此前，虽然已可为多个 Agent 发布插件，但这意味着需要重复维护。一个插件可以将某项技能与 MCP 服务器捆绑在一起，例如部署运行手册及其工具集成。尽管底层的技能和服务器对每个客户端都相同，但围绕它们的打包方式并不相同，因此你需要为每个客户端维护独立的清单文件和目录布局。

VS Code、Copilot CLI、GitHub Copilot SDK 和 GitHub Copilot app 现已全面支持该规范，适用于所有 Copilot 套餐。

• 从市场安装规范插件。 你可以在 Awesome Copilot marketplace 中查找插件；该市场默认在 VS Code、Copilot CLI 和 Copilot app 中可用。
• 在工具之间共享同一个插件。 兼容客户端可以从同一软件包中发现其所支持的技能和 MCP 服务器配置。
• 保留现有插件。 不面向 Agent Plugins 1.0 的现有 GitHub Copilot 插件仍将继续获得支持，无需迁移。

如果你维护一个插件，采用该规范主要涉及清单文件相关工作：

• 在 plugin.json 中添加 $schema
• 将技能保留在 skills/ 下，并将 MCP 配置放在 mcp.json 中
• 将 Copilot 专属文件移入 com.github.copilot/ 目录，其他客户端会忽略该目录

最后一步使插件能够在不牺牲任何功能的前提下保持可移植性。该规范标准化了技能和 MCP 服务器，因此超出这些范围的 Copilot 功能将存放在带命名空间的目录中。自定义 Agent、命令、规则和钩子会在 VS Code、Copilot CLI 和 Copilot app 中从该目录加载；CLI 和 app 还会加载画布等扩展。一个软件包既能保持可移植性，也能保留其 Copilot 行为。

请参阅 Build an Agent Plugin，了解最小软件包及各组件的存放位置；你也可以从示例插件和迁移指南开始。

随着插件能够在不同工具之间移植，组织需要一种一致的方式来管理哪些插件可供开发者使用。Copilot Business 和 Enterprise 客户可在 VS Code、Copilot CLI、GitHub Copilot app 以及 Copilot cloud agent 中使用现有的企业托管设置。

在 managed-settings.json 中，使用 enabledPlugins 自动安装或阻止特定插件，使用 extraKnownMarketplaces 添加开发者可用的市场，并使用 strictKnownMarketplaces 将安装限制在受管理的市场中。企业级设置建立基础策略，而插件和市场设置会与已批准的团队专属覆盖设置以叠加方式组合。要了解更多信息，请参阅我们关于为特定团队设置覆盖规则的文档。

如果你已经为受支持的 Copilot 客户端管理这些插件设置，它们同样适用于 Agent Plugins 1.0。无需单独制定 Agent Plugins 策略。

插件还可以携带 MCP 服务器配置，因此应将其与 MCP 允许列表配合使用；该允许列表可按 URL、命令或名称批准或阻止单个服务器。

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.

• Install spec plugins from a marketplace. You can find plugins in the Awesome Copilot marketplace, available by default in VS Code, Copilot CLI, and the Copilot app.
• Share one plugin across tools. Compatible clients can discover the skills and MCP server configuration they support from the same package.
• Keep your existing plugins. Existing GitHub Copilot plugins that don’t target Agent Plugins 1.0 remain supported, with no migration required.

If you maintain a plugin, adopting the spec is mostly manifest work:

• Add $schema to plugin.json
• Keep skills under skills/ and MCP configuration in mcp.json
• Move Copilot-specific files into the com.github.copilot/ directory, which other clients ignore

That 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.

As 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.