32dots HEIDELBERG AI
Curriculum › Lovable course › lovable-04
Session 4 easy

Edit visually + recover (Try to Fix / revert)

LESSONLesson 4 · ~15 min

🎯Goal. Style cheaply with the preview toolbar, and recover cleanly when a change goes wrong.

  1. 1Use the preview toolbar: pick a mode, point at an element, and describe the change — cheaper and more precise than re-prompting layout in chat. Inline text edits are free (up to 100/day); select and annotate modes use credits.
  2. 2If a change breaks something, click Try to Fix — Lovable scans the logs, finds the error, and attempts a fix. If a try or two doesn't clear it, stop repeating it and switch approach (plan the change, or revert) rather than digging the hole deeper.
  3. 3If it's still wrong, revert to a previous version from the version history — but remember the DB-revert caveat from Lesson 2.
A Lovable chat message's menu showing Restore and the credits it used
Every message's ··· menu has Restore — roll the whole project back to that version. It also shows the credits used for that step. Source: lovable.dev

✓You'll see. Targeted visual edits applied, and a broken state recovered via Try-to-Fix or a version revert.

💳Cost. Inline text edits are free; select/annotate toolbar modes and chat fixes use credits. Reverting is free.

💡Takeaway. Know your recovery moves — Try-to-Fix, then revert — so you never get stuck pushing a broken build forward.