Message queue regression again

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I queue a message, sometimes it will interrupt the running agent and execute the message immediately and still add the message to the queue at the same time, so the message will be executed twice.

Steps to Reproduce

Send a message 1 to agent
Agent is running
Send message 2 to the agent to add it in the queue
Message 2 is added to the queue
But at the same time, Agent interrupt message 1 execution and start immediately running message 2
Once message 2 is done, the agent is running message 2 again because it was added in the queue

Expected Behavior

When adding message to the queue it should not interrupt the running agent and it should be executed once the agent is done with the ongoing task

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.35
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0

For AI issues: which model did you use?

Opus 4.5

Additional Information

Regression that was already fond several time in previous versions

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Hey, sorry to hear that!

  1. Do you remember which Cursor version worked correctly for you?

  2. Did you check Cursor Settings > Agents and this setting?

scr 2026-01-16 at 17.18.26@2x
scr 2026-01-16 at 17.18.26@2x1368×232 17.6 KB

  1. Does it happen every time you do the steps you listed?
  2. Could you check Help > Toggle Developer Tools > Console to see if there are any errors when the issue happens?
4

Hey, this looks like a regression of a known message queue bug.

@Ra.in asked the right questions. If you can answer them, that’ll help.

5

Hi,

It happened again just now. Request ID: 6ae4119c-7300-4e7e-b867-5aefc9bd9490

  1. No, there are many updated and I don’t track which ones contains which bug sorry
  2. Yes, I checked and it is configured properly
  3. No, sometimes
  4. Not sure if those errors were there or not when the bug happened, but the console is on fire with many errors:
    1. No handler found for server message of type abort
    2. Trace spans collection is not enabled for this user
    3. [transport] Stream error reported from extension host ConnectError: [canceled] [aborted] Error
    4. transport] Connect error in unary AI connect ConnectError: [not_found] Error
    5. etc
6

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.