---
title: "How to deploy a website from Claude Code to a live URL"
description: "Claude Code can put the site it just built online with one command, cool publish, at name.cool.computer, with no hosting account to set up first."
canonical: "https://www.cool.computer/blog/deploy-website-from-claude-code"
last_updated: "2026-11-20"
---
# How to deploy a website from Claude Code to a live URL

> Claude Code can put the site it just built online with one command, cool publish, at name.cool.computer, with no hosting account to set up first.

To deploy a website from Claude Code, give it the `cool` CLI and ask it to publish. Claude Code runs `cool publish ./dist --name my-site --visibility private`, and the site is live at `https://my-site.cool.computer` a few seconds later, open only to you and the people you invite. There is no hosting project to create, no repository to connect and no build settings to fill in. It is free and needs no card.

A private site needs you to be signed in. Without an account Claude Code can still publish: the site is public, and you sign in afterwards to keep it.

## Steps

1. Paste this into Claude Code:

   ```text
   set up cool computers for me: follow https://cool.computer/setup.md and build me an artifact about the last thing i was working on, and annotate and draw on it once i'm signed up
   ```

   Claude Code installs `cool`, publishes a first page, then signs you up with your email and a six-digit code. [/setup](/setup) is the walk it follows.

2. Ask for what you want online, for example "publish the landing page you just built, private". Claude Code builds the project if it needs a build, then runs:

   ```sh
   cool publish ./dist --name my-site --visibility private
   ```

   A single file works the same way: `cool publish page.html --name my-site --visibility private` publishes it as the site's `index.html`.

3. Open the URL it prints. A private site opens only for you and the people you invite:

   ```sh
   cool share add my-site ana@example.com
   ```

   To open it to everyone, run `cool share public my-site`.

4. Ask for a change. Claude Code edits the files and publishes to the same site, so the link you shared keeps working:

   ```sh
   cool publish ./dist --computer my-site
   ```

### Connect it for good

The setup prompt is enough to start. To make Cool Computers part of every Claude Code session, install the plugin from Anthropic's official marketplace:

```sh
claude plugin install cool-computers@claude-plugins-official
```

Then run `/mcp` in Claude Code, choose `plugin:cool-computers:cool-computers` and sign in. The plugin adds the MCP server and a skill that teaches Claude when to publish a page, how to answer comments and when a site needs a VM. More on [the Claude Code page](/claude-code).

### Let Claude Code act on feedback

People who can open the site can pin comments to any element and draw on it. Claude Code listens for the ones you send it, in a background terminal:

```sh
cool comments watch my-site --agent "Claude Code"
```

While it listens, each comment card has an Ask Claude Code button. Press it to hand the comments to Claude Code, which makes the change, publishes again and resolves them. You review on the page instead of describing the problem in chat. [This post](/blog/get-feedback-on-a-prototype) covers the review loop.

## What it can deploy

- Static sites: HTML, CSS, JavaScript and images, or the output folder of a framework build such as Vite, Astro or a Next.js static export.
- Single-page apps: add a `cool.json` with `{"spa": true}` and every path that is not a file serves `index.html`.
- A small backend: a `cool.json` with `functions` adds an API under `/api` that runs at the edge, with an optional SQLite database and secrets. No server to keep running.
- A real server: a program that has to stay up, such as a bot, a queue worker or a scheduled job, gets an always-on Ubuntu VM at the same address. VMs need Pro.

Publishing never runs your build. Claude Code runs it first, then publishes the output folder.

## Why and when to use it

Use it when Claude Code made something a person should open in a browser: a prototype, a report, a dashboard, a landing page.

- No setup between the code and the link: one command, and Claude Code already knows it.
- Private by default: Claude Code publishes private unless you ask for public, and tells you which it is.
- A link that lasts: each publish is a new release at the same address. `cool releases my-site` lists them, and `cool releases promote my-site 2` puts release 2 back.
- Not tied to Claude Code: Codex, Cursor or a chat app can publish to the same site later.

A production app with staging environments, preview deployments per pull request and a team already on a hosting provider should stay on that provider's CLI. This is for the page that should be online in the next minute.

## Questions

### Can Claude Code deploy a website by itself?

Yes. Claude Code runs shell commands, so once `cool` is installed it publishes with `cool publish` and gives you the URL. It does not need a hosting dashboard or a token pasted into the chat.

### Do I need an account to deploy from Claude Code?

No. Without an account the site is public and the output includes a claim link. Open it and sign in within 24 hours to keep the site, or it is deleted. A private site needs an account.

### Is it free?

Yes. Free costs nothing and needs no card: up to 20 sites at once, sharing 5 GiB of published content. Pro, USD 20 a month, lifts the limit on sites and adds VMs. See [pricing](/pricing).

### Can Claude Code deploy a React or Next.js app?

Yes, as a build. Claude Code runs the build and publishes the output folder, such as `./dist` or `./out`. An app that needs a Node server at runtime runs on a VM, which is on Pro.

### Can I use my own domain?

Yes. `cool domain set my-site app.example.com` prints the two DNS records to create at your DNS provider.

### Does it work where Claude Code cannot run the CLI?

Yes. The plugin's MCP server publishes through the `cool_publish` tool instead. One call takes at most 64 KiB of arguments, so a larger site goes through the CLI.

The same steps for other agents are in [this post](/blog/ai-agent-publish-website), and sites people published with their agents are on [/explore](/explore).
