AIToday
Large Language ModelsAI Business & IndustryImpress WatchPublished: Sep 29, 2026, 16:00 JST

OpenAI ends カスタム GPT on 12月11日, pushes Plugins

OpenAI ends カスタム GPT on 12月11日, pushes Plugins

3 Key Points

  1. What happened

    OpenAI will retire ChatGPT's Custom GPTs on December 11 across all ChatGPT plans, telling creators to migrate to Plugins. Approved Enterprise workspaces can keep them until 27年2月11日.

  2. Why it matters

    Migrations use only the latest published GPT version, so chosen models, カスタムアクション, and existing conversations are not carried over, and migrated Plugins start private.

  3. What to watch

    People using someone else's GPT cannot migrate it themselves and get no automatic Plugin access, so it hinges on the creator's guidance. Enterprise workspaces stop new Custom GPT creation on 10月26日.

WHO IT HITSChatGPT users who rely on Custom GPTs built by colleagues or third parties may lose access unless the creator migrates and re-shares. Enterprise workspace admins and internal tool builders face a migration deadline before December 11, or 27年2月11日 if approved.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

OpenAI is consolidating ChatGPT's builder tools around Plugins, which bundle reusable instructions, reference files, and connected apps. Migration is deliberately partial: instructions and knowledge files move over, but the chosen model, custom actions, and past conversations are left behind. The migrated Plugin is also created as private, and the original GPT's sharing settings do not carry over, so creators likely need to re-share it with their audiences.

For Enterprise workspaces, the timeline is tighter in one respect: new Custom GPT creation ends on 10月26日, and any draft that needs to move must be published before then. The shutdown itself is December 11, with an extension to 27年2月11日 only for workspaces that meet conditions and are approved for a deferral.

Consumers are largely bystanders. If you use a GPT someone else built, you cannot migrate it, you are not granted migration rights, and having access to the old GPT does not automatically grant access to a replacement Plugin. The practical stakes therefore hinge on whether creators act and re-share. The same pattern is appearing elsewhere, with Google's Gemini custom apps, Gem, also set to end in stages from November.

FAQ
Can I migrate a Custom GPT that someone else made?
No. Users of other people's GPTs do not need to migrate and are not given migration permission. They must wait for the creator's guidance and check their access.
What exactly carries over when a GPT becomes a Plugin?
The latest published GPT version is used: instructions become skills, knowledge files are copied to reference files, and connected apps are added. The chosen model, custom actions, and existing conversations do not carry over.
What happens to the original GPT after migration?
It stays usable until the shutdown date but becomes read-only. Creators can no longer delete it, and further changes are made on the Plugin side.

AI news that matters for your work, in one minute a day

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleNVIDIA unveils Open Agent Safety Platform to police AI agents