01From chat to address, without changing horses
The pitch of every AI builder is that you describe and it delivers. Delivery stops at the file boundary in most setups, which is why the pillar page exists: publishing joins the agent's abilities instead of starting a new phase of the project with new tooling. The site goes from conversation to repository to live address, and the repository is where publishing officially becomes something your agent does rather than something done to its output.
02Why neutrality is a feature, not a shrug
Agents change faster than hosts. The tool you use in March may not be the tool you use in September, and a hosting setup wired to one vendor's export format ages badly. Publishing through git is deliberately ordinary: Claude Code, Codex, Copilot, Cursor and copy-paste ChatGPT all speak it, and whichever arrives next year will too, because file-writing agents converge on git the way drivers converge on roads. Your site should outlive your editor choice, and it does when the interface is a repository.
This is also the exit plan. The hosting never holds the files; they live in your GitHub account, and any other static host can serve the same repository tomorrow.
03What each party owns in this arrangement
| Party | Owns | Cannot do |
|---|---|---|
| Your agent | Writing, committing, pushing the work | See your hosting portal, billing or rollback controls |
| You | The account, the domain decisions, the review | Hand accountability for what goes live to software, quietly |
| LoomWeb | Serving releases, certificates, history, the form endpoint | Hold your code; the repository was always yours |
| GitHub | The repository, its access controls and its history | Know or care who the deploying host is |
Every row of that table is a boundary we chose on purpose, and the deal only works while all four hold.
04Where the boundary of the claim sits
Publishing is an agent capability now; operating a business website is not. No agent watches uptime, answers the visitor whose form submission vanished, or notices that the pricing page is a year old. The hosting can take maintenance off your hands and can make every publish reversible, but the site still needs an owner who looks at it sometimes. The honest state of the art: the agent makes and ships the changes in the morning, and you read them with breakfast. Handing over an existing site has its own checklist, in the handover guide.
05Agent publishing questions
Do different agents need different setups?
One repository, one remote, one hosting connection. The agents share the repo, and the pipeline cannot tell them apart.
What if my agent prefers merge commits or rebase?
The host follows a branch, not a philosophy. History style is between you and your repository.
Is my site locked in if my agent is?
The files and history live in your GitHub account. Swap agents freely, and swap hosts by pointing a different one at the same repository.
Can an agent from another company break my site?
Any writer can push a bad change, which is why releases are versioned and rollback is one click.
Build it with your AI. Host it here.
Deploys on every push, from Australia, with nothing to maintain.