Agent Plugins 1.0.0: The New Open Standard for AI Coding Tools

Five rivals just agreed on a plugin format

On 6 August 2026, Amazon, Cursor’s maker Anysphere, Microsoft, OpenAI and Vercel jointly released Agent Plugins 1.0.0 – an open standard for packaging Agent Skills and MCP servers into a single, portable unit. That’s a genuinely unusual amount of consensus from companies that normally compete hard on tooling, and it’s worth understanding what it actually changes rather than filing it under “yet another AI standard announcement”.

What problem this is solving

Before Agent Plugins, a skill or MCP server you built for Claude Code didn’t travel cleanly to Cursor, Codex, or any other agent. Each tool had its own packaging conventions, its own manifest format, its own install mechanism. If you wanted your extension available everywhere, you were maintaining several near-duplicate versions of the same thing. Agent Plugins fixes the packaging layer specifically – not the skills or MCP servers themselves, which already had their own emerging conventions, but the container around them: how a bundle declares what it needs, how a host discovers it, and how it gets installed.

What’s actually inside a plugin

• One or more Agent Skills – the instructions-plus-scripts pattern that teaches an agent how to do a specific task
• One or more MCP servers – the connectors that give an agent access to external tools and data
• Hooks and agent configuration, where the host tool supports them
• A manifest describing what’s bundled, version constraints, and any required permissions or credentials

The point is that a plugin author writes this bundle once, and any host that implements the Agent Plugins spec can install it – no per-tool repackaging.

Who’s actually shipping support

OpenAI moved fastest on the consumer side: Codex CLI 0.147.0, released the following day (7 August 2026), added the ability to install portable Agent Plugins and search local, personal, workspace, and remote plugin catalogs. Given Codex and Claude Code are direct competitors in the terminal-agent space, that’s a strong signal the standard isn’t just a press-release exercise – actual engineering time went into it within days of the announcement.

What this means if you build or use Claude Code plugins

1. Existing Claude Code plugins built around Skills and MCP servers are already close to the Agent Plugins shape – the underlying pieces are the same, it’s the manifest and packaging that need to conform.
2. If you maintain a plugin you’d like to see used outside Claude Code, this is the moment to check whether it’s Agent Plugins-compliant, since Codex support already exists and other hosts are likely to follow given the backing list.
3. For everyday users, the practical upside is a larger effective plugin catalog over time – a well-built plugin doesn’t need a specific author decision to support your tool of choice, as long as your tool implements the spec.

What’s still unresolved

A shared packaging format doesn’t guarantee identical behaviour across hosts – a plugin that assumes Claude-specific tool semantics, or relies on a capability one host has and another doesn’t, will still need testing per platform. Cross-tool portability at the packaging layer is a real and useful step, but it’s not the same as write-once-run-anywhere for the plugin’s actual logic. Treat early “works everywhere” claims with a bit of caution until the spec has had more real-world mileage, and check a plugin’s declared host compatibility before assuming it’ll behave identically outside the tool it was built for.

Worth watching

The list of backers is the interesting part here – five companies that are otherwise fighting hard for the same developer attention chose to standardise the boring, unglamorous packaging layer rather than compete on it. That’s usually a sign a market has matured past the “everyone builds their own walled garden” phase, at least for the parts that don’t create competitive advantage on their own. Worth keeping an eye on which hosts add full support over the next few months, and whether the existing plugin ecosystems (Claude Code’s included) start publishing Agent Plugins-compliant manifests alongside their native ones.