How To Put Your Claude Code Website Online In One Step

Claude Code just built you a site. It runs on your laptop at localhost:5173, it looks finished, and the moment you close the terminal it's gone.

So you ask the obvious question: can Claude Code put this online for you?

It can, and it's shorter than most guides make it look. Your Claude Code website is a folder of files once it's built, and putting a folder online is one request. You don't need a plugin, an API key or an account to get the first link. Claude Code can run the build, send the output to a host, and hand you a live address plus a link to keep it.

What it can't do is host the site itself. Claude Code writes code and runs commands on your machine. It isn't a server, and nothing it starts on localhost is visible to anyone else.

So the job is to get the output somewhere public. I'll show you the one-step version first, then how to check you built the kind of site that can go online this way, then the routes that make the link permanent.

Can Claude Code Host A Website?

No. Claude Code is a coding agent that runs on your computer. It can write the site, build it and start a local preview, but that preview only exists on your machine, and it stops when you close the session.

Hosting means a computer somewhere else serves your files to anyone who asks, all day. So the real question is how Claude Code gets your files onto one.

There are three common ways:

• A host's command-line tool, such as the Vercel or Netlify CLI. Claude Code installs it and runs it. Usually needs you to sign in first, though both had a temporary no-account mode when I checked in November 2026.
• An MCP server. A small tool server Claude Code can call directly, with the host's deploy built in.
• A plain HTTP request. Claude Code zips the files and sends them with curl. Nothing to install.

The third is the one that needs nothing from you, so start there.

If you started in a chat rather than Claude Code and you're holding one HTML file instead of a project, the shortcut for a Claude HTML file is quicker still.

Does Your Claude Code Website Need A Server?

Usually not. Most sites Claude Code builds are files: a React, Vue, Svelte, Astro or plain Vite project that turns into a dist or build folder of HTML, JavaScript and CSS. Those can go anywhere. Check before you deploy, though, because the answer decides which hosts can take it.

Some are servers. If Claude Code built routes that run on the server, reads a database, or keeps a secret key that has to stay hidden at runtime, the output isn't just files.

If you're not sure, ask Claude Code directly: "Does this project need a server at runtime, or is the build output static files?" It can read its own code and tell you in one line.

What Happens When You Ask Claude Code To Deploy?

You type one sentence and it does five things. In the project folder, something like "build this and put it online, then give me the link" is enough.

1. It runs the build. Usually npm run build, which writes the finished site to dist, build or out.
2. It zips the output folder. Only the output, never the source, node_modules or package.json.
3. It asks before sending. In its standard permission mode, Claude Code asks before running a shell command like curl, unless you've already allowed it. Say yes. Claude Code's permissions documentation
4. It sends the zip to a host. One POST request to a no-account deploy address.
5. It gives you two links. The live site, and a claim link with an expiry time.

That's the whole thing. The temporary link and the claim window are the same pattern every big host now uses, and how deploying without an account works covers it in detail, including how long each host waits.

Why It Works With No Plugin

Claude Code can read a website, and some hosts publish instructions written for agents to read. The common format is a file called llms.txt at the site's root, a convention described at llmstxt.org. Ours tells an agent exactly which address to post a built app to and what to give back to the user.

I tested this on 8 November 2026. In an empty Vite project, with no plugin, no MCP server and no settings, Claude Code built the app, zipped dist, posted it and came back with a live URL and a claim link. Nobody told it how. It read the instructions and followed them.

The same request works from any agent that can run a shell command, though Claude Code is the only one I've tested end to end. If Node.js is installed, npx oxypages does the build, the zip and the upload as one command.

A Walkthrough: A Bakery Menu Built In Vite

Here's a typical one. Say a small bakery wants a one-page menu with a filter for gluten-free items, and Claude Code builds it in Vite with React: one page, about a dozen components, and a JSON file of products.

The prompt can be as plain as: "Build this and deploy it somewhere I can share. I don't have an account anywhere."

Claude Code runs these, asking once before the last line:

npm run build
cd dist && zip -r ../dist.zip . && cd ..
curl -sS -X POST https://api.oxypages.com/drops/app -H "X-Oxy-Agent: claude-code" -F "file=@dist.zip"

It comes back with a link on a random unclaimed- address, a claim link, and a note that the site goes offline in 30 minutes. On a project this size the whole thing usually takes under a minute, most of it the build.

Then the check that matters. Open the link on a phone, tap the gluten-free filter, and refresh the page on the filtered view. It should load. A refresh on a sub-page is the first thing that breaks on a badly configured host, and app drops on our side switch on single-page app routing so it doesn't.

Last step: claim it, then copy the new address. The temporary one stops working once you claim, so that's the one to send. A free account is fine for a personal project, but a bakery menu is commercial, so that one belongs on a paid plan.

Making It Permanent

The temporary link is a preview. To keep the site, and to update it later without starting over, you want it in an account. These are the options, roughly in the order I'd reach for them:

For a site you'll touch once a month, claiming is enough. Ask Claude Code to deploy a new version when you change something.

For a site you'll change every week, put it on GitHub. Each push builds and deploys by itself, and you get a history to roll back to.

What Usually Goes Wrong?

Four things, and none of them are the host's fault.

• A blank page. The build set a base path for a subfolder, so the page asks for scripts at the wrong address. Ask Claude Code to check base in vite.config.
• Refresh shows a 404. The app uses client-side routing and the host isn't sending every path to index.html. Turn on the host's single-page app setting, and fixing a 404 on refresh covers the other hosts.
• A secret in the bundle. Anything in a VITE_ or NEXT_PUBLIC_ variable ends up in the JavaScript every visitor downloads. Never put a private API key there.
• The deploy command was refused. You said no to the network prompt, or your settings block curl. Allow that one command.

If the site loads but something on it is broken, that's usually the code, not the deploy. The checklist for an AI website that isn't working walks through the usual suspects.

OxyPages is the wrong place for a Claude Code project that needs a server. We serve the built files only, with no server functions, so an app with API routes or a database belongs on Vercel, Netlify or Cloudflare Workers.

What To Do Next

Open the project in Claude Code and check one thing: is the build output static files? If it is, you're one sentence from a live link.

1. Ask: "Is the build output static files, or does this need a server?"
2. If it's static, ask it to build and deploy, and allow the network command.
3. Open the link on your phone and refresh a sub-page.
4. Claim it, then share the new address.

Ready to try it? Ask Claude Code to deploy your site to OxyPages with no account, and see what comes back. When you want to keep a personal project, start a free account, no card needed, and claim it.