Ask Mode queue interrupts current run instead of waiting

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using Ask Mode in Cursor, the prompt queueing behavior doesn’t work as expected. If an Ask response is currently generating and I submit another prompt (intended to be queued), Cursor immediately stops/cancels the in-progress Ask run and begins executing the newly submitted prompt instead.

This seems specific to the “modes” UI (Ask / Debug / Agent / Plan). In my case, queueing while in Ask does not behave like a queue; it behaves like preemption.

Steps to Reproduce

  1. Select Ask Mode.
    2. Submit a prompt that takes a bit of time to generate a response.
    3. While it’s still running, submit a second prompt (expected to be queued).
    4. Observe that the first run is stopped and the second prompt runs immediately.

Expected Behavior

Queueing should work regardless of mode (Ask/Debug/Agent/Plan).
• Submitting a new prompt while one is running should enqueue it and wait until the current response finishes.
• The first result should remain open/available so the next queued prompt can reference it.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20 (Universal)
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Any, but auto usually.

Does this stop you from using Cursor

Yes - Cursor is unusable

Queue Message Major bug
2

Hey, thanks for the report. I’ll pass it to the team.

4

Any update here? Queue doesn’t work at all (just checked for updates and there are none) and this is totally disrupting my workflows

5

Hey, this should be fixed in version 2.2.36.