OpenAI Will Retire Custom GPTs in December 2026
The company is transitioning to a standardized plugin architecture to unify its extension mechanisms.
Updated on Oct. 5, 2026 in Artificial Intelligence

Live Poll
Will your current AI workflows function effectively after the transition to the new plugin architecture?
OpenAI will retire Custom GPTs on December 11, 2026, as it shifts its ecosystem toward a new plugin architecture. This change consolidates various extension tools into a single, reusable format supporting Model Context Protocol servers.
Why it matters
By consolidating AI extension mechanisms into a unified plugin format, OpenAI is aiming for greater interoperability between ChatGPT and its broader developer tools. The move forces a migration of legacy GPT logic, potentially altering how automated workflows function.
The new architecture utilizes Model Context Protocol servers to handle extension requests. Existing GPT instructions are converted into skills, while knowledge files are mapped to reference files within the new plugin system.
The players
OpenAI
Developer of the ChatGPT platform and LLM research labs responsible for the transition to a plugin-based architecture.
The details
Creators must migrate existing GPTs manually through the My GPTs interface. In this transition, GPT instructions are redefined as skills, and knowledge files are migrated into a structured reference file format. Importantly, existing GPT conversations do not carry over to the new system, and migrated plugins will default to private access settings upon deployment.
Timeline
October 26, 2026: Enterprise workspaces stop creating new Custom GPTs.
December 11, 2026: Custom GPTs officially retire.
February 11, 2027: Final deadline for qualifying Enterprise deferrals.
The Tech Race
This transition aligns OpenAI with the broader industry trend toward standardized, vendor-neutral integration protocols. By moving away from proprietary GPTs, the company is positioning its plugin architecture to better support the evolving Model Context Protocol ecosystem.
Users currently relying on Custom GPTs will need to initiate manual migrations through the My GPTs interface before the December deadline. Enterprise customers should evaluate if they qualify for the extended February 2027 deferral window to maintain operational continuity.
The takeaway
The end of the Custom GPT era necessitates an immediate audit of existing automated workflows and instruction sets. Developers should prepare for performance variations in their migrated plugins and monitor the My GPTs interface for migration tool availability.
Further reading
For more on the changing landscape of AI developer tools, see our latest coverage in Artificial Intelligence.
Live Poll
Will your current AI workflows function effectively after the transition to the new plugin architecture?









