GitHub Ships Agent Plugins 1.0, Qwen Code Follows

GitHub made Agent Plugins 1.0 generally available on August 12 across VS Code, Copilot CLI, the Copilot SDK and the Copilot app, on every plan. It bundles agent skills and MCP servers into one installable package. An author writes it once instead of packaging skills and MCP config separately for each host CLI.

The spec behind it published six days earlier, on August 6. It lists six co-authors: AWS, Anysphere, Microsoft, OpenAI, Vercel and Google, per the GitHub changelog post. Vendor-specific behavior lives in namespaced directories like com.github.copilot/, so one manifest carries a $schema field plus per-host quirks without forking the package. Org admins get a governance layer too: managed-settings.json controls which plugins can install, including a strictKnownMarketplaces flag to block anything outside approved sources.

The clearer signal came from outside GitHub. QwenLM's qwen-code CLI shipped its own Agent Plugins v1 support in version 0.21.11, dated August 13, one day after GitHub's rollout. That's the first evidence anyone other than a spec co-author is building to the format.

GitHub's post doesn't say what happens when a plugin declares behavior the host CLI doesn't support. It also doesn't say whether strictKnownMarketplaces blocks anything hosted outside GitHub's own marketplace by default.

That's the bet worth tracking. A plugin bundle written once now installs on two competing CLIs instead of one. Whether that becomes a real cross-vendor standard depends on one thing: a third company with no hand in writing the spec building to it next. GitHub and its co-authors doing the integration themselves wouldn't count.