GitHub brings Agent Plugins 1.0 to VS Code, Copilot CLI and its Copilot app

GitHub has made Agent Plugins 1.0 generally available across VS Code, Copilot CLI, the GitHub Copilot SDK and the GitHub Copilot app, giving developers a more portable way to package tools for coding agents. The August 12 changelog post says support is available on all Copilot plans and is meant to let plugin authors build one package that compatible agent clients can discover instead of maintaining separate formats for every surface.

The announcement follows the publication of the Agent Plugins 1.0 specification on August 6 with AWS, Anysphere, Microsoft, OpenAI and Vercel, with Google joining as a core maintainer the same day. The public Agent Plugins documentation describes the project as a vendor-neutral package format for reusable components that extend AI agents, combining agent skills and Model Context Protocol server configuration in a predictable directory structure.

What changes for developers

For plugin authors, the main change is packaging. GitHub says a plugin can now bundle reusable instructions, such as a deployment runbook, together with the MCP server configuration that gives an agent access to the underlying tool. Instead of reshaping that bundle for each client, authors can put portable pieces in common locations and reserve client-specific behavior for namespaced folders. GitHub's migration guidance centers on adding a schema field to plugin.json, placing skills under skills/, putting MCP configuration in mcp.json, and moving Copilot-only files into com.github.copilot/.

The practical promise is narrower than a universal app store for agents, but still important: agent clients that support the standard can read the same package and load the pieces they understand. GitHub also says existing Copilot plugins that do not target Agent Plugins 1.0 remain supported, so teams are not being forced into an immediate migration.

Enterprise controls carry over

GitHub is also tying the rollout to enterprise management. Copilot Business and Enterprise administrators can use existing managed settings to install or block plugins, define additional known marketplaces, or restrict installs to approved marketplaces. The company says those policies apply across VS Code, Copilot CLI, the Copilot app and Copilot cloud agent, while MCP allowlists can still govern individual servers by URL, command or name.

That governance layer matters because agent plugins can carry tool access as well as instructions. Standard packaging makes distribution easier, but it also raises the value of clear approval paths for which agent extensions are allowed inside a company's development environment.

Sources

• github.blog
• agent-plugins.org

Cover photo by Lukas Blazek on Pexels, used under the Pexels License.