When I queue messages while the agent is working and the agent moves to those queued message(s), I will often run into a “Taking longer than expected” error, from which the agent and/or client never recovers. My current work-around is to stop generation and resubmit as a normal (non-queued) message.
Steps to Reproduce
While an agent is working (before it finishes), queue more messages, then observe.
Expected Behavior
Queued messages should work (and in general, I think they should behave like normally sent messages).
Hey @jsimonrichard, thanks for the report, and for the Request ID.
That ID belongs to the message you re-sent after stopping (it ran fine on our side). The queued messages that got stuck never actually left Cursor, which is why the agent sat on “Taking longer than expected” with nothing to recover from.
You’re on 3.18.9, and there have been several changes to how queued messages are sent since then. Could you update to the latest version (3.20) and try again?
Hey @jsimonrichard, thanks for trying the update and for the screenshot, that was the missing piece.
I can see what is happening now. When the running task finishes, Cursor moves your queued message into the chat as a sent message, but in some cases the actual send behind it does not go through, so nothing starts and there is nothing to stop. It depends on timing at the very end of the previous task, which is why it sometimes works and sometimes does not.
Until it is fixed: if a queued message shows up in the chat but the agent does not start working within a few seconds, just send it again (copy the text and press Enter). No need to press Stop first. If you queue several messages at once, check that the first one actually got a response, since it is the one that can get skipped.
While I have filed this with the team, I also expect the issue to eventually be resolved on a newer version of the agent runtime we are gradually moving users to!
Quick update: a fix for queued messages showing up as sent without the agent actually starting has landed, and it will be included in an upcoming version of Cursor (3.23).
