Concept

Your code

You own the code Willo writes for your site. How to read it on GitHub, why changes still go through Willo, how to get a copy, and what can't be imported.

Last updated Open in ClaudeOpen in ChatGPT
On this page

Every Willo site is backed by a real code repository on GitHub. The code is yours. You can read it at any time, point your own AI tools at it, and ask support for a copy to take with you.

Read access, on every plan

An admin of the business can give their own GitHub account read-only access to the repository. It costs nothing, and every plan includes it. Give an agent read access to your code has the steps; in short, Settings → AI Agents → Your code on GitHub, enter your GitHub username, and accept the invitation GitHub emails you.

The repository has two branches that matter:

  • main is your live site.
  • draft holds changes you haven't published yet, when drafting is on.

Both update as Willo works, so a fresh git pull always shows the latest.

Each admin connects their own GitHub account, one per person per business. Access ends on its own if that person stops being an admin, if the business is transferred, or if it is deleted. You can also remove it yourself from the card.

Why it is read-only

Pushes to the repository are refused, on every plan. Willo builds, checks and deploys every change, and keeps the draft, the preview and the Activity history in step with the code. A change made outside Willo would skip all of that.

So changes still go through Willo. If your own AI tool drafted a change, paste it into Willo's chat and ask Willo to apply it. Or, on Builder and up, connect the tool to Willo directly with an agent token, so it can make changes under the same rules as Willo's chat. See Connect your agent.

A downloadable copy

For a zip of your site's code, for example if you are leaving Willo, write to support@willo.ai. Read access is self-serve; a downloadable copy is the one thing support handles here.

Bringing existing code into Willo

Willo doesn't import an existing codebase: not a zip, a folder, a GitHub repository or a running app, on any plan. Willo builds and hosts fast websites and web apps on a managed backend; it is not general-purpose hosting, so a separate long-running program has nowhere to run.

What does work:

  • One or a few files. Attach a text or code file in chat, or paste it, and Willo reads it as a reference.
  • Building around a system you already run. Willo builds the site, sign-up and sign-in, the app's screens and its database, and the front end calls your existing system's API. Your system stays where it is.

Never make a private repository public to share it with Willo. It doesn't help, and it exposes your code and any secrets in its history.

Bringing an existing site's content

Moving the content of a site you have elsewhere (pages, posts, images) is a different thing: that is a migration, open to every account in Beta. Start a new business, choose the Migrate an existing site tab, and enter your site's address. Willo scans the site and shows you what it found before anything is built, then either rebuilds it exactly as it is or brings the content into a fresh design. Migrate an existing site walks through it.

Related: Give an agent read access to your code, Agent tokens, Migrate an existing site.