OpenAI has transformed ChatGPT plugins into functional mini-applications by adding interactive interfaces and event-driven automation.
The prominent AI developer's efforts to redefine the user experience with chatbots have entered a new phase. Following the introduction of various tools in the form of pages and slides, the next major step focuses on deeper integration of diverse software within the conversation environment so that users can access the tools they need without leaving the chat interface.
During the DevDay event held moments ago in the United States, OpenAI announced that programmers are now able to implement experiences similar to independent applications through plugins. The AI ecosystem previously allowed connections to tools like Slack, SharePoint, Airtable, and Google Drive, but these new capabilities create a dedicated space for these tools in the platform's sidebar.
Developers can now build special interactive panels so that users can simultaneously carry out their operational tasks while chatting with the AI. According to TahaSite, OpenAI has also enabled the integration of custom file viewers for each product's specific formats, ensuring a seamless experience.
The process of creating and publishing these tools has undergone positive changes. The introduction of a new tool called Plugin Creator helps developers speed up the development stages and submit their plugins to the official directory through an optimized process with clearer feedback. At the same time, the ranking and suggestion system for tools has been improved, and users can now review and approve required permissions individually when activating each plugin.
The ability to host plugins has also been extended to lightweight websites built with artificial intelligence, known as ChatGPT Sites. Such a capability allows team members to share their desired applications, along with connected data and permissions, among colleagues.
OpenAI has initiated support for the proposed MCP Events specifications so that plugins can trigger automation workflows based on events occurring within connected software. The process of adding and managing these automation scenarios has also become much simpler than in the past.
Comments