AI 服務暫時不可用，以下為來源正文，待恢復後補全翻譯。
Credit: Canva The AI race spent two years being about models. This week it moved to the plumbing. On the eve of GPT-5’s first birthday, OpenAI and four rivals published Agent Plugins, an open standard that lets a single agent extension work across competing products. The pitch is “build once, run anywhere”. Today, every agent tool expects a different folder layout and setup. Agent Plugins replaces that with one package format. It bundles two things developers already use. The first is Model Context Protocol servers, which connect an agent to live tools and data. The second is Agent Skills, reusable sets of instructions. A plugin is just a folder with a small plugin.json file at its root. Who is behind it Despite the OpenAI billing, this is not an OpenAI product. Vercel initiated the proposal. Representatives from Amazon, Cursor’s maker Anysphere, GitHub, Microsoft, OpenAI, and Vercel then shaped the 1.0 specification. The steering committee has five members: Amazon, Cursor, Microsoft, OpenAI, and Vercel. The project is openly licensed, and its backers say no single company’s roadmap sets its direction. OpenAI still framed the launch as its own milestone. GPT-5 turns one on 7 August, and the company is marking the week by looking beyond individual models, per 9to5Mac. Its ChatGPT and Codex apps support the format at launch, alongside Cursor, GitHub Copilot, Kiro, and VS Code. The move goes further than OpenAI’s own Codex plugins, which work only inside its tools. Deliberately small The standard is narrow on purpose. It defines how a plugin is packaged and found, and little else. Marketplaces, installation, permissions, sandboxing, and trust all stay with each client. That keeps the format easy to adopt. It also leaves the hardest problems unsolved. Deciding whether a plugin is safe to run is still every client’s own job, a live worry after fake Agent Skills slipped past security scanners earlier this year. Not everyone is convinced. Dax Raad, who builds the SST developer-tools framework, said he was “very much against” it, calling it “a thin standard” whose useful parts will end up in client-specific extensions anyway. Others cheered. “We neeeeded this,” wrote developer advocate Angie Jones, who had wanted one way to carry her skills between the tools she uses. The bigger question is what standardising the plumbing does to competition. A shared format could let a small developer reach every major agent at once. That is the open-ecosystem case, and it is a real one. It could also cement the handful of clients that already have the users, because a standard rewards whoever people already run. For now the plumbing is agreed. The fight over the parts it leaves out, the marketplaces and the trust, has barely started. Get the TNW newsletter Get the most important tech news in your inbox each week.