An AI that edits your site, built into the app.

Ask for a change in plain words

Open a project, open the chat, and write what you want. It reads the files in that folder and edits them. Things people ask for:

• Make the heading bigger and the button green.
• Add a pricing page with three plans.
• The phone number changed. Fix it everywhere.
• Put the photo on the left and the text on the right.

One request can touch several files. It opens what it needs and keeps working for up to twelve steps before it answers, so "fix it everywhere" is one message and not four.

It edits your real folder

The same folder your editor opens and the same one Publish sends. Nothing is uploaded to be edited, and no copy is made somewhere else first.

When it finishes, the project lists what changed since the last publish, file by file. Press Start to see the site on your own computer, then publish when it looks right.

Watch it work, or go and do something else

The chat names each file as it writes it, so you can follow along instead of waiting at a spinner.

You can also close the window. The app keeps the turn running and shows it still working when you come back. Edits are saved as they are made, so a turn that stops halfway leaves the finished work in place.

Publish without leaving the chat

Type /deploy. The app publishes the project with the same checks and to the same address as the button, then says what happened and gives you the link.

Type /model to see what the AI is running on today.

Ask it what went wrong

Every project keeps its own log: what ran, what was published, and the output of a build that failed. When something breaks, the Logs tab has an Explain this button. It hands the last two hundred lines to the AI and asks what happened, in the same chat as everything else, so the answer arrives in plain words instead of a wall of npm.

Standing instructions, written once

Set them in the AI section and every request carries them: your name, your colours, how you want pages written, anything you would otherwise repeat in each chat. New sites are built with them too.

A whole site from one sentence

In the new project form, write what the site is for and pick ours as the builder. It makes the folder and writes the first version, naming each file as it goes. After that it is a project like any other: preview it, publish it, ask for changes.

One project, several conversations

Each project keeps its own chats. What you asked on Tuesday stays in Tuesday's chat, so this week's question does not drag last week's along with it. Start a new one whenever the subject changes. Deleting one asks first, and never touches your files.

What it will not do

• No terminal. Its only tool is a file editor. It cannot run commands, install packages or start a server.
• No leaving the folder. Every path it asks for is checked against the project folder, and anything outside it is refused.
• No keys in files. It is told not to write them, and the check before every publish stops the upload if one gets in anyway.
• No rebuilding your project into something else. A site that is plain HTML, CSS and JavaScript stays that way. It will not add a framework or a build step you did not ask for.
• One turn at a time. An account runs one request at a time, so a second window cannot spend your balance twice over.

Where your work stays

The files stay in your folder. The conversation is saved beside the project on your own computer rather than on our server.

What you need, and what it costs

An account. That is an email address and a code we send you, with no password to invent and no browser trip. Nothing else to install: the AI is part of the app you already downloaded.

Everything else in the app is free while it is in beta. This part costs money, because each answer costs us to run. It works off a balance in dollars rather than credits or tokens, so the number on your profile means what it says. New accounts start with a dollar from us, which is enough to try it on something real. Every charge is listed on your profile, next to the balance it came out of.

Prefer your own tool?

Use it. Claude Code, Cursor and Codex all work here, the app can start Claude Code or Codex in the right folder, and it writes a /deploy command into the project so they can publish for you. Ours is for the changes that are too small to open a terminal for.