Edits, Versions and Preview
How do I go back to an earlier version if something goes wrong?
Every time the AI changes something, the previous state is saved automatically, so you can open an older version, see it in the preview first, and press "Go back to this version" to return to it. The last 20 versions are kept. That means you can experiment freely without worrying about breaking anything.
The preview on the right is the real thing
Whatever you are building shows up on the right straight away. On mobile, tap the "preview" tab to see it. It is not a picture, it is the real running site. Press a button and it works.
Three tabs
- chat: this is where you tell the AI what you want.
- preview: see the site live.
- code: see all the files (index.html, style.css and so on), and copy them too.
Going back to an earlier version
Every time the AI changes something, the previous state is saved on its own. Open "earlier versions" and you get a list: "View" on any of them shows that state in the preview first, and "Go back to this version" takes you back to it. In the chat, too, every build has a "Go back to this version" button under it: it shows the state right after that build in the preview, marked "Viewing an earlier state" at the top, and only goes back when you press "Go back to this version" there. The last 20 versions are kept.
So there is nothing to fear about experimenting. Change whatever you like, and come back if you do not like it.
If the site is published, restoring an earlier version takes the LIVE site back to it too, with no separate publish. And whenever you edit after the last publish, a small "Edits not published yet" badge appears at the top of the builder; one click updates the live site.
App rules: write it once, it is followed every time
Under the text box there is a "memory and rules" button. Whatever you write in the rules box, the AI will follow it every time it builds. For example: "all headings should be dark green", "buttons should be rounded", "keep the language simple, less English". No need to remind it every time, writing it once is enough.
See what changed with your own eyes
After every build a "changed in this build" chip appears below the chat: which file got how many lines added (+) and how many removed (−). Press the chip and the green and red diff opens up, so you can see exactly which line changed. You do not have to trust the AI blindly.
Small changes, in the blink of an eye
For a small edit like "change the price to 20 BDT" the AI no longer rewrites the whole file, it only changes the line that needs changing. So small jobs are much faster and use less Token too. For big changes it does rewrite the whole file, because that is the safe way.
And when only TEXT or a picture needs to change, you do not need the AI at all: open the Site manage chip above the message box and go to "Text and pictures". Every heading, price and image on the page is its own field there, so you change just the one you mean, at zero Token cost. If the site is published, saving puts the change on the live site.
Two more buttons sit right above the preview. Press Edit text, tap the words you want to change in the preview, type, and press Enter to save; no AI and no Token. If some text cannot be changed directly, it drops into the box below and the AI changes it instead. Press Point at it, tap the thing you mean in the preview (on a phone the first tap marks it and the second picks it), then write in the box what should change; the AI changes exactly that thing.
The next job while a build runs, and questions only
You do not have to sit and wait while a build runs. Write the next thing and press "Queue it"; it waits under "Up next" and goes by itself when the build finishes. Changed your mind? "Remove from queue". If the build gets stuck, the queued jobs are dropped, so one mistake does not set off more builds.
When you only want to know something about the app, such as "where does the form go when it is sent?", pick "Ask" above the writing box (on a phone, the chip in the row under the box). The AI answers but touches no file; it is metered like chat.
If you want to look at the code
The "code" tab shows all the files. It is great for learning, and you can also ask the AI "what is section 3 of this file doing".
The code is yours. You can copy all of it and keep it on your own computer, push it to GitHub, whatever you like.
Share link
Every app has a viewing link (something like banglacodes.app/p/...), and pressing the "Share" button copies it. Whoever you send the link to can open it in a browser and look at it. No account needed, completely free. This link is for showing your work; for the real address you give customers, press "Go live, free" and the site goes live at an address in your own name (apnar-site.banglacodes.app).
Deleting and bringing back
On the Builder page every card has "Open", and its "More" menu holds "Share link", "Duplicate" (a copy of the app, with the original left as it is) and "Delete". Hitting the wrong card at two in the morning is no longer a disaster. A deleted app leaves your list at once and its live link stops working, but it is kept inside for 30 days.
- Within those 30 days, open the "deleted apps" part at the bottom of the Builder page and press restore. All of it comes back: the files, the newest 5 versions, the pages, the messages sitting in the inbox, the chats.
- If somebody else took that name in the meantime, the restored app gets a slightly different link, and you are told so as it comes back.
- A custom domain is released the moment you delete, so after a restore you add it and verify it once more.
After 30 days it really is gone for good. One more thing is worth saying separately: on a free account an app moves itself into this same list 60 days after the last edit, but since that was not you deleting it, it can be brought back for a year rather than 30 days. Restoring it starts the 60 days over, and an email goes out before that day arrives. On Pro (which any pack makes you) your apps stay for life. A published site is outside this count: once it is live it is never swept.
Beginner questions
What if the AI changes the very thing that was good?
Press the go-back button that appears after a change and the old state returns. The last 20 states are always kept.
Does a tiny change rebuild everything?
No. Only what you asked for changes, the rest stays untouched. It even shows which files moved.
A single word is misspelt; do I have to ask the AI for that too?
No. Press "Edit text" above the preview, tap the wrong word, fix it, then press Enter. It saves at once, with no AI and no Token.
How do I compare two versions?
The history button lists every version with its date. "View" on any of them shows it in the preview before you go back, and even after you go back, if you are not convinced, jump forward again, nothing is lost.
The same thing is available from the manage screen: the Text and images tab ends with Go back to an earlier version, holding the last twenty. See Manage your site.