chatgpt + codex

Run your site from ChatGPT

Edit your site by talking to ChatGPT. Here's how to get set up — whether you've used Codex before or this is your very first time. You don't need an API key or any tokens, just your ChatGPT plan.

You manage your site through Codex, the part of ChatGPT that works on code. Point it at your site once, then describe the change you want in plain language. Every change arrives as a draft with its own preview link, so you always see it before anyone else does.

Prefer Claude? The same guide for Claude Code →

The GitHub repository for your site, as owner/name.

Have you used Codex before?

  1. Open Codex in ChatGPT one-time setup

    Sign in at chatgpt.com/codex with your usual ChatGPT account. Codex is the part of ChatGPT that works on your site's files — it's the same subscription you already have, not a separate product to buy.

    Open Codex →

    Codex comes with every ChatGPT plan, but the part this guide uses — where it works on your site for you, in the cloud — needs Plus or above. On the Free and Go plans Codex only runs on your own computer.

  2. Connect GitHub one-time setup

    GitHub is the service that stores your site's files. In ChatGPT, open Plugins, find GitHub, and click Install plugin. ChatGPT shows a short "Connect GitHub" screen — click Continue to GitHub and approve it there. If GitHub asks which repositories to allow, pick your site (or allow all of them — either is fine).

    The GitHub entry in the ChatGPT Plugins directory, with an Install plugin button The Connect GitHub confirmation screen in ChatGPT, with a Continue to GitHub button
    Plugins → GitHub → Install plugin, then approve the connection on GitHub.

    What this connection does and doesn't do. It lets ChatGPT read your site, which is handy on its own — you can ask "what does my pricing page say?" and get a real answer. It does not let ChatGPT change anything. Making changes is Codex's job, and Codex asks for its own GitHub approval the first time you give it a task. Approve that one too; it's the same one-click flow.

  3. Point Codex at your site one-time setup

    In Codex, open Settings → Environments and create an environment for your site. An environment is just Codex's private workspace for doing the work — it isn't your website's hosting, and nothing about your live site changes here. Choose your repository:

    What this screen asks you for

    Repositoryyour site — the one above
    Branchmain
    Everything elseleave exactly as it is
    You'll only do this once — every task after this reuses it.

    Don't see your site in the list? Codex shows every repository your GitHub account can open — if yours is missing, your account doesn't have access to it yet. Contact us (below) and we'll sort it out.

  4. Ask for a change

    Start a task and describe what you want in plain language — no command, no special wording. Talk about your site, not about code:

    • "Add a Black Friday banner to the homepage — 50% off, ends Monday."
    • "Rewrite the about page in a warmer, less corporate tone."
    • "The pricing page says $49 in two places and $59 in one. Make them all $59."

    Your site carries its own instructions for AI assistants, and Codex reads them before it starts. That's why you don't have to ask for a draft or explain how your site is built — it already knows to keep your live site untouched and give you something to look at first.

  5. Press "Create PR"

    When Codex finishes it shows you a summary and the exact edits it made, and waits. Press Create PR to turn that work into a draft of your site.

    What you'll see when Codex finishes

    A summarywhat it changed, in words
    The editsevery change, file by file
    Create PR← the one to press
    Codex hands the work back and waits for you — this button is the step people miss.

    This is the one thing to remember. Until you press it, the change exists only inside Codex: your site doesn't have it, there's nothing to preview, and it won't appear in your drafts list. Not happy with the result? Ask Codex for a follow-up first, and press it when it's right.

  6. Preview it, then publish

    A minute or two after you press Create PR, BlinkPages builds your draft and posts an Open Preview link on it. Open that link to see the change on a real copy of your live site — the rest of the internet still sees the old version.

    Always use the link BlinkPages posts rather than guessing an address. When you're happy, open your site editor, find the draft in the list, and hit Publish — that's what puts it on your real site. If the preview link never appears, the build didn't succeed; contact us and we'll take a look.

Good to know

You don't need an API key.
Your ChatGPT subscription does the work. There's no OpenAI key to bring and nothing to pay per edit here.
Cloud tasks need ChatGPT Plus or above.
Codex is in every plan, but having it work on your site for you — without installing anything — starts at Plus. On Free and Go it runs only on your own computer.
Connecting GitHub isn't the same as letting it edit.
The GitHub connection on its own is read-only: great for asking questions about your site, but it can't change a thing. Codex is the part that makes changes, and it asks for its own approval.
Asking for options gives you separate previews.
Ask for a few versions and each one gets its own draft and its own preview link to compare. They arrive as independent drafts, so publishing one doesn't clear the others away — discard the ones you don't want.
"Edit with AI" requests need a different route.
Changes you queue from the Edit with AI card on your live site can't be picked up by Codex in the cloud — it works with the internet switched off. Just ask Codex for the change directly instead.
It only touches your site.
Codex edits your content and pages, and only inside your own repository. It can't see or reach any other site.

A permalink with this site filled in, ready to hand to whoever runs the site.

Stuck, or not sure your site has the editor turned on? Contact us and we'll get you set up.