← Nov 6 · Where to Launch ☰ All Live Sessions Friday Live · Own It
Dr. Erin Jacques · Friday Live
Friday Live · November 13

Your custom GPTs are being retired.

On December 11, every custom GPT stops working.

If you built a GPT, this is the week to deal with it. Today I'll show you what's happening, what OpenAI is replacing it with, why that replacement may not do what you want, and how to take your assistant off their platform so nobody can retire it on you again.

28 days
until custom GPTs stop working
What's happening

OpenAI is retiring custom GPTs.

This is straight from OpenAI's own help page. They're retiring custom GPTs and moving creators to something called plugins.

👉🏽 Your old chats are safe. OpenAI says existing conversations with custom GPTs stay accessible after retirement. It's the GPT itself that stops working.

It affects all ChatGPT plans. And if you use someone else's GPT, that one is going away too.

The replacement

What's a plugin?

A plugin is OpenAI's replacement for a GPT. It bundles your instructions, your reference files, and connected apps together.

If you created a GPT, you go to My GPTs and select Migrate to plugin.

What carries over

Your instructions become a "skill" inside the plugin. Your knowledge files get copied over as reference files. Connected apps come along.

What does not

Custom actions don't transfer. If your GPT connects to an outside service, that breaks, and rebuilding it may take a developer. The model you picked doesn't carry over either.

⚠️ Migrating makes the original read-only, and you can't delete it. Finish any edits you care about before you migrate.

Here's the catch.

If you built your GPT to share it, read this part twice.

👉🏽 So if you were using a GPT as something you give out, promote, or sell access to, the replacement doesn't do that job out of the box. That's the real story this week.
Do this today

Get your instructions out. Right now.

Before anything else, go save what you wrote. Those instructions are the actual work, and they're sitting on a platform with a shutdown date.

👉🏽 Do this even if you plan to migrate. Takes two minutes, and it's the thing you can't get back.
The real fix

Own it instead.

A custom GPT was always a rental. It lives inside ChatGPT, your people need a ChatGPT account to use it, you can't charge for it, and OpenAI can retire it. Which is exactly what just happened.

The alternative is to take the same instructions and rebuild them as your own web app: your link, your login, your subscription, your customers.

I've already written the whole thing out, step by step. It's the same tutorial we built this summer, and it works today.

The full tutorial →
👉🏽 You don't have to use Claude. The steps are written for Claude Code, but ChatGPT and Codex can follow them too. Give it the tutorial link and the instructions you just saved.
Prompt — Start it in ChatGPT or Codex
I had a custom GPT and OpenAI is retiring it. I want to rebuild it as my own web app that I own, with its own link, a login, and a subscription. Read this tutorial and follow it: https://drerinjacques.com/custom-assistant Here are my GPT's instructions: [PASTE YOUR INSTRUCTIONS HERE] Start at the beginning and walk me through it one step at a time. Stop and wait for me after each step. Don't assume I know any of the tools.
Easier now

You don't need VS Code anymore.

When I first taught this, you had to install VS Code and work inside it. A lot of you hated that part, and honestly, it was the step where most people quit.

You can skip it. Claude Code and Codex both work in their own app now. And instead of pasting keys around, you connect your tools once and they stay connected.

Do this first, before you build anything

In Claude or in ChatGPT, go to Settings → Connectors and connect the tools you'll use.

GitHub · Supabase · Stripe · Vercel

Once those are connected, you can just say what you want and it can act in those tools for you, instead of you clicking through four dashboards and copying keys between them.

👉🏽 This is the biggest quality-of-life change since I first taught this. If you started the tutorial and gave up at the VS Code part, start again from here.
Then get users

Five places to post your app.

We went deep on this last week. Here's the short version, because it's what you do the moment the app is live: don't post it everywhere, post it to these five first.

Your one next move.

Go copy your GPT's instructions into a document on your computer. Today, not next week. Then pick your date to rebuild it, and post it in the community so I know you did it.

Then come back to last week's session for the full launch walkthrough.

Join us →