Cursor updater kills all Cursor instances without any confirmation

Feedback
1

On Windows, the Cursor updater kills all Cursor instances without any warning or confirmation, even when a Cursor instance have a modal dialog open.

Here’s the full story: Cursor’s update popup appeared at the bottom left cornor. Was going to check out the changelog, but accidently clicked on the update link. The updater launched, killed multiple editor instances and 20+ terminals with running programs, resulting in a catastrophic data loss. The editor will warn you about active terminals when exiting gracefully (see below), but the updater killed them altogether forcefully.

image
image835×279 9.73 KB

I, as a pro subscriber, find this behavior unacceptable and wish you guys reconsider the behavior of the updater. Much thanks.

Version info:

Version: 0.45.11
VSCode Version: 1.96.2
Commit: f5f18731406b73244e0558ee7716d77c8096d150
Date: 2025-02-07T09:43:58.555Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.26100
2

Yes great feedback, Cursor team is working on ‘update’ improvements. I agree that the update tool should ask for permission to close the app.

3

Hey, thanks for the report. We’ll work on improving this in future versions.