OpenAI, AWS, Microsoft, Cursor and Vercel Launch Agent Plugins, a Shared Format So One Plugin Runs Across Rival AI Tools, Logiciel Tech News

OpenAI, AWS, Microsoft, Cursor and Vercel Launch Agent Plugins, a Shared Format So One Plugin Runs Across Rival AI Tools.

Five companies that normally fight over the same developers agreed on something on August 6, 2026: one way to package the add-ons that extend AI agents. They call it Agent Plugins 1.0.0, an open standard from OpenAI, AWS, Microsoft, Cursor, and Vercel. The pitch is simple. Build a plugin once and it runs in any tool that supports the format, instead of rebuilding it for each one. The name missing from the list is the part worth noticing: Anthropic, which created both of the technologies the new format bundles together.

Robert

Logiciel Tech News

Aug 7, 2026 2 min read

OpenAI, AWS, Microsoft, Cursor and Vercel Launch Agent Plugins, a Shared Format So One Plugin Runs Across Rival AI Tools

What Agent Plugins Actually Does

A plugin here is just a folder with a manifest file, plugin.json, at its root. Inside it packages two things developers already use. Agent Skills, which are reusable instruction sets, go in a skills/ directory. MCP server settings, which connect an agent to live tools and data, go in an mcp.json file. Anything specific to one client lives in reverse-domain named folders so nothing collides.

The standard wraps both pieces in a portable contract, so any compatible client can find and load the same plugin. Vercel, which first proposed the idea, describes it as "a small interoperability floor for the parts that can be portable." In plainer terms: agree on the boring shared layer, let everyone compete above it.

Who's In, and Who's Missing

A technical steering committee of core maintainers from AWS, Cursor, Microsoft, OpenAI, and Vercel runs the spec. At launch it works in six clients: ChatGPT, Codex, Cursor, GitHub Copilot, Kiro, and VS Code. Development is public, with proposals handled through GitHub.

Then there's Anthropic. Its Model Context Protocol has become the default way agents talk to external tools, its Agent Skills format is the other half of what Agent Plugins wraps, and its own Claude products already ship a plugin system. Yet it isn't on the committee. A cross-vendor plugin standard built largely on one company's work, without that company at the table, is a strange thing to launch, and nobody in the announcement explains it.

The Pushback

Not everyone is sold on the substance. Dax Raad, who created the SST developer framework, called it "a thin standard" and argued the genuinely useful parts will drift back into each platform's own extensions anyway. Other developers raised the same worry from a different angle: how deep can a shared format go when every client wants its own behavior?

It's a fair hit. A standard that only covers the lowest common denominator can get quietly ignored the second a vendor wants to do something its rivals can't.

One Thing to Watch

All of this rests on the clients continuing to honor it. Standards like this survive when maintaining a separate plugin for every tool becomes more trouble than just agreeing. They fall apart when one big player decides its own way is better and walks. Right now six clients read the same plugin, which is more agreement than this corner of the industry usually manages. What Anthropic does next, join, ignore, or ship a rival, probably decides how far it actually goes.