See when you have unpublished changes

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want See when you have unpublished changes working in a real project rather than a sandbox.

   Set up See when you have unpublished changes in this project — get notifications for unpublished project updates. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Notice unsaved edits before accidentally publishing over them

   The record lists this as one of the jobs See when you have unpublished changes is meant for, so it is a fair first test of whether it fits your app.

   In this project, use See when you have unpublished changes for notice unsaved edits before accidentally publishing over them. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   See when you have unpublished changes is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses See when you have unpublished changes before I publish. Check visual change notifications and simplifies project updates, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Know at a glance whether the live app matches the latest build

   A second job the record lists for See when you have unpublished changes, useful once the first path works.

   Extend this project so See when you have unpublished changes also covers know at a glance whether the live app matches the latest build. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is See when you have unpublished changes?

  See when you have unpublished changes is Lovable's Editor feature: Get notifications for unpublished project updates. The Publish button now provides visual cues indicating pending changes, enhancing the editing experience in Lovable and reminding users of their latest unsaved work, streamlining the publishing process.

• Is See when you have unpublished changes GA or in beta?

  See when you have unpublished changes is generally available (GA) on Lovable.

• What Lovable plan includes See when you have unpublished changes?

  See when you have unpublished changes is available on all Lovable plans.

• When did See when you have unpublished changes launch?

  See when you have unpublished changes launched on Jun 16, 2026.

• Improved sharing linksSame category · Jun 2026
• A refreshed color paletteSame category, also GA · Jun 2026
• SVG previews in chatSame category, also GA · Jun 2026