How the chat works

Every change in Automo Build begins with a message. Understanding the rhythm of the chat makes you much faster.

One message, one intention

The best messages ask for one thing:

• "Add a search box above the list that filters by name."
• "Make the header stay at the top when I scroll."
• "Show a friendly message instead of an error when the form is empty."

The worst messages bundle five unrelated wishes. If you would not describe them in one sentence to a colleague, send them separately.

What the builder does with your message

Broadly, every message goes through the same steps:

1. It reads the relevant parts of your project.
2. It plans the change, and for bigger work shows you the plan.
3. It edits code and, where needed, the database.
4. It checks the result and summarises what changed.

The hand-offs are visible, so you can see what is happening rather than guess.

Referring to what you can see

You do not need to describe the screen from scratch. Point at it:

• "On the checkout page, move the promo code field above the total."
• "In the admin table, add a column for the customer's phone number."
• "The button in the empty state should say 'Add your first client'."

A screenshot is often the fastest way to explain a visual problem.

When the builder asks a question

Sometimes it needs a decision it should not make for you: whether old records should be kept, or who is allowed to delete. Answer in a sentence. If you are not sure, say "use your judgement" and it will pick a sensible default and explain it.

When you want to start over

You can ask it to undo the last change, go back to an earlier version, or do the opposite of what you just did. See Versions and restore.