Claude Code on the web: put your site live on your own domain

Claude Code on the web runs your task in a cloud machine that Anthropic manages, on a copy of your GitHub repo. It can build the whole site there. The deploy step is where people get stuck, because that machine only talks to an approved list of websites, and dropthehassle.com is not on the default list. Here are the two ways around it, with no account needed to get a live link.

Your AI can publish. It can never spend your money.

Built it with ChatGPT, Claude, Gemini, Cursor, Replit, v0, Windsurf or by hand? Same steps.

Last updated: 30 September 2026. Network levels, the Trusted domain list, and connector traffic are from Anthropic's cloud environment docs. Plans and the cloud VM are from Claude Code on the web. The command, the 25 MB cap, and the update path are from DropTheHassle CLI 0.3.0 and the server.

This page is only the cloud session (claude.ai/code). Running Claude Code on your own machine is a different guide. Cloud sessions are on Pro, Max, and Team plans, and for Enterprise users with a premium seat or a Chat and Claude Code seat.

Why the deploy fails in a cloud session

Every Claude Code on the web environment has a network access level: None, Trusted, Full, or Custom. The default is Trusted, which allows a fixed list of package registries and code hosts. registry.npmjs.org is on that list, so npx -y dropthehassle deploy downloads fine. dropthehassle.com is not on it, so the environment blocks the upload.

You have two options. Use a connector, which Anthropic says does not go through the session's network, or allow one extra domain.

Route 1. Add DropTheHassle as a connector

Connectors you enable on a session run through Anthropic's servers, not through the sandbox. They keep working under the Trusted setting. Anthropic does not publish one settings URL for the add-connector screen, so use the connector controls in claude.ai.

1. In claude.ai, add a custom connector with this URL: https://dropthehassle.com/mcp. No token.
2. Enable it for your Claude Code on the web session.
3. Ask: "Build the site, then publish the built files with DropTheHassle and give me the claim link."

Claude sends the files to the deploy_site tool and gets back a live address like yourname.dropthehassle.app with HTTPS, plus a claim link. search_domain and whoami work on that URL with no account too. What the connector can and cannot do is on the MCP guide.

The connector sends file contents in the request. Before the site is claimed, that upload can be at most 25 MB, same as the command below. A normal static site fits. Large video often does not. Claiming the site raises a later signed-in update to 100 MB. It does not raise this first upload.

Your AI can find a free name. Only you can pay for it.

Route 2. Allow dropthehassle.com and run the command

A free HTTPS link from one command, no account:

1. On claude.ai/code, open the environment selector (the cloud icon above the message box) and edit the environment.
2. Set network access to Custom.
3. Add dropthehassle.com and tick Also include default list of common package managers, so npm keeps working.
4. Start a session and ask Claude to build the site and run:

npx -y dropthehassle deploy

The command uploads the folder you point at (the current folder, if you name none). The server publishes index.html, or dist/, build/, out/, or _site/ when that is where the built site is. public/ is used only when the upload is not a JavaScript project. It prints the live link and a claim link. You do not need --login. That flag waits for a browser approval and then publishes a new address on your account. DTH_NO_OPEN=1 only stops the command from trying to open a browser. The no-account deploy does not open one.

Full access also works. Anthropic describes Full as any domain, so it opens the session to every site. Custom with one domain plus the default list is the smaller change.

The same 25 MB cap applies here until you claim the site. An unclaimed upload also stops at 1,000 files, and it refuses executable and archive files.

If you prefer to keep the setting in the repo, claude mcp add --scope project writes .mcp.json. Commit that file. A cloud session with one repository loads it. Unlike a connector you enable on the session, that file is not listed as traffic that skips the allowlist, so dropthehassle.com still has to be allowed. A session with several repositories does not load it.

Claim it within 7 days

Ship it on a free link first. Buy the domain when it has visitors. Open the claim link and the site is yours. An unclaimed site is removed after 7 days. From one network you can put 5 new unclaimed sites online per hour, and 20 a day.

The cloud machine is temporary. The first deploy writes .dropthehassle.json in that folder so the next deploy from the same folder updates the same site. If that folder already has a .gitignore, the CLI adds the file to it. Do not commit it. The machine is gone when the session ends, so a later session does not have it.

Without that file, npx -y dropthehassle deploy always creates a new site. The CLI has no flag that takes a token and a site name. --login does not look one up: it asks you to approve a new address in the browser. --slug only applies to that new address, and only together with --login.

To update a site you already claimed:

• Sign in and drop the new folder on that site, or
• On that site, choose Update and let your AI do it. The dashboard shows a code that lasts 15 minutes. In the new session run npx dropthehassle deploy --code XXXX-XXXX. The code fills the site it was made for, not a name you pass on the command, or
• Connect with the token from Connect your AI and ask the agent to list your sites, then publish with deploy_site and that site's site_id. The free-link name is not enough on its own.

The connector at https://dropthehassle.com/mcp with no token cannot do this update. It always starts a new site and returns a new claim link. Do not commit .dropthehassle.json or any token.

Add your own domain

When it takes off, add a .com without untangling a subdomain. No DNS records to edit: the domain lives with the site.

• Buy it here. A .com is EUR 19 a year including VAT in the EU, or USD 19 elsewhere, the same every year.
• Already own one. Add one A record at your registrar, to the address shown on your screen.

Claude can search for a free name. It can never pay. The checkout is your click. Building it for a client is a separate step: hand them the domain after you are paid your own way.

Publish your site for free

Keep secrets out of the environment

Environment variables in Claude Code on the web can be read by anyone who uses that environment. Do not store a DropTheHassle token there. The zero-account route needs no token at all.

Questions

Why does npx work but the deploy fail in Claude Code on the web?

The default Trusted network allows registry.npmjs.org and does not list dropthehassle.com. Add dropthehassle.com under Custom network access, or use a connector. Anthropic's docs say a connector you enable on a session does not go through the sandbox network.

Do I need a DropTheHassle account to deploy from a cloud session?

No. The command and the connector both work without an account and return a live yourname.dropthehassle.app link with HTTPS, plus a claim link. Before you claim it, the upload can be at most 25 MB.

What happens if I don't claim the site?

The claim link works for 7 days. After that an unclaimed site is removed.

Why did a second session create a new site?

Cloud sessions start on a fresh machine, so .dropthehassle.json is gone. Without that file, npx dropthehassle deploy creates a new site. The CLI has no flag for a token plus a site name. Claim the first site, then update it while signed in: drop the folder on that site, use the dashboard code with --code, or publish with your account token and the site id from list_sites.

Can Claude buy the domain for me?

No. Claude can search for a free name, but paying is always your click. A .com is EUR 19 a year including VAT in the EU, or USD 19 elsewhere, the same every year.

Should I switch the environment to Full network access?

Full allows any domain, so the deploy works, and it opens the session to every site. Custom access with dropthehassle.com plus the default package-manager list is the smaller change.

How large can the first upload be?

25 MB before you claim the site, on both the connector and the command. After you claim it, a signed-in update can be 100 MB.