Stopping agent reverts changes

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

This one is driving me crazy today and making Cursor practically unusable right now. I have lost so much work and could not figure out why. Finally found it.

When clicking the stop button, pending changes are being erased/reverted/lost. Not even just erased, but seemingly randomly reverted. It’s extremely hard to recover from this because everyone is confused about what was applied and what wasn’t.

Typically, this happens after a series of really long changes when the agent has decided it needs to give me a summary. I click stop, then it just randomly throws everything out.

Steps to Reproduce

  • Have the agent do anything.
  • After the agent has generated some changes, click stop
  • your changes are lost

Expected Behavior

Stopping shouldn’t do anything other than stop the agent.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.45 (Universal)
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

Yes - Cursor is unusable

This is a real problem. I’m losing tons of work from hitting the stop button and having everything go p ooooo f

Hi, thanks for the detailed report. To help us reproduce and fix this issue, could you provide some additional details:

Context & Model:
• Can you share if this happens for every chat or only for very long chats when context is almost full?
• Which model does this happen for?
• Can you please share a request ID?

What Exactly Happens:
• When you click stop, does it show that all the changes in Agent chat are rejected? Or does the chat messages disappear?
• Are you able to reproduce this consistently, or does it happen sporadically?

This information will help us identify the root cause and get this fixed. Thanks!

> Can you share if this happens for every chat or only for very long chats when context is almost full?

I did not necessarily see any correlation. It seemed to be happening on every chat

Which model does this happen for?

I almost exclusively use Claude Sonnet 4, but I don’t believe it’s specific to that model.

Can you please share a request ID?

I don’t have one handy. I’ve had so many chats that I can’t remember which ones caused this.

Unfortunately, I’m now unable to reproduce this. I am noticing a slight change to the UI, so maybe it got fixed with an update.

When you click stop, does it show that all the changes in Agent chat are rejected? Or does the chat messages disappear?

No. This is the most annoying part. Everything in the UI indicates that things are working as expected. Chat history is present and the modified file list in chat displays the correct content.

Under the hood, the actual files are reverting to some sort of random prior state. The LLM will try to make edits to them and say something like “That’s odd, our changes aren’t in that file anymore. Let me rewrite them”

Are you able to reproduce this consistently, or does it happen sporadically?

This was happening on literally every conversation earlier in the week. I worked around it by always clicking the “Keep All” button before stopping the agent.

Right now, I cannot reproduce this.

1 Like

Thanks for the detailed response. I’m glad it’s fixed for you now. In case this happens again, please share the request ID with us.

@sanjeed5 I just had this happen. Request ID: b55c8255-3085-4cd8-b03c-94f414df90e6

Here’s what happened:

  • Agent was doing a bunch of code base exploration
  • Agent wrote out findings to a markdown file
  • I gave the agent direction on how to refine the findings in the markdown file
  • While the agent was thinking/working (but before any changes were written), I decided against action I just gave it
  • I hit stop. All changes are lost

Just happened again. Request ID: 7b8abf49-3a25-430d-bb2d-b0028bc11f35

This doesn’t happen much because I’ve generally started committing to git before I click the stop button. It at least gives me a way to fix this mess.

Thanks for the info, that’s very helpful.

Yep!

It’s worth noting that commiting to Git before clicking stop doesn’t solve the issue, it just gives me a manually curated checkpoint that I can restore from, independently of Cursor.

1 Like

Having this happen a load on this request ID: 48525be9-08f3-41a0-a744-e766f532faaf

Extremely annoying as it keep trying to run scripts that it’s just written then it needs to cycle on re-writing the script.

Any update on this?

This is becoming a complete blocker for me. I’m just randomly loosing progress all of the time now. It’s basically impossible to reliably use Cursor when this is happening.

@wesley-harding thanks for the request IDs. Sorry that you are facing this issue. I’ve passed it on to the team. Which Cursor version are you on now? Is this still happening on the latest version?

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.