Your unsaved work now survives an app update

When we ship a new build, Playcode offers to reload so you get it. That reload used to happen immediately - and if you had a browser project you hadn't saved yet, it went with the page.

Now the reload saves first. If you're signed in, your project is written to your account before anything else happens, and edits still syncing get a moment to land. If it can't be saved - you're signed out, for instance - Playcode asks before reloading instead of deciding for you.

Two related gaps closed at the same time:

• Other tabs. Reloading in one tab used to reload the rest instantly. A tab holding unsaved work now keeps it and waits for you.
• Closing or refreshing the page. The browser's "leave site?" warning now appears for an unsaved project on any exit, not only when moving between pages inside Playcode.

Projects created with the AI builder and Cloud projects were never affected - those save to your account continuously.