Dev.to WebDev 🛠 Dev 👁 0 📖 4 min read

ChatGPT Remix Lets You Fork a Teammate's AI-Built Site in Chat — Here's What It Means for People Who Build Websites

This post was originally published on ConvertElementor. I build websites for a living, mostly with WordPress and Elementor, and I have watched AI site builders go from a curiosity to a real part of how clients start pro

This post was originally published on ConvertElementor.

I build websites for a living, mostly with WordPress and Elementor, and I have watched AI site builders go from a curiosity to a real part of how clients start projects. On November 6, 2026, OpenAI started rolling out Remix for ChatGPT Sites, and it changes how teams iterate on the sites ChatGPT builds. Here is what it is, and why it matters even if you never touch ChatGPT Sites.

What Remix actually is

ChatGPT Sites is OpenAI's public-beta tool for building hosted websites: describe what you want in chat, and it generates a site. The problem was what happened next. A teammate built a decent first version, and anyone else who wanted to build on it had to start over, or ask the original author for edits.

Remix fixes that specific problem. It lets a workspace member copy a teammate's ChatGPT Site, describe the changes in plain language, and keep editing their own version in chat. It is the "fork" button from open source, applied to websites.

How a remix works

The flow is deliberately simple. Open a teammate's Site, describe the changes in plain language, and Remix creates your own copy with those changes applied. You keep editing your version in chat from there. That simplicity is the whole pitch: the person remixing does not need to know how the original was built.

Remix is not the same as co-editing

This is the distinction most people will get wrong, so let me be precise: OpenAI offers both, and they solve different problems.

Co-editing — the "Can edit" permission — means several people change one Site at one URL. Everyone edits the same page.

Remix is the opposite shape: a separate copy for variants or template reuse, at its own address, evolving on its own. Co-editing is everyone committing to the same branch; Remix is a fork. Teams that treat Remix as just another way to co-edit will be confused when their changes do not show up on the original.

What it costs, and the limits that come with it

Remix is rolling out to ChatGPT Business and Enterprise accounts; OpenAI has not said whether it will come to Plus or Pro. There is no separate Remix charge, but per OpenAI's Help Center, building or editing a Site counts toward Codex usage — and Remix is editing, so it draws on the same usage. Two other limits are worth knowing: Enterprise hosting charges for Sites are currently waived — free for now — but that is a promotional state, not a promise.

Why this matters for WordPress and Elementor builders

On the surface Remix has nothing to do with WordPress — a ChatGPT feature, for sites hosted by OpenAI. But the workflow it normalizes is coming for us. Here is how that plays out. A client builds a first version in ChatGPT — a landing page, a booking form — and brings it to you. Until now, that AI-built draft was a dead end: you could look at it, maybe screenshot it, and rebuild it properly in WordPress. With Remix, the draft becomes a living starting point the client can iterate on, and the conversation between the client and the builder gets much richer.

That changes the work in two ways. First, the AI-built draft stops being a dead end and becomes a brief — a working prototype you can respond to instead of a screenshot you have to interpret. Second, the fork-and-iterate pattern becomes the expectation: clients will expect to try a variant, compare it, and keep the better one, the way developers have forked repositories for decades.

The honest limits I would not skip

First, the audience: Business and Enterprise only, with no word on Plus or Pro. The freelancers and small studios who build most WordPress sites are not in the room yet.

Second, a fork is a fork: it diverges. Nothing in the announcement describes merging a remixed version back into the original, so a remix is a one-way street for now.

Third, ownership. A ChatGPT Site lives on OpenAI's hosting, inside a ChatGPT workspace, and nothing in the announcement describes exporting a Site or moving it to WordPress. If you build your business on a remixed Site, you are building on rented land.

What I would do this week

If you are on a Business or Enterprise workspace, try Remix once on a real site, not a demo: pick a teammate's Site, fork it, and see how far plain-language edits get you. If you are a freelancer or a small studio, do not buy a Business workspace just for Remix — watch where it goes, and practice the workflow with the tools you already have. And if you build with WordPress and Elementor, take the lesson, not the threat: the fork-and-iterate pattern is becoming how clients think about websites, and the builders who can work with that pattern will win the work.

The bottom line

Remix is a small feature with a large idea inside it: a website is not a document you finish, it is a thing you fork, change, and keep evolving. For those of us who build websites professionally, the message is not that ChatGPT will replace us. It is that the clients we serve are learning to iterate the way developers do — and we should be ready to meet them there.

Read the full article on ConvertElementor: ChatGPT Remix Lets You Fork a Teammate's AI-Built Site in Chat — Here's What It Means for People Who Build Websites

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.