DUSK GPT is becoming a Plugin


What happened to "If it ain't broke, don't fix it"?

From December 11th, custom GPT agents are being retired.

OpenAI says custom GPTs are being retired because it wants creators to move those workflows into Plugins, which can combine reusable instructions, reference material, connected apps/tools, and more structured capabilities in one package.

Plugins can bundle Skills, external connections through MCP, and in some cases UI or other workflow components, and the same plugin framework can work across ChatGPT and Codex through a shared directory.

So what does this mean for DUSK GPT? It too will need to migrate to a Plugin.

Whilst DUSK is migrating, you can still use the GPT Agent as normal, right up until the cut-off date.

The bigger picture though, is what will happen to the thousands of public GPTs that will inevitably not get migrated, either due to their creators not realising, or choosing not to bother, missing the cut-off date?

The biggest hurdle, is that Plugins cannot be made public by default. There is a whole submission process to Open AI for approval, which can take weeks to review and verify submitted applications.

In addition, this change fundamentally affects how a user interacts with these custom creations. A GPT agent behaves very differently to a plugin. Instead of starting a new chat with the agent, you install the plugin and then call it to action with the @ action. There will be a required shift in interaction to adjust to these migrated tools.

It might not sound like the world's biggest change, but there will be a large volume of users who will find this initially confusing to say the least.

I will be starting the migration process for DUSK soon, and hopefully will get it approved for public use as soon as possible.

Will keep you all posted!


1
6