OpenAI Adds App-Like Interfaces to ChatGPT Plugins, Plans Event Triggers
Developers can put their tools in ChatGPT’s sidebar and within conversations. Planned support for connected-app events would let automations start without a new request.
Loading page…
Developers can put their tools in ChatGPT’s sidebar and within conversations. Planned support for connected-app events would let automations start without a new request.
Listen to this story
OpenAI is making ChatGPT plugins more like embedded apps: developers can add dedicated sidebar spaces, interactive controls and viewers for their products’ file formats. The update also includes a Plugin Creator and changes to plugin submissions and recommendations, while ChatGPT Sites can host shared app experiences without combining users’ separate connections or permissions. A different, still-planned capability would let events in connected apps launch plugin automations through the proposed MCP Events specification, moving some work beyond chat-initiated requests.
OpenAI introduced the plugin extensions at Dev Day on September 29.
Users can approve a plugin’s access needs individually; appearing in a directory or conversation does not grant access.
OpenAI says its redesigned submission flow is intended to give plugin developers clearer feedback.
ChatGPT plugins are gaining space to work, not just a way to connect to other services. At Dev Day on September 29, OpenAI introduced extensions that let developers build sidebar homes, interactive panels and file viewers for their plugins. It also said it is adding support for automations triggered by events in connected apps—a planned capability, not a completed one.
ChatGPT already supports plugins that connect to services such as Slack, SharePoint, Airtable and Google Drive. The new extensions let developers give a plugin a dedicated home in the ChatGPT sidebar. An interactive panel can put the tool’s controls within reach while someone is chatting, rather than leaving the connection entirely behind the conversation.
Developers can also add viewers for the file formats their products use. That gives a plugin room to show the material someone is working with, not merely retrieve information from another service. The change is in how a connected product can be presented and used inside ChatGPT.
OpenAI introduced a Plugin Creator to help developers build plugins and redesigned how they submit them to its directory. The submission flow is intended to give developers clearer feedback. OpenAI also says it has improved how plugins are ranked and recommended, both in the directory and when they appear during a conversation.
Being shown a plugin is separate from granting it access. When users choose one, they can approve its access needs individually. That distinction becomes more important as OpenAI gives plugins more visible places to appear and more ways to work with connected material.
ChatGPT Sites, the lightweight websites people can build with ChatGPT, can host plugins too. In OpenAI’s example, colleagues using a shared Site could work with the same app experience while each uses their own connected data and permissions. Sharing the Site would not mean sharing one person’s account connections.
For that second path, OpenAI says it is adding support for the proposed MCP Events specification. An event in a connected app would then be able to start a plugin automation, instead of the work beginning with a request in the chat. OpenAI also says it is making automations easier to add and manage.
The distinction is worth keeping in view: the panels give people a new way to work with a plugin now, while event-triggered automation remains a capability OpenAI says it is adding. One changes where the tool can be used; the other would change what sets it in motion.
Loading discussion...
Join the conversation
When would that help, and when would you want to approve it?
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.