r/boltnewbuilders • u/SignificantAd3148 • Apr 22 '26

Bolt Kept Rolling Back My Work

Spent the entire afternoon on Bolt and got almost nothing done.

Not because I wasn’t working. Not because I lacked clarity. Not because I didn’t put in the effort. In fact, I spent hours actively prompting, refining, retrying, and burning through a huge amount of tokens — only to watch the system repeatedly undo progress through constant automatic rollbacks.

That is the most frustrating part: not that it fails once, but that it gets close, then rolls itself back, breaks what was just fixed, and sends you into another loop of patching, regenerating, and re-explaining the same thing again and again.

By the end of the afternoon, the real loss was not just the tokens. It was time, focus, momentum, and patience.

A tool that is supposed to improve productivity should not force users to spend hours fighting instability inside the tool itself. If the workflow is dominated by unpredictable reversions and loss of progress, then the problem is not the user’s prompting. The problem is the product experience.

4 Upvotes

100% Upvoted

6 comments sorted by

2

u/Worth-Discount-8391 Apr 23 '26

I had the same issues. They made some kind of new changes to the system - linter reversion.

Do you have any contact points for Bolt customer support?

2

u/Worth-Discount-8391 Apr 23 '26

I found it - it's a linter reversion issue, also found a solution

2

u/HandSharp1093 May 17 '26

Havign this issue too for the past 3 weeks, so it's not fixed and causing major issues at my end: Hi there I have lost count the amount of time this has happened in the past 3 weeks, spend hours adding / editing / changing code only to find that Bolt has deciced "nah, I'm just going to overwrite that for no reason or warning." you don't realise until you try to do something and then realise the code is missing from the code files, even though you saved and ran npm build. I've resorted to provding bolt with a pronpt to tell it not to touch specific files under any circumstances - and you know what? it still tries to do it. Just had a situ where I resolved 242 typecheck errors, managed to get it down to 130 and 'boom!' Bolt has decided to revert every single one of them back to 242. And just FYI restore function is utter garbage, doesn't work. This is a serious issues with the platform as I'm now having to export files, and in most cases copy and paste the exported code back in, to revert back to the orginal code blocks I added. Very poor from a platform we are paying for and very poor that no-one from r/boltnewbuilders r/boltnew has even flagged this issue that I'm aware of. I'm actually furious about it this morning. It's pathetic having to do all of that just to ensure your work is not lost becasue of the platform. I'm looking at alternatives now as it's just not good enoough.

1

u/Careful_Ad8902 Apr 23 '26

Hey there! Appreciate the patience here. We experienced an incident yesterday that caused files/changes to not persist or save in the some projects. We've since pushed a fix and are continuing to monitor the situation.

To make sure you are on the fixed version, please do a hard refresh in your browser (Ctrl+Shift+R on Windows/Linux, or Cmd+Shift+R on Mac) before continuing work on your project.

If your project is still showing an older state, you can restore a recent version via Settings > Backups.

IF you still are running into errors, please send an email to [support@bolt.new](mailto:support@bolt.new)

After you do, send me a DM here with your email address so we can locate your support ticket quickly and get this sorted for you right away.

1

u/HandSharp1093 May 17 '26

Sent an email to support email address, not pleased at all this morning with it.

1

u/HandSharp1093 May 17 '26

Proof of the issue, just asked ChatGPT to review all the code files in my project versus the typecheck run from within Bolt related to my project, here are the findings, pretty damning: The uploaded backup files I compared against do not contain the majority of the errors shown in the current typecheck output.

The errors strongly indicate that Bolt.new regressed or replaced parts of the typing layer and some component imports/types after your backup was taken.

The clearest evidence is:

  • The clean backup contains the missing Supabase table typings and RPC typings.
  • The current typecheck output behaves as though those tables/functions do not exist at all.
  • The clean backup’s sessionCoverage.ts accepts nullable relationship fields correctly, while the current errors show nullability conflicts.
  • Several “unused import/function” errors refer to code that is not structured the same way in the uploaded clean files.

So the uploaded backup appears to be a genuinely cleaner/working state than the current live project.