Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Any other message you try to send while some work is being done, just queues that message to be sent afterwards. But when you call /summarize, it stops the current work on its tracks. And after summarized, it also does not continue the work from where it stopped, unless you send a new message asking it continue.
Steps to Reproduce
- Send some long work to start working on…
- Then while that is running, call
/summarize - The current work stops

- Send some long work to start working on…
- Then while that is running, send a message with some more follow-up details.
- The message gets queued, and the current works continues normally

Expected Behavior
My expectation would be that /summarize works like any other message/command. That it should get queued. And you could still choose to manually “send now”, to stop the current work more intentionally if you need.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.4.0-pre.50.patch.0
VSCode Version: 1.105.1
Commit: 607284f6ec7035970f7a03d23a765b138f73c680
Date: 2026-01-19T08:29:30.378Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0
Does this stop you from using Cursor
No - Cursor works, but with this issue