Creator Preview Changes view with Inspector toolbar and unpublished draft
Changes view

Appifio Creator · Lesson H04 · Advanced

AI Diff, History
& DOM Search

Three tools so you control changes instead of “AI finished - hope it works”: Diff compare (✓/✗), restore points in Edit history, and find elements with DOM Search (Ctrl+Shift+F).

Learning goals: Know when to open Diff, when to use History vs Checkpoint vs Versions; find elements when Inspector is hard to click.

Prerequisites: B01 (AI Chat), C03 (Inspector), E01-E02 (Versions & Checkpoint).

UI labels: Compare changes · Add (+) · Remove (−) · Apply changes · Close · Edit history · Restore this point · DOM Search · Utilities

Previous → next: H03 → H04 → (T / K / X deep technical series)

1. Which tool?

AI just edited files → file-changes bar / Diff "Compare changes:"
→ ✓ accept · ✗ reject (hint: "Press ✓ to accept or ✗ to reject")
→ or "Apply changes" / "Close"
Undo a few Inspector/drag steps?
"Edit history""Restore this point"
Roll back project + chat to an AI milestone?
→ Checkpoint (flag on AI messages) - E02
Parallel experiments?
"Versions" · "Create new (Clone)" - E01
Can’t click an element on preview?
→ Enable "Inspector"DOM Search (Ctrl+Shift+F)

2. Glossary

Term / labelMeaning
Compare changes:Diff panel title after AI writes files
Add (+) / Remove (−)Lines added / removed in the diff
Previous / Next / Latest changeNavigate hunks in Diff
Apply changesCommit the changes you’re reviewing in Diff
Edit historyUndo points from editor actions (not a full AI session)
Current (in History)The point you’re on - not the preview “Current” button
DOM SearchModal to find Class, ID, Text, Tag, Attribute, Selector
UtilitiesPreview toolbar for sub-components (Loading, Back to top, Analytics…)

3. Steps - Diff after AI edits

  1. Send a request in "Ask AI… (Shift+Enter for new line)""Send".
  2. When AI reports file edits, open the file-changes bar or "Compare changes:" panel.
  3. Read Add (+) and Remove (−). Use Previous change / Next change / Latest change to jump hunks.
  4. Per change: to accept or to reject (matches the UI hint).
  5. When done, click "Apply changes" or "Close". Then check the "Changes" preview tab.
  6. Only when happy click toolbar "Save changes" (not the Routes “Save”).

4. Steps - Edit history

Edit History popover showing History is empty on the Inspector toolbar
Edit History
  1. Open "Edit history" (from the editor toolbar/history - common UI label History).
  2. If empty you’ll see "History is still empty" - no recorded points yet.
  3. Pick a point → "Restore this point". The active point shows "Current".
  4. To remove a milestone: "Delete" → confirm "Are you sure you want to permanently delete this history point?".

Four “go back” layers:
1) Undo / Redo (toolbar) - last editor steps.
2) Edit history (History button) - pick a recorded point → Restore this point / Delete.
3) Checkpoint - flag on AI messages (E02).
4) Versions - Clean/Clone (E01).
History ≠ Checkpoint ≠ Versions; History also doesn’t replace Diff after AI writes files.

5. Steps - DOM Search

DOM Search modal Search by Class ID Text Tag Attribute
DOM Search
  1. On View space, turn on "Inspector" first. If off, tooltip: "Turn on Element Inspector to use DOM Search".
  2. Open DOM Search (Ctrl+Shift+F) - title "DOM Search"; find by Class, ID, Text, Tag, Attribute…
  3. Type into "Enter search keyword… (Enter to search)" → Enter.
  4. See "Found N results"; browse with Previous / Next. Types: Text · Class · ID · Tag · Attribute · Selector.
  5. Click a result to select the element → edit in Inspector / ask AI.
  6. Close with "Close". Search history lives under "Search history" (separate from Edit history).

5b. Utilities (sub-components)

Utilities on the preview toolbar (tooltip: Configure Utilities (Loading, Back to top, etc.)) opens Configure extra utilities. When you click Apply to source, the system confirms then writes HTML into the pages you selected.

GroupFeatures
UIPage load effect (Spinner / Progress / Fade-in) · Back to top · floating Share · Cursor & scrollbar
TrackingCode in / end of (GA, Pixel…)
Third-party chatTawk.to / Intercom / Facebook Chat…
Pages to applyPick which HTML gets the code (e.g. Login may skip Share)

After applying, still preview and Save changes to publish. Don’t ask AI to inject scripts that duplicate Utilities already on.

6. Compared with other tools

  • VS Code / Cursor Diff: familiar ✓ hunks - Creator Diff is similar but tied to the virtual disk + preview.
  • Chrome DevTools Ctrl+F / Inspect: DOM Search is closer to DevTools, wired into Appifio Inspector.
  • Figma Version history: Creator History is narrower (action points), not full Git version control.
  • Lovable / v0: often auto-apply AI; Appifio lets you reject hunks via Diff - safer on a live site.

7. Technical limits

You can

  • Reject part of AI changes before Save changes
  • Undo recent Inspector actions
  • Find hard-to-click elements (stacked/small)

Not a replacement for

  • Full Git / PR review
  • Long-range chat+project restore (use Checkpoint/Versions)
  • DOM Search with Inspector off
  • Blocked custom-domain preview (reset domain - X series)

8. Security

  • When reviewing Diff, watch for secrets/API keys slipped into HTML - reject (✗) immediately.
  • Don’t share Diff screenshots that contain tokens/sessions.

9. Common issues

SituationFix
Diff stuck on “Loading content…”Reload preview; check connection; reopen file changes
Can’t open DOM SearchTurn on Inspector first - DOM Search only works with Inspector on
“No results for …”Change search type (Class/ID/Text); confirm you’re on Changes vs Current
History empty after a big AI editUse Checkpoint / Versions Clone - History doesn’t cover every AI write
Confused History “Current” with previewContext: History = undo point; preview = live vs draft

10. Tips

  • Golden rule: AI edits → Diff ✓/✗ → preview Changes → then Save changes.
  • Before a big prompt: Checkpoint + (optional) Clone version.
  • Search stable class/id (not marketing copy that changes) so searches stay useful.
  • Add Utilities (Loading, Back to top, Tracking) after the DOM is clean - avoid duplicate AI scripts.

11. Checklist - end of series H

  1. Have you rejected at least one hunk with ✗?
  2. Can you tell History / Checkpoint / Versions apart?
  3. Can you open DOM Search after enabling Inspector?

Next

Series T / K / X - deep glossary & technical topics

Suggested list in the master report: virtual disk, appifio_client, shards, CMS manifest, rate limit, custom domain…

Appifio Creator · User guide · H04