V 1.2.1 serously broken

Bug Reports
1

Describe the Bug

I just upgraded to 1.2.1, and it seems broken. Using Opus in MAX mode, it made changes to multiple files. I see the files as changed in File Explorer and Git, but I do not see the diffs when I open them. Normally, I can review them one by one and accept/decline. Pressing “Review changes” in chat shows a diff panel of all file changes. Tried to restart - no change.

Steps to Reproduce

Change multiple files via chat query

Expected Behavior

When open individual files should show changes with ACCEPT/REJECT button for each

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.1
VSCode Version: 1.99.3
Commit: 031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0
Date: 2025-07-03T06:13:13.763Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Linux x64 6.11.0-29-generic

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, does this happen in a new chat? Also, could you share the request ID? You’ll need to disable privacy mode first.

3

How can I send it to (privately)?

4

Ive seen this too. 1.1.7.
Open an issue here.

5

I dont think there is a reason to hide the request id as nobody can do anything with it unless they work at cursor. you could email them but im sure their email is full of other people and be appreciated if you would continue the conversation here. otherwise you cann look the email up.

1 Like
6

this is definetly a premature release - roll it back

7

Its annoying when working through a bunch of changes, you crash, come back and all the changes are lost. But you fixed them, they just didnt save.

8

I’ve seen this behaviour on various versions, so it’s likely not 1.2.1 specific. I wasn’t able to repro on OSX, it was working fine for me.

Curious to see your chat settings. Are you on Agent mode with auto-run enabled?
Does manual mode or cmd+k work properly?

Are you running extensions? Does running cursor --disable-extensions from terminal to launch cursor fix things?

Otherwise can you try to perform a clean install? (step 3 here)

image
image1280×118 10.5 KB

9

I ran into similar issues, and it turned out to be a capitalization problem with file names which creates major headaches with git. Different operating systems handle case sensitivity differently (some are case-sensitive, others aren’t), but the agent doesn’t always account for this inconsistency when working with files.