Your project
Asking for changes
You do not start over to fix a page or a level. Ask in the same project. A short change costs less than building it again.
Say what is wrong
“Make the menu easier to read on a phone” or “the jump is too short” is enough. Name the part. The preview is how you tell if the new version is right.
If the preview did not catch up, press Reload in the preview toolbar before you send the same request again. A second copy of the same message, while the first is still running, does not speed it up.
One project keeps the history of the work
The current site or game is what the next message edits. You do not need to paste the original prompt every time.
A new chat on that project still edits the same thing. It just does not show the older messages. Prefer the chat you were already in when you are mid-change.
The live link stays put
Edits stay in the project until you publish again. People on the public link keep seeing the last version you published. That is what you want while you try a new headline or a new level.
Publish when the new version is the one they should see. You do not get a second link for every edit. The same address updates.
A new idea is a new project
A second website, or a game when this project is a website, starts as its own project from the dashboard. The credits for that build come from the same account, as a separate spend.
Deleting the old project is optional. Delete only when you are sure. It cannot be undone.
