Hand My Site to My Coding Agent

01What a handover actually is

People say hand my site to my agent and mean three different things: let it edit the files, let it publish, or let it run the whole thing. Only the first two are real. An agent works in a repository; it has no account, no browser login and no credit card. So the handover is: get the site's files into a repository your agent can reach, attach that repository to hosting, and keep the account-side keys in your name. The pillar page explains the destination; this one is the move itself.

02The handover, in order

Get the current site files: export from the builder, clone from the old host, or collect from the old developer Start the hosting trial; the repository it creates sits in your own GitHub account Commit the files as the first release and push, so there is an immediate baseline Click through the live copy against the original before changing anything Then let the agent work, one reviewed change at a time

03The site that is not a repository yet

Many sites that want an agent are still WordPress builds, folders on an old host, or a builder export. Everything the browser displays can become static files; the parts that cannot, usually plugins doing server work, need a decision before the move rather than after. For a WordPress site this is a migration with one honest fork: rebuild the pages as static files, or stay where you are with the maintenance that comes with them. Leaving WordPress without losing content covers the first road, and the static comparison helps with the fork itself.

04The keys that do not hand over

Even after a clean handover, some things stay yours on purpose. The GitHub connection is granted through OAuth with scoped access and can be revoked from GitHub at any time; your GitHub password is never in the agent's hands or ours. Billing sits in the portal, with the card held by a tokenised payment page rather than on our servers. Rollback and domain changes are portal actions. If the agent could reach those, so could anything that compromised it, and that is precisely the access you do not want to give a piece of software with shell access. Once the site is live in its new home, the first-week guide takes over.

05Handover questions

Can the agent deploy without me?

Yes, every push deploys. If you want a gate, branches and merges put a human click between its work and the live site.

My old developer holds the repo. Now what?

Get repository access transferred first; a handover without it is just a wish. A host can only deploy what it is pointed at.

Will the site look identical after moving?

If the files are static and complete, yes. Claims of pixel-perfection are settled by the baseline check, not by promises.

What does the move cost?

The trial covers the first fourteen days, then $39 a month. Whatever you decide afterwards, the repository and its history never leave your GitHub account.

Build it with your AI. Host it here.

Deploys on every push, from Australia, with nothing to maintain.

Start free