370
edits
ChatGPT Plugins: Difference between revisions
no edit summary
(Created page with "==Introduction== Language models, such as ChatGPT, have shown their utility in a range of applications, but they remain limited by their reliance on training data. To enhance their capabilities, plugins can serve as "eyes and ears" for language models, providing them with up-to-date, personal, or specific information that is not available in their training data. These plugins also enable language models to perform safe and constrained actions at a user's request, imp...") |
No edit summary |
||
| Line 14: | Line 14: | ||
The integration of a code interpreter aims to create a natural interface for computer capabilities, making workflows more efficient and accessible. Initial user studies have identified several use cases for the code interpreter: | The integration of a code interpreter aims to create a natural interface for computer capabilities, making workflows more efficient and accessible. Initial user studies have identified several use cases for the code interpreter: | ||
Solving mathematical problems | *Solving mathematical problems | ||
Performing data analysis and visualization | *Performing data analysis and visualization | ||
Converting files between formats | *Converting files between formats | ||
==Retrieval== | ==Retrieval== | ||
| Line 28: | Line 28: | ||
Third-party plugins are defined by a manifest file that includes a machine-readable description of the plugin's capabilities, invocation instructions, and user-facing documentation. The process of creating a plugin involves the following steps: | Third-party plugins are defined by a manifest file that includes a machine-readable description of the plugin's capabilities, invocation instructions, and user-facing documentation. The process of creating a plugin involves the following steps: | ||
Develop an API with endpoints that the language model can call. This can be a new API, an existing API, or a wrapper around an existing API specifically designed for language models. | #Develop an API with endpoints that the language model can call. This can be a new API, an existing API, or a wrapper around an existing API specifically designed for language models. | ||
Create an OpenAPI specification to document the API and a manifest file that links to the OpenAPI spec and includes plugin-specific metadata. | #Create an OpenAPI specification to document the API and a manifest file that links to the OpenAPI spec and includes plugin-specific metadata. | ||
Users can select which third-party plugins they want to enable when starting a conversation on chat.openai.com. The language model is shown documentation about the enabled plugins as part of the conversation context, allowing the model to invoke appropriate plugin APIs as needed to fulfill user intent. While current plugins are designed for calling backend APIs, the exploration of plugins capable of calling client-side APIs is ongoing. | Users can select which third-party plugins they want to enable when starting a conversation on chat.openai.com. The language model is shown documentation about the enabled plugins as part of the conversation context, allowing the model to invoke appropriate plugin APIs as needed to fulfill user intent. While current plugins are designed for calling backend APIs, the exploration of plugins capable of calling client-side APIs is ongoing. | ||