Queue Message Major bug

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Queue message doesn’t work in the version 2.2.43 anymore!?

While the agent is running, and you send another message, two things happen now:

  1. the message is sent immediately and interrupting the current agent process
  2. the same message is queued again as if it wasn’t sent yet

So not only is the current running task interrupted with the new command, once that is done the Queued Message is executing AGAIN! Which also leads to unnecessary
token waste…

Initial message:
e8672a82-3253-4aea-ab4d-0bc67f5e8ba8

Supposedly queued message but send immediately:
a2e5a467-b63f-42b5-8646-64227ac2ee0f

Message which is a copy of the above, which is actually queued

e81b6c51-5dff-4dc2-8789-7f103cdf9a7b

Steps to Reproduce

send a message and queue another one

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.43 (system setup)
VSCode Version: 1.105.1
Commit: 32cfbe848b35d9eb320980195985450f244b3030
Date: 2025-12-19T06:06:44.644Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

tested with all Codex models and Gemini 3 Pro

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report.

This looks like a regression. A similar issue was fixed in version 2.2.36 Ask Mode queue interrupts current run instead of waiting, but based on your report it seems to be back in 2.2.43.

I’ll pass this to the team.

1 Like

Hope it’s just me who’s affected

I can confirm this is real on latest version.

1 Like

Looking into this right now

1 Like

havent encountered that anymore, any hunch on what the issue was?