ChatGPT Plugins

Original intent · 初衷

The plugin platform set out to make a language model useful with outside data and services rather than only with what it had been trained on. The launch post describes plugins as tools designed specifically for language models with safety as a core principle, and lists the three jobs they were meant to do: access up-to-date information, run computations, and use third-party services.

Timeline · 时间线

1. 2023-03 · month-level

   OpenAI announces initial support for plugins in ChatGPT, described as tools that let the model access up-to-date information, run computations and use third-party services.

   [plugins-launch-announcement]
2. 2023-11 · month-level

   OpenAI introduces GPTs and their actions, saying the new capability builds on insights from the plugins beta and that an existing plugin manifest can define a GPT's actions.

   [plugins-to-gpts-actions]
3. 2026-05-29 · date-level

   OpenAI's plugins quickstart repository is archived and becomes read-only.

   [plugins-quickstart-archived]

Dates are shown at the precision the sources provide; nothing is rounded up to a full date.

What happened · 后来发生了什么

OpenAI opened plugins as a waitlisted beta in March 2023. In November 2023 the company announced GPTs and their actions, stating that actions built upon insights from the plugins beta and that an existing plugin manifest could be converted into a GPT's actions. Developers were later directed away from the plugins model: OpenAI's retrieval-plugin repository describes 'the ChatGPT plugins model (deprecated)' and recommends custom actions with GPTs instead. The plugin platform's starter repository was archived and made read-only in May 2026. Plugins were not switched off on the day GPTs launched; the platform was superseded and then wound down over the following years.

Why it stopped · 停止原因

OpenAI's own statements describe a consolidation rather than a failure: GPTs are presented as the successor that benefits from the plugin beta's lessons, and the migration from a plugin manifest to GPT actions is described as straightforward. No statement in the collected evidence explains whether plugin adoption or safety review drove the change, so this entry does not claim one.

Curator's reading · 策展人分析

Facts cite a source. Author statements are the makers' own words. Curator analysis and hypotheses are marked as interpretation.

What remains · 留下了什么

No leftover artifact is recorded for this entry: no public repository, demo or write-up we could verify.

What the makers learned · 制作者总结

This is the archive's case of an AI platform ecosystem that was replaced by the platform owner rather than by a competitor. The developer-facing lesson is about dependency: a plugin built against the plugins beta had to be re-expressed as a GPT action within eight months, and the migration path was only possible because the same vendor owned both surfaces. The second lesson is about where the boundary of an 'app store moment' sits: the plugin model put third-party capability inside the assistant, and the successor folded that capability into custom assistants, which changed what a third-party developer was building and who owned the distribution.

If someone tried again · 重做问题

The plugin platform and GPTs both let third parties extend ChatGPT, but under different ownership of the surface. If the plugin model had kept distribution and discovery in developers' hands instead of the assistant's, would the ecosystem have grown differently — or was centralising discovery the point?

Sources and verification · 来源与核验

Status evidence

[plugins-to-gpts-actions] [plugins-quickstart-archived]

Added

2026-09-13

Entry updated

2026-09-13

Last verified

2026-09-13

Project period

2023-03 → 2023-11