claude code

Run your site from Claude Code

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

You manage your site through Claude Code. Open your repository, describe the change you want, and Claude makes it and ships it to your live site. Here's how to get going — pick the path that matches you.

Prefer ChatGPT? The same guide for ChatGPT →

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

Have you used Claude Code before?

  1. Sign in to Claude Code one-time setup

    Go to claude.ai/code and sign in with your Claude account — the same login you use for Claude chat. Claude Code is included in the paid Claude plans (Pro, Max, and Team); if you're on the free plan, it asks you to upgrade before letting you in.

    Open Claude Code →

    Using the Claude desktop app instead of the browser? Click the Code tab, and when it asks where to work, choose Remote — that's the flow this guide follows. (Local is for folders on your own computer.)

  2. Connect your GitHub account one-time setup

    The first thing Claude Code asks a new account to do is connect GitHub — the service that stores your site's code. Follow the prompt, and GitHub walks you through approving the Claude GitHub App:

    1. Sign in to GitHub if it asks you to.
    2. Pick your GitHub account (or the organization that owns your site).
    3. Choose which repositories Claude can use — "All repositories" is the easy choice, or select just your site.
    4. Click Install & Authorize, and GitHub sends you straight back to Claude Code.

    That one-time approval is the only credential you'll ever need — no API key to buy, no token to paste. You can add or remove repositories later from your GitHub settings. And if Claude Code still shows only a GitHub login button afterwards, the connection didn't finish — click it and run through the approval once more.

    GitHub will start emailing you about activity on your site — none of it needs anything from you. Here's how to turn that off (two minutes): stop GitHub emailing you.

  3. Create your environment one-time setup

    Next, Claude Code asks you to create an environment — its private workspace for doing the work. This is the screen that makes new users nervous, and it shouldn't: leave every field exactly as it is and click Create environment.

    What you'll see on this screen

    Nameany name works — "My site" is fine
    Network accessset to "Full"
    Environment variablesleave empty
    Setup scriptleave empty
    Create environment← the only thing to click
    The one-time environment screen, field by field — nothing to change.

    An environment isn't your website's hosting — nothing about your live site changes here. You'll only see this screen once; every session after this reuses it automatically.

  4. Open your site's repository

    From here on, this is the whole routine. Start a new session, then click the repository selector — the box just under the message field — and pick your site. You can search for it by name:

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

    Open Claude Code →

    Claude Code home with a New session button Claude Code with the connected repository selected on the main branch
    Start a new session, then pick your repository — it stays selected for next time.

  5. Ask for a change

    Just describe the change in plain language — no command needed. Claude edits your site, shows you what it did, and publishes it to your live site. Your update is live a minute or two later.

    Want options? Ask for a few variations and you'll get separate previews to compare before you pick one.

    Claude Code prompt asking in plain language, with no command, to add a Black Friday sale banner site-wide promoting a 50% off sale on all products
    Ask for any change in plain language, right from Claude Code.

  6. Optional: pick up your "Edit with AI" requests

    Queued a change from the Edit with AI card on your live site? If the editor is turned on for your site, pick those up straight from Claude Code by running /blinkpages on its own:

    The first time, it prints a one-click link. Open it, confirm the code shown, and click Approve. You'll need to be signed in as an editor on your site. After that, Claude works through your queued requests and each in-page card updates on its own.

    Claude Code prompt: /blinkpages
    Run the skill and it works through everything you queued.

Good to know

You don't need an API key.
Your Claude Code session does the work. There's no Anthropic key to bring and nothing to pay per edit here.
It's part of your Claude plan.
Claude Code comes with the paid Claude plans — Pro, Max, and Team. Your edits use your plan's included usage; there's nothing extra to pay here.
You can close the tab.
Sessions keep running after you close the page — on your computer or in the Claude mobile app's Code tab. Come back later and the work is waiting.
It only touches your site.
Claude edits your content and pages, and only inside your own repository. It can't see or reach any other site.
Your domain, your deploy.
Changes go live on your own domain, through the same deploy you already use. Nothing new to host.
GitHub emails you about your site.
Every update to your open drafts shows up as a GitHub email, and none of it needs anything from you. Only you can switch that off — here's how, in two minutes.

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