Agent Plugins 1.0 发布：VS Code、Copilot CLI 与 Copilot
Agent Plugins 1.0 in VS Code, Copilot CLI, and the Copilot app
AI 编程插件开发者注意：Agent Plugins 1.0 是跨客户端插件标准，一次构建即可在 VS Code、Copilot CLI 等复用，且现有插件无需迁移。建议阅读迁移指南，按规范调整清单结构，以保持可移植性。
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.
您现在可以构建一次插件，并在所有兼容的代理客户端中使用它。我们于8月6日发布了Agent Plugins 1.0，合作方包括AWS、Anysphere、Microsoft、OpenAI和Vercel。Google也在同一天作为核心维护者加入。Agent Plugins 1.0是一个开放标准，将代理技能和MCP服务器打包成一个可安装的插件，该插件独立于任何单一供应商进行治理。
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.
为多个代理发布插件以前也是可能的，但需要重复工作。一个插件可以将技能与MCP服务器捆绑在一起，例如部署手册及其工具集成。虽然技能和底层服务器对每个客户端都是相同的，但围绕它们的打包方式不同，因此您需要为每个客户端维护单独的清单和目录结构。
Support is generally available in VS Code, Copilot CLI, the GitHub Copilot SDK, and the GitHub Copilot app, on all Copilot plans.
在VS Code、Copilot CLI、GitHub Copilot SDK和GitHub Copilot应用中，所有Copilot计划均普遍支持。
What you can do
您可以做什么
- 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.
- 从市场安装规范插件。您可以在Awesome Copilot市场中找到插件，该市场在VS Code、Copilot CLI和Copilot应用中默认可用。
- 在工具之间共享一个插件。兼容的客户端可以从同一个包中发现它们支持的技能和MCP服务器配置。
- 保留您现有的插件。现有的不针对Agent Plugins 1.0的GitHub Copilot插件仍然受支持，无需迁移。
Building or migrating a plugin
构建或迁移插件
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
- 在plugin.json中添加$schema
- 将技能保留在skills/下，并将MCP配置放在mcp.json中
- 将Copilot特定的文件移动到com.github.copilot/目录中，其他客户端会忽略该目录
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.
最后一步是保持插件可移植而不放弃任何功能的关键。该规范标准化了技能和MCP服务器，因此Copilot超出这些的功能位于命名空间目录中。自定义代理、命令、规则和钩子从那里加载，跨VS Code、Copilot CLI和Copilot应用，CLI和应用也加载扩展，如画布。一个包保持可移植性并保留其Copilot行为。
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 use
使用您已有的设置来治理插件
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.
随着插件在不同工具间变得可移植，组织需要一种一致的方式来管理哪些插件对开发者可用。Copilot Business 和 Enterprise 客户可以在 VS Code、Copilot CLI、GitHub Copilot 应用和 Copilot 云代理中使用现有的企业管理设置。
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.
在 managed-settings.json 中，使用 enabledPlugins 自动安装或阻止特定插件，使用 extraKnownMarketplaces 添加可供开发者使用的市场，使用 strictKnownMarketplaces 将安装限制在受管理的市场。企业值建立基线，插件和市场设置与批准的团队特定覆盖相结合。要了解更多信息，请参阅我们关于特定团队设置覆盖的文档。
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.
如果您已经为受支持的 Copilot 客户端管理这些插件设置，它们也适用于 Agent Plugins 1.0。无需单独的 Agent Plugins 策略。
Plugins can also carry MCP server configurations, so pair this with MCP allowlists, which approve or block individual servers by URL, command, or name.
插件还可以携带 MCP 服务器配置，因此请将其与 MCP 允许列表配对，该列表通过 URL、命令或名称批准或阻止单个服务器。
Learn more
了解更多
- Plugins in VS Code
- Finding and installing plugins in Copilot CLI
- About GitHub Copilot plugins
- Published Agent Plugins 1.0 specification
- VS Code 中的插件
- 在 Copilot CLI 中查找和安装插件
- 关于 GitHub Copilot 插件
- 已发布的 Agent Plugins 1.0 规范
The post Agent Plugins 1.0 in VS Code, Copilot CLI, and the Copilot app appeared first on The GitHub Blog.
文章《Agent Plugins 1.0 在 VS Code、Copilot CLI 和 Copilot 应用中》首次出现在 GitHub 博客上。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力