Cursor, OpenAI, Microsoft, AWS and Vercel agree a shared plugin format — AI coding tools stop being separate silos
Agent Plugins 1.0, published 6 August 2026 by Vercel with AWS, Anysphere (Cursor), Microsoft and OpenAI, is a vendor-neutral package format for AI agent skills and MCP servers that already loads on day one in ChatGPT, Codex, Cursor, GitHub Copilot, Kiro and VS Code — a direct answer to the search for a standard AI coding tool format.
19 August 2026
Five of the biggest names in AI coding tooling — AWS, Anysphere (Cursor’s maker), Microsoft, OpenAI and Vercel, who initiated the proposal — published Agent Plugins 1.0 on 6 August 2026. It’s a small, deliberately narrow specification: a folder with a plugin.json manifest that packages an MCP server and a set of agent skills into one installable unit any compatible client can load. Six tools support it immediately — ChatGPT, Codex, Cursor, GitHub Copilot, Kiro and VS Code — with GitHub shipping support the same week.
The problem it solves is one every team that’s tried more than one AI coding tool has hit directly: every agent expects its own folder layout, its own manifest format, its own setup steps. A custom internal tool, an MCP server for your API, a house-style skill for how your team writes tests — under the old world, each of those had to be rebuilt separately for Cursor, then again for Copilot, then again for whatever the team switches to next. Agent Plugins means build once, and the plugin follows you across tools rather than locking you into whichever one you built for first.
That’s the detail worth sitting with if you’ve been avoiding investing in AI tooling because you didn’t want to bet on the wrong vendor. The standard deliberately stays out of installation, marketplaces, permissions and sandboxing — it leaves each client to handle security and distribution its own way — so it’s a packaging format, not a security guarantee. But it does mean the switching cost between AI coding tools just dropped, and the tooling investment you make today has a real chance of surviving your next platform decision.
So what
If you’ve held off building internal AI-agent tooling — a skill for your codebase conventions, an MCP connector into your own systems — because you weren’t sure which coding assistant your team would standardise on, that’s less of a blocker now. We build AI-assisted development workflows around the tools that actually fit a project, not a single vendor’s ecosystem — see our AI-assisted development approach, or get in touch if you want help scoping what’s worth building versus what a plugin can now solve off the shelf.