Reviewing the change
When Kaeru finishes, it tells you what it did and shows you the result before anything is final.
Step 4 of 5 · about two minutes
Reading what changed, and taking back anything you do not want.
When Kaeru finishes a request, it says what it did in plain words and lists the files it touched. The frame below is opened on that moment, with the first changed file already open beside the summary.
Looking it over
Read the summary
One short paragraph: what changed, and what did not. In the frame it ends with the checks still passing, which is Kaeru telling you it did not quietly break something else.
Look at the change itself
Green lines were added, red lines were taken away. You do not have to read the code to use this — the line under each file name says what that file was for, in words.
See it running
The Preview tab shows your site with the change already in it, so you are looking at the real result rather than a description of one.
Keep it, or take it back
Looks right keeps the file. Undo this one puts it back exactly as it was, and only that file — the rest of the work stays. You can also just say "undo that" in the conversation.
Read more
Undo anything covers stepping back through a change, or going all the way back to an older saved version.
What's next
Happy with the result? Publishing it covers making it official.