Talking to the builder
How a message becomes a change, Build versus Discuss, and queuing messages while it works.
Last updated September 17, 2026
On this page
Every message you send is a turn. The builder says what it is about to do, does it, and ends with a plain summary of what changed. The preview refreshes as it goes.
Build and Discuss
- Build changes your app. This is the default.
- Discuss talks it through and changes nothing. Use it to plan, to ask what the builder recommends, or to understand how something works.
The switch is next to the message box and is remembered per browser, so check it before an instruction.
Queuing messages
You can keep typing while a build runs. Messages wait in a queue and go out one at a time. Pause holds them, Clear removes them, and you can drag to reorder.
What works best
- One change per message.
- Point at the thing: "the Book button on the schedule page".
- Describe the outcome, not the code.
- Say what should stay as it is.
More in the documentation: Working with the builder and Writing a good brief.
Was this page helpful?
Still need help? Contact support