Automatio

Build and publish

Have the agent build a site or app, then put it online.

Ask for what you want: "build me a landing page for my bakery". The agent builds it in a cloud sandbox and a project panel opens beside the chat.

The project panel

Preview shows the running project, and Code shows its files. A project in a sandbox also has Terminal, Storage, API and Usage, and one with a database has Database.

The action bar holds Environment variables, Download, Push to GitHub and Publish.

To go back, open the version list in the panel's header, and press Restore this version.

Publishing

Where Publish is: the action bar of the project panel, which opens beside the chat when the agent builds a project (a closed panel is opened with the small window icon in the top bar of the chat, tooltip "Open project panel" or "Open preview"). It opens the "Publish Your Website" dialog: the site goes live at <name>.automatio.site, and a staging link can be tested first. The dialog's "Custom Domain" section puts your own domain on the site (it needs a paid plan; on the free plan the section is shown locked) and shows the DNS records to set. Publish is off for a project that only holds code. The Sites page in the sidebar lists the sites already published; it does not publish or add a domain.

Pick Staging first to test at a private link that search engines do not index, or Straight to production. Once a site is live, the same dialog shows which version it serves, named as in the version list. When you have a newer version, its buttons name it, for example "Publish v12" and "Test v12 on staging first". If the staging copy already holds that version, Publish puts the build you checked there online in seconds, without building it again. When the site already serves your latest version, the dialog says Production is up to date and offers Republish, which builds the same version again so changed settings take effect, and, when the staging copy is behind, a button such as "Update staging to v12". Delete site is always there.

In the version list, the version your published site serves is marked "(live)". A dot on Publish means your latest version is not published yet. Deploy History in the same dialog lists every publish, and Rollback puts an earlier version back online while its files are still kept.

On a paid plan you can turn off the Built with Automatio badge. On the free plan it stays on.

Copies and forks

A chat that built a project has a fork button in its top bar, "Fork or clone this chat". Its menu has:

  • Clone conversation: a new chat on the same project. Both chats change the same code, and each sees what the other did.
  • Fork project: a new chat with a project of its own, which opens in a new tab. The code and the database tables are copied, and the rows too if you own the project and leave Copy the current data too ticked.
  • Transfer project… hands the project to someone else, and Send a copy… gives them a copy while you keep yours. Only the owner sees these two.

To branch from an earlier point, use the fork icon under a message, "Fork from here (new chat + new sandbox at this point)": a new chat and a new project with the code as it was at that message.

When a fork made with Fork project is ready, Merge brings its changes into the project it came from. Merge, then review in chat does the same and opens that project's chat with a review message written for you, which nothing sends until you press Send; when the two changed the same lines, the message asks the agent to resolve that instead. The project it came from must be connected to GitHub, and Merge pushes both sides for you. A panel then says where the code went, that the fork stayed as it was, and anything that did not come across, such as an environment variable.

Your sites

Sites in the sidebar lists what you published, with each site's status and a View Chat link.

A site with a database shows Database on its card, which opens the database. It turns amber when Cloudflare turned some of the site's database requests away in the last day: that happens when the database does too much work in a short time, and the pages that read it fail while it does. Database health, at the top of the Database tab, says whether any requests were turned away in the last week; Show details adds a box per day, how much work the database did in the last day, and the queries that read the most rows. The first time it happens on a day, you get a notification. In the project panel, Fix with AI asks the agent to make those queries lighter.

Deployments is a different page, for apps on your own dedicated servers.

Cost

How many sites you can publish, and what a further one costs, is in Limits.

If a site's monthly fee cannot be paid, it gets a grace period of 14 days, is then suspended, and is deleted 60 days after that.

Saved keys

A project reads its own values from Environment variables. Do not type a password or key into the chat, because everything in a chat is saved. See Integrations.