Visual edits

Change it in the preview

Mapped text, styles, and uploaded images change where you click. No model is called, so nothing is charged.

What it is

Asking a model to change one headline is a poor trade. Clicking it is faster and costs nothing.

The zero is structural, not a promise. This path has no model dependency at all — it locates the node in your source, replaces the string, and rebuilds.

The change lands in the source file. Nothing is painted on top of the preview.

How to use it

Step 1. Turn on visual edits

Editable regions are marked in the preview once the mode is on.

Step 2. Click what you want to change

Text is edited in place. Styles come from a list. Uploaded images can be swapped.

Step 3. The preview rebuilds

Your change is built into the app, and a restore point is written for you.

What we measured

12/12Text edits applied (3 real apps)
15/15Style edits applied
27/27Builds still sound after the edit
0Credits per edit

Measured on three generated apps against a 95% bar.

What it does not do

Data-driven text is out of reach

A product name that comes from the database does not change here. Change the row, or ask in chat.

So are conditional regions

Text that only appears when someone is signed in is left alone.

Ambiguity means no edit

Breaking a build is worse than declining. When the node cannot be resolved exactly, the reason is shown and you are pointed to chat or to the code editor.

Pages are not added here

Creating or removing a page is a chat request.