Skip to content
Docs
    Menu

    Build with AI

    AI sessions: versions, Save and Reject

    How the AI's changes are grouped into a session of versions you can step through, and what Save and Reject do.

    Everything the AI changes lands on your site right away, so you can see it on the canvas. Nothing is final until you decide. The changes are grouped into an AI session.

    When a session starts

    A session starts when you send your first message. The session bar appears just above the prompt box. It shows AI Session, the version controls, and the buttons to end the session.

    Versions

    Each request that changes your site becomes a new version. Edits you make yourself on the canvas during a session become versions too.

    • Click ‹ (Previous version) and › (Next version) to step through them. The canvas changes to show that version.
    • The counter shows where you are, for example 2 / 4. Original is your site as it was before the session.
    • Click the counter to jump to any version. The list shows Original, v1, v2 and so on, with how many files and CMS changes each one made.

    If you step back to an earlier version and then send a new request, the AI builds on the version you're looking at. The list marks that version as based on v1 (or whichever version it started from), so you can still find the versions you stepped away from.

    Save

    Save keeps your site as it is on the canvas and ends the session. The chat clears and the next message starts a new session.

    Reject

    Reject puts your whole site back the way it was before the session started. It asks first:

    Discard this session's work? Rejecting permanently discards all changes from this session — every version and any pending edits. This can't be undone.

    Click Discard & reject to confirm, or Keep working to go back.

    Reject also undoes CMS changes made during the session: collections and items the AI created or edited, and items you deleted from a delete card.

    End Session

    If a session hasn't changed anything (for example, you only asked questions), the bar shows End Session instead of Save and Reject.

    While the AI is working

    Save, Reject and the version list are hidden or unavailable while the AI works. They come back when it finishes (Available when the AI finishes editing).

    Why there's no accept or reject for each request

    Requests build on each other. The third request often changes something the second one added, so keeping one and throwing away another rarely gives a working site. Instead:

    • To change direction, send another message.
    • To go back, step back to an earlier version and continue from there.
    • To throw everything away, use Reject.

    Why you Save before publishing

    You can't publish while a session is open. The Publish panel shows Publishing locked — accept or reject AI changes first. with a Review AI changes link. This makes sure what goes live is something you chose to keep. Click Save (or Reject), then publish.

    If a session is interrupted

    If the session bar says Session interrupted — accept current state or reject to restore, the session lost track of its versions. Save keeps your site as it is now. Reject restores it to before the session.

    Related