Monday Aug 10
COOL TOOLSOpenAI

OpenAI Ends The Agent Plugin Mess

10AUG
ONE FORMAT SIX RIVALS

Every AI coding tool used to speak its own dialect. OpenAI and five rivals just agreed on one shared skill format. Build a skill once, and it now works everywhere.

Every AI vendor built its own plugin format. Skills built for one tool never worked in another.

Agent Plugins packages a skill and its MCP config into one folder. Vercel proposed it; OpenAI, AWS, Microsoft, GitHub, and Cursor signed on. Launch clients include ChatGPT, Codex, Copilot, and VS Code.

No single company controls the format going forward. Expect every major agent platform to adopt it within a year.

full brief & sources

⚡ Why this matters

  • Ends months of developers rebuilding the same skill for every AI tool.
  • First time OpenAI, Microsoft, and rivals ship shared infrastructure instead of competing on it.
  • Sets the packaging layer other agent tools will build on next.

🔍 What happened

  • Vercel drafted the proposal; AWS, Cursor, GitHub, Microsoft, and OpenAI refined it into Agent Plugins 1.0.
  • A plugin bundles Agent Skills (reusable instructions) and MCP server configs (tool connections) in one package.
  • Announced August 6, 2026, timed to GPT-5's first anniversary.
  • Launch clients: ChatGPT, Codex, Cursor, GitHub Copilot, Kiro, and VS Code.
  • Google joined as a core maintainer the same day.
  • The spec is openly licensed with a public technical steering committee, not one company's roadmap.

💬 Smart takes

  • Vercel: frames it as build a plugin once, use it across every compatible agent client.
  • AWS Open Source Blog: positions it as ending duplicate work for portable agent extensions.
  • Skeptic (AgentPatterns.ai): the spec deliberately skips distribution, permissions, and trust, so teams on a single client gain nothing.

🧭 Where this goes

  1. Likelyevery major coding assistant (Copilot, Cursor, Codex) supports Agent Plugins within 6 months.
  2. Likelya plugin marketplace emerges, run by one of the six backers, not a neutral body.
  3. PossibleGoogle's same-day maintainer seat means Gemini clients adopt it by year-end.
  4. Wild Cardthe standard fragments again within 18 months as vendors bolt on proprietary extensions.

🥄 The Spoon Take

Six rivals just agreed a plugin should look the same everywhere. That's rare in AI, where everyone competes on lock-in. The format is a truce, not a product. Whoever builds the marketplace on top of it wins, and the spec conveniently skips that part.

🤔 Pushback

The spec skips distribution, permissions, and trust, so single-client teams gain nothing and multi-client teams still need a marketplace layer.

·The New Stack - Agent Plugins standard·Vercel - Introducing Agent Plugins·AWS Open Source Blog - Agent Plugins support·AgentPatterns.ai - What the spec skips