01The step Claude Code leaves out
New to the set? The pillar page holds the full pipeline.
Claude Code works in your terminal, on your files, so a website it builds is already on your disk and already in git. What it never does is serve anything to the public, because serving was not in its toolset and no prompt changes that. The deploy is therefore not really a Claude Code problem. It is a hosting decision: give the repository a remote that deploys on push, and the last command of every task becomes the act of publishing.
The same loop carries over to Codex CLI and Cursor almost word for word, which is the point of building on git in the first place.
02The loop from task to live
Connect the repository
Signup creates the repository in your GitHub account and attaches hosting. Claude Code adds it as a remote like any other.
Build the site as normal
It plans, edits files, runs the build and fixes its own errors. Nothing about that changes.
Commit and push
The deploy follows the push. The host validates the static build and serves the release over HTTPS.
Break something? Restore
Every release is kept. The portal puts the last good one back in one click.
03Source or built output
If the project is plain HTML, CSS and JavaScript, the repository holds exactly what visitors receive. If it is a framework project, the browser never sees the source; it sees the built output. Have Claude Code run the build and commit that output directory, so the deployed site matches what you previewed locally. This is the one judgement call in the whole setup, and any host would force the same decision.
When the choice is unclear, the test is cheap: push, open the live address, and compare it against localhost. Differences point at whatever the browser was getting from your machine instead of from the repository.
04Where this setup can disappoint
Two limits to know before you start. First, static hosting will not run server-side code: there is no application process to query a database and no inbox to receive mail. The contact-form endpoint is the one dynamic piece included, and everything else on the site must work client-side. Second, Claude Code cannot see the hosting portal. Deploys, rollbacks, domains and billing are operated by you, from the portal, because account-side keys should not sit inside an agent with shell access.
If you wanted an agent that also operates the hosting account, that is a different product with a different risk profile, and this one is not it.
05Questions from the terminal
Does Claude Code need credentials from LoomWeb?
Nothing is issued to the agent at all. It pushes with the GitHub access it already has, and LoomWeb never sees your GitHub password.
Can Claude Code fix a broken deploy?
It can write the fix and push it. The faster move is usually the one-click rollback while it works.
What about the artifact version from the chat?
That flow is covered in the Claude hosting guide. This page is about the terminal agent working in your repository.
Will the deploy run my test suite?
The build is validated as a clean static site and nothing more. Tests are the agent's job before the push.
Hosting price after the trial?
No charge for fourteen days and nothing billed at signup. After that it is $39 a month, and cancelling is a two-click portal job. The code outlives the hosting either way.
Build it with your AI. Host it here.
Deploys on every push, from Australia, with nothing to maintain.