Editing a website with AI

On any website's detail page, the Edit with AI card lets you jump into a dedicated editor: describe a change in plain English in a real chat thread, review a live preview and diff, and approve it to go live. A separate History tab covers the site's entire edit history, so you can publish any past version to production whenever you want.

Go to https://app.trustpager.com/growth/websites and open any website record. Below the Deployment band, the Edit with AI card shows the current status and an Open AI Editor button. Click it to open the full editor page.

Who can use it

Anyone who can view the site can open the editor page. Making changes, approving, discarding, reverting, and publishing a version all require write access to the site. This is self-serve for the workspace that owns the site, not admin-only.

The Chat tab

Type an instruction into the box at the bottom and press Enter (or Shift+Enter for a new line) to send it. For example: "Change the hero headline to say 'Family owned since 2004', and make the button say Call us instead of Get started."

Every instruction you've sent stays visible in the thread, along with what happened: while an edit is running, a "thinking" bubble shows "Queued — starting shortly…" and then "Applying your change and building a preview…" (normally 30-60 seconds); once it's done, the reply shows how many files changed, and you can click any file to expand a real diff, added lines in green and removed lines in red. If an edit fails, the reply shows a plain-English message and a Clear and try again button. You can keep sending follow-up instructions to keep iterating on the same preview rather than starting over.

A status pill in the toolbar tracks the latest edit: Idle, Queued, Editing, Preview ready, or Edit failed. The main panel is a live embedded preview that updates automatically as new builds land, no separate tab required (a fallback link appears if a preview doesn't load).

Once a preview is ready, the toolbar shows:

• Approve — go live merges the change into production.
• Discard throws the pending change away with no impact on the live site.

The History tab

History lists every edit ever made to the site, not just the current session, newest first, each showing the instruction that produced it and when. Two badges tell you where an entry stands: Live now means production exactly matches that version today; Current preview means it's what the in-progress staging preview currently reflects (only shown while a preview is open).

Two actions are available per entry:

• Publish this version makes that exact version live on production right now, as a new forward-only change (nothing is ever rewritten or lost) — this works on any past edit, including ones from long-finished, already-approved sessions, not just the one you're currently iterating on. It's blocked while an edit is running or an unapproved preview is still open; approve or discard that first.
• Revert to here (only shown while a preview is currently open) moves the in-progress preview back to that point, discarding anything applied after it. This only affects the preview, never the live site, so it's always safe to try.

What the AI can and can't touch

The AI edits the site's actual content and code, but never touches build or install configuration files (package.json, tsconfig.json, the Cloudflare Wrangler config). That's a deliberate safety boundary that keeps every change safe to preview automatically, not a limitation you need to route around.

One edit at a time

Only one edit can be in progress on a site at once. Starting a second edit while one is running, or trying to approve/discard/revert/publish while one is still applying, is rejected with a plain message asking you to wait for it to finish. None of these are silent queueing.