Bolt.new project disappeared (or chat history gone, or rollback made it worse)

Bolt.new Easy 10-30 minutes data risk Last verified Jul 17, 2026

The fix Do not keep prompting fixes; follow-up 'fix' prompts after a bad rollback have wiped projects. Your project is probably not deleted: Bolt stores projects in your StackBlitz account, so sign in at stackblitz.com with the exact account and login method you used originally, open Collections, and use 'Open in bolt.new'. Note: rollbacks never restore your Bolt or Supabase database.

Symptoms

The project is missing from the bolt.new sidebar
The project exists but the chat history is gone
A rollback left the app erroring or blank, and follow-up 'fix' prompts wiped the project
A page refresh reverted the project to an earlier state
After restoring a version, the database still reflects the newer schema and data

Why it happens

Broken session reference, not deletion

Bolt projects are stored in your StackBlitz account, not in the browser. Signing in on a different device or browser, clearing cookies, or using a different login method (GitHub vs email) than the identity that owns the project makes it look deleted.

Chat persistence bugs

Chat saving has had real bugs, with multiple user reports of chats not saving or disappearing after crashes.

Rollback excludes databases by design

Bolt's official docs state that restoring an earlier project version 'will not change your current Bolt or Supabase databases,' so code rollback and database state diverge after every restore.

How to fix it

Log in to StackBlitz with the original identityGo to stackblitz.com and sign in with the same account and login method you used when you created the project. Open Collections, find your Bolt collection, locate the project, and use 'Open in bolt.new' to restore it with its history.
Try your other login methodGitHub login and email login are separate identities even when they share an email address, and projects are tied to the specific identity that created them. If the project is missing under one method, sign out and try the other.
Restore through Version History, and bookmark good statesPrefer the Version History clock icon for restores. Preview versions before restoring, and bookmark known-good versions so you can find them again later.
Reconcile the database after any rollbackBolt's docs state that restoring an earlier project version will not change your current Bolt or Supabase databases. If the restored code expects the old schema, reverse the schema changes or reconcile the data manually before building further, or the app will error against a database it no longer matches.
Set up real backups nowConnect the project to GitHub so every state is pushed to a repository you control, and periodically download a ZIP backup. Neither depends on Bolt's session or persistence layer.
If it is truly gone, contact Bolt supportIf the project appears under no login method and there is no GitHub copy, contact Bolt support. Honest caveat: chat persistence has had genuine bugs, so a chat history lost to one of them may not be recoverable even when the project itself is.

How to prevent it

Connect every Bolt project to GitHub as soon as it exists; a repo you own is the only backup that survives account mixups.
Pick one login method (GitHub or email) and use it every time.
Bookmark known-good versions in Version History as you hit milestones.
Download a ZIP backup before risky changes.
Treat code rollback and database state as separate things; plan schema reconciliation whenever you restore.

Tools that actually fix this

Recommended because they address the failure mode above, not because of the payout. Some are affiliate links; see how we choose.

SimpleBackupsNo free tier (free trial)

Automated, scheduled backups of your database and storage so the AI's next confident refactor is survivable. Set it once and stop trusting an agent with your only copy.

Try SimpleBackups →

GitProtectFree for open source

Backup and recovery for your Git repositories, so a force-push or an agent's cleanup does not take your history with it. Free for open-source projects.

Try GitProtect →

Frequently asked questions

Did bolt.new delete my project?

Almost certainly not. Bolt projects are stored in your StackBlitz account, and the usual cause of a 'deleted' project is signing in on a different device or browser, clearing cookies, or using a different login method (GitHub vs email) than the identity that owns the project. Log in to stackblitz.com with the original account and open the project from your Bolt collection.

Does restoring a version in Bolt roll back my Supabase database?

No. Bolt's official docs state that restoring an earlier project version will not change your current Bolt or Supabase databases, so a rollback reverts code while the database keeps the newer schema and data. After any restore, reconcile the database manually if the restored code expects the old schema.

Why is my bolt.new chat history gone?

Chat persistence in bolt.new has had real bugs, with multiple user reports of chats not saving or disappearing after crashes, and the session reference can also break if you sign in under a different identity than the one that owns the project. Reopening the project from your StackBlitz collection restores whatever history was saved. A chat lost to a persistence bug may not come back.

How do I make sure I never lose a Bolt project again?

Connect the project to GitHub so every state is pushed to a repository you control, and download a ZIP backup periodically. Bookmark known-good versions in Version History so restore points are easy to find later. These backups live outside Bolt's session and persistence layer, so login mixups and chat bugs cannot take them away.

Sources

The Vibe Oops briefing

One email when something ships to production that should not have. New incidents, new error guides, no filler.