Troubleshooting Updated about 1 hour ago 3 min read

The AI says connected, but my live app has not changed

When the assistant says something is "connected", "working", or "done", that's your preview. Your live site only changes when you hit Publish.

You asked the AI to build or fix something. It replied that it's done, connected, or all set. But when you open your real app, nothing changed. Here's why — and the one-click fix.

The short version

Two versions of your app run at once: a preview (what you see in the editor) and a live copy (what your real users see). The AI works in the preview. When it says a change is done, connected, or working, it's describing the preview — not your live site.

Your live site only updates when you click Publish. The AI can't do that step for you. That's on purpose — you decide when your users see a change.

So the AI said it's done and my live app is updated are two different things. The gap between them is one button.

The fix: hit Publish

  1. In the top right of the editor, click Publish.
  2. A window opens showing what's changing.
  3. Click the main Publish button (it says Publish site the first time, Publish changes after that).

About 5 seconds later, your live site updates. Refresh your real app and you'll see it.

Why the AI can't just publish for you

There's no publish you can ask the AI to do in chat — publishing is a deliberate, manual click. This keeps you in control: you can experiment freely in preview, break things, roll back, and none of it touches your real users until you decide to push it live. If you ask the AI to publish it or make it live, the best it can do is point you to the button — so head there yourself.

I did publish, and it's STILL not updated

Check these, in order:

  1. Did the publish actually finish? Open Publish again. If it shows changes waiting to go out, they didn't publish yet — click the button and wait for the confirmation.
  2. Your browser is showing a cached copy. Hard-refresh your live app: Cmd-Shift-R (Mac) or Ctrl-F5 (Windows). Or open your live address in an incognito / private window — that always shows the true live version, with no editor frame and no cached data.
  3. It's a connect an account or saved-key feature. Some things (like connecting an outside service, or a saved key) also need a publish to reach your live app. Republish, then hard-refresh.

Want proof it's actually live?

The surest test: open your real app address (not the preview-... one) in an incognito window. That's exactly what your users see. If your change is there, you're live. If it's not, you haven't published the latest version yet — go hit Publish.

If you're on a custom domain and the live site still lags after publishing and a hard-refresh, connecting your own domain covers the DNS delays that can cause it.

Was this helpful?

Thanks for the signal — it helps us improve the docs.

More in Troubleshooting

When things go wrong

The build failed, the preview won't load, the deploy is stuck. Here's the short list of fixes that work most of the time.

Still need help?

If this didn't answer your question, our team is one click away.

Sign in to open a ticket Back to help center