Site · Insites AI
History, Previews and Revert
Last updated 18 November 2026
Preview, confirm and revert changes the assistant proposes.
How a change happens
Insites AI is pre-release. This page was written against the build of 31 October 2026 and will be revised at release.
The assistant never writes on its own. Every change to a page, partial, layout or record goes through the same five steps.
- You ask. For example Rewrite the About page intro to sound warmer or Mark the Terracotta Planter as back in stock with 12 units.
- It reads first. It reads the current page or record, and the Insites Logic Engine rules for that kind of file, so the change follows the platform's conventions and your site's own structure.
- It proposes. A card shows a plain summary and a preview. For a file, green lines are added and red lines removed. A new page is shown on a draft page before it exists. Nothing has been written yet.
- You confirm or reject. Click Confirm to apply it as yourself, or Reject to drop it. A proposal must be confirmed within ten minutes, or it expires and you need to ask again.
- The page is checked. After a page change is applied, the site loads the page once. If the page shows an error, the change is put back automatically.
Only editors and owners can confirm a change. A confirmed change costs 3 credits; a change to many records at once costs 3 credits plus 1 for every 50 rows, at most 20. The assistant changes at most 500 rows in one bulk edit.
The History page
Go to AI > History (#/ai/history). The page has two tabs.
Changes
Every change the assistant proposed, newest first, including changes made by automations. Columns:
| Column | Shows |
|---|---|
| When | When it was proposed |
| Type | Page, partial, layout, record, build or another kind of change |
| Module | The module the change belongs to |
| Change | A plain summary |
| Status | Proposed, Applied, Reverted, Declined, Refused or Expired |
| Credits | What the applied change cost |
| Administrator | Who asked |
Filter by date (last 7, 30 or 90 days, or a custom range), status, type, administrator and module. The list shows the newest 1,000 changes in the period.
Open a row to see the code difference or the records before and after. From there you can View the page, Open conversation, or Revert.
Conversations
Owners also see a list of conversations visitors had with the site assistant on your public site, marked Site visitor. See Site Assistant.
Revert a change
- Go to AI > History and find the change. Filter by status Applied to narrow the list.
- Open the row and check the before and after.
- Click Revert. What was there before is restored. If the assistant created the page, Revert deletes it.
You can also click Revert on the proposal card in the conversation. A change belongs to the administrator who made it, so only they can revert it or open its conversation. A page or form build reverts as one unit: every file it wrote is removed, newest first.
Revert does not need Git. The content before the change is stored with the change itself.
If your team deploys from a repository
An applied change is written straight to the site, the same way as an edit in the admin. It does not reach your repository. Pull the change before your next deploy, or the deploy will overwrite it. Owners can turn on Write a commit message for every applied change under AI > Configuration > General, so each change carries a ready commit message with the question, who asked and the model.