Describe the Bug
date: 2025.07.14
two days ago, everything was fine.
today when I begin dev work, cursor is much faster in terms of response (pretty good).
but when I try coding with large diffs, it just pops up for a while and got accepted automatically.
later attempts shows the same result.
by the time the chat is done, the diffs are already accepted and merged into the codebase, nowhere to be visible.
by the pace of your recent updates, I can see that you’re pushing lots of useful improvements, some bugs are pretty understandable.
but this is critical bug, please track and fix immediately.
Steps to Reproduce
Please refer to the version info.
It just happens right now, blocking usage.
I can’t trust or tolerate an AI tool that overturns my control over the codebase.
Expected Behavior
diff appear, user review, accept or reject, at the user’s discretion.
AI can’t decide it whatsoever by default.
did you add some new feature and forgot to keep backward compatibility at args/settings level?
(like, some auto-accept logic with a timeout stuff, or maybe it’s just bug?)
dude~
software engineering bro.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.2.4 (user setup)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T17:09:01.383Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
Does this stop you from using Cursor
Yes - Cursor is unusable