Composer hangs during Applying → Then, Composer shows the red text that says: “› Cancelled (1 file changed)” → Then, composer Applies those cancelled changes about ~5 minutes later after it just said it Cancelled applying them
→ I checked the forum and I don’t see this particular bug, especially not recently.
//
clear description of the bug / reproduce the bug (if known):
Sometimes, for 30 minutes to an hour (or more?), I encounter an issue when inputting my Composer request into a fresh Composer dialog (right after pressing the “+” button). My request is typically a simple code task.
When I submit it, the suggested edits generate as expected, but then the process stalls at “Applying.” It takes longer than expected to Apply, often 1–2 minutes or more.
After the delay, it displays “› Cancelled (1 file changed)” in red (see screenshot). Reading the UI, I assume “Cancelled” means the process has stopped, so I move on with my work, editing the file.
However, several minutes later (sometimes 2–7 minutes or more), Composer seemingly randomly applies the red/green highlighted changes, displaying the Accept/Reject buttons directly in the code—right where I’m actively working. This disruption happens even though the UI still shows “› Cancelled (1 file changed).” At that point, new gray/blue “Reject All” and “Accept All” buttons also appear next to the “Cancelled” message.
I need a reliable way to cement the cancellation so Composer doesn’t try to apply suggested edits minutes after marking them as “Cancelled.” Alternatively, I’d like to better understand why this happens or how to predict when it might occur. Is this something I can monitor through Mac’s ‘Activity Monitor’ to check resource usage, such as how much memory Cursor is consuming?
This is an intermittent and relatively uncommon issue—it happens about once a day—but when it does, it can halt productivity for an hour or more. The lag between “Cancelled” and the seemingly random application of edits makes it difficult to track or troubleshoot. I also don’t want to sit idly for up to 10 minutes waiting to see if the “Cancelled” edits will still apply themselves for no apparent reason.
I hope I’ve explained the issue clearly enough for the community to relate and share advice on how to deal with this frustrating bug.
//
screenshots or recordings
//
operating system and Cursor version
->🗣️ MacOS Sequoia 15.1.1
→ Cursor Version: 0.44.11
VSCode Version: 1.93.1
Commit: fe574d0820377383143b2ea26aa6ae28b3425220
Date: 2025-01-03T07:59:06.361Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin x64 24.1.0
//
Tell us if the issue stops you from using Cursor.
→ 
This issue does not stop me from using Cursor. However, this issue probably would stop me from using Cursor if I encountered it more often.