Hi, I’m Vibhor, Product Lead for Ecosystem at @OpenAI. I am going to use this space to share what we are doing to further the Ecosystem for our customers, and partners. DevDay feels like a good time to start. One of the best parts of DevDay was the deep collaboration with partners: @Adobe, @Atlassian, @Canva, @Figma, @Instacart, @MagicPathAI, @Shopify, Superpower, and @tldraw. While I went in excited I left with even more conviction in what we’re building together for our shared customers. It was also incredible to meet AI native partners and hear how our platform is empowering them build a sustainable business on ChatGPT 🎉 A conversation is often just the beginning of a task. You describe an idea, work through it, and eventually want something you can use: an edited image, a working prototype, a diagram you can keep refining. Getting there takes great tools and the people who know how to build them. Our ambition is to make those capabilities feel like a natural part of working with ChatGPT. At DevDay, we shared several steps in that direction. 1. Plugin Extensions help our partners bring interactive experiences to ChatGPT. Adobe is a good example. You can ask for an image edit, then adjust the details with hands-on controls. With tldraw, you and the agent can work on a shared canvas. MagicPath brings interactive prototypes into the conversation, with room to edit them yourself. These examples make the idea much more tangible: - Adobe: video.tv.adobe.com/v/3503940 - tldraw: x.lingyaoai.com/tldraw/status/21053958… - MagicPath: x.lingyaoai.com/skirano/status/2104994… - Figma: lnkd.in/gaqHXZjT - Shopify: lnkd.in/ghEXY5GT 2. A useful plugin can package skills, an MCP server, or both. That gives builders different ways to contribute: reusable workflow knowledge, access to live information, or actions that help someone finish a task. We introduced Plugin Creator and improvements to submissions, including automated checks and clearer feedback. Sites can also host supported plugins. There’s still work to do to make building and maintaining a plugin consistently straightforward. 3. We also announced improvements to plugin discovery, ranking and recommendations, in the directory and in conversations. This matters for both sides of the ecosystem. Users need to find something useful when they need it. Developers need a way for their work to reach those users. The goal is to make suggestions genuinely helpful, with good judgment about when they add value and when they get in the way. 4. MCP Events lets users ask ChatGPT to watch for supported events, such as a new message or a document comment, and respond when they arrive. It opens up another way for developers to make their tools useful beyond a single exchange. 5. ChatGPT Sites can now host MCP servers including plugin extensions! Create an MCP server with extensions, deploy the MCP server to Sites, turn the MCP server into a plugin, and install the plugin across platforms. There’s still plenty to do, especially around reliability, discovery and the developer experience. Thank you to the teams and partners doing this work with us. The future feels bright, and we’re just getting started. Onward!