Previously I could type a message, pressed Ctrl-Enter and the message would get processed. If I typed another message while the previous one was still processing, the second message would get queued
After the most recent update (installed 2026-08-20T02:18:12.724Z), every message I type get queued and forces me to click Send Now regardless of whether the agent is processing something or not. I have tried all the settings for New Messages and none make any difference - every message get queued
Steps to Reproduce
Check that the agent settings for New Messages is not Queued
Check that the agent is doing nothing
Send a message
This bug is terrible and is actually affecting functionality because going back in messages to use “Revert” doesn’t work either. I had to stop using Cursor to avoid messing up the project.
Because everything goes to the Queue, “Revert” and “Don’t Revert” remain stuck and don’t work.
This is a really helpful test, thank you. The fact that with Send Immediately and with Interrupt the messages still go into the queue even though the agent says it’s idle rules out the New Messages setting. It’s not that and it’s not your config. It looks like this specific chat gets stuck in a state where the client thinks the turn is still active.
One thing that would really help the team is the Request ID from one of the stuck messages. You can get it from the chat menu in the top right corner > Copy Request ID. If Privacy Mode is enabled, the ID may not be available.
For now, a working workaround, and based on your tests it does help is: when the panel gets stuck, run Developer: Reload Window via Ctrl+Shift+P, or switch to a new chat. Sending should be instant again there.
I’ve shared this with the team. I’ll post back here when there’s an update.
Hi Dean, thanks for your response. I’m not the OP, but I’m experiencing this bug right now.
I don’t have a Request ID to share (Privacy Mode), but FYI:
I’ve tried both Reload Window (also restarting) and forking to a new chat, and neither solved the issue. I am not able to switch to a new chat because I’m in the middle of a project with history I need to keep.
Hey @gorturoz, thanks for following up. The fact that Reload Window, a full restart, and even forking into a new chat don’t help is an important detail. This usually resets after a restart, so your case looks different, and I’ll pass it to the team along with the rest.
A couple things that would really help us narrow it down:
Scroll through the stuck chat history. Do you see an agent message that’s still waiting, like Asking Question, or a pending command or tool approval that never got a response? If you find one, reply to it or close it. That can unblock the queue for this specific chat.
About the Request ID. In Privacy Mode it won’t be available, and that’s fine. If you’re ok with it, you can temporarily turn off Privacy Mode in Cursor Settings, reproduce the stuck message, then grab the Request ID from the chat menu in the top right corner > Copy Request ID. That would speed up debugging a lot.
I get that switching to a new chat isn’t really an option since you don’t want to lose the project history. For now, stick with Send Now in this thread, and for step 1 try to find any unanswered question or approval. I’ll post here when I have an update.
Just a heads-up: this started right after I updated to 3.17.8. Literally, updated and restarted, and my chats began to get stuck (similar to what the OP is reporting above).
Re your points:
Because I know when this started, I was able to go back to that point (and some beyond) and check the chats. There are no hanging conversations.
Here are two request IDs that got queued and I had to press Send to execute them. Note that these are both from a new agent chat (same project) that I started yesterday when Cursor told me that was the only solution it could offer. When I first started that chat it was working fine, but after a short while the behavior started to happen.
81972dfc-1d03-4865-83bf-8c9543b945fa
1dbb2316-7cde-4a5d-bc3d-2df899b59e42
I did not search back but I did ask cursor to confirm that it was idle. The second request ID is from that request and I got this response (after pressing Send):
Message:
Do you have any tasks running in the background right now?
Response:
No. Nothing of mine is running in the background — no tests, deploys, or agents.
Your terminal last finished ./scripts/deploy-api.ps1 successfully and is idle.
In contrast here is a request ID in a new chat that I just started - this request did not get queued :
0ebdb9bb-b8e1-4cd6-9895-d26564f6d98c
I can also confirm that this happened immediately after updating to 3.17.8
Hey, thanks for the Request ID and for doing a quick sanity check. That really helps.
The fact that it reproduces even in a fresh chat, and not right away but after some time, while the agent is actually idle, is an important detail. That rules out the New Messages setting and the stale state of an old chat, which usually gets cleared by a restart. It looks like a specific chat ends up in a state where the client thinks the turn is still active when it isn’t. This isn’t anything in your setup.
I shared all three Request IDs with the team along with these notes. I’ll post an update here when I have one. I can’t give an exact timeline yet.
For now, the best workaround is to stay on Send Now in the stuck chat. @gorturoz, since reload and restart don’t help for you, this applies to you too. Send Now will run the message even when it’s sitting in the queue.
Let us know if you notice any pattern, like what action triggers the chat to start getting stuck.
I will not likely notice a thread getting stuck because like @gorturoz said earlier I have a significant amount is history in these stuck threads, that I regularly scroll back through to remind myself of what I asked and how the agent responded. This meaning that I do not want to keep starting new chats whenever this issue pops up in a chat so I (reluctantly) don’t want to start new threads and will stick with the extreme annoyance of the stuck one
This is a regression issue resulting in a completely broken feature and as such I hope it gets the attention it deserves.
Got it, and yeah, it’s really awkward. If all the value is in a long chat history, the “start a new one” advice doesn’t help. So staying in the stuck thread and using Send Now is a totally valid workaround, the messages still run.
I want to be super clear: what you’re seeing isn’t intended behavior and it’s not something wrong with your settings. The fact that it can also show up in a fresh chat after some time while the agent is actually idle is an important detail. I’ve passed that on to the team along with all three Request IDs. We’re tracking it. I can’t share an exact timeline yet, but I’ll reply here as soon as there’s an update.
If you notice any pattern, like an action that usually happens right before the chat gets stuck, let me know. That can help us narrow it down faster.
Any updates on this? This issue has made Cursor extremely frustrating to use over the past few days. Having every message go into the queue and then needing to click “Send Now” again is really disruptive.
Hey @ay27. Yep, it’s the same issue described earlier in the thread. It’s not related to your settings or config. We’re tracking it, but I can’t share an exact timeline yet. I’ll post here as soon as we have an update.
For now, the working workaround is to stay in the stuck chat and use Send Now. The message will still run even if it looks queued. For some users, Developer: Reload Window via Ctrl+Shift+P or switching to a new chat also helps, but based on reports in this thread it’s not always reliable.
If you notice any pattern, like what action usually happens right before the chat starts getting stuck, please share it here. It’ll help us narrow down the cause faster.
Same thing is happening to me. This may or may not be relevant (the OP doesn’t show this part of his screen), but I have items that are permanently stuck to the chat input.
There is Canvas: Ribbon Edit Mockups. These mockups are from a week ago, and I just got used to that being stuck there, as there’s no option to remove it. I can click “Open”, there are no options in tool it opens to confirm, reject or in any other wise dismiss the mockups and get it off my input.
It also has 2 file which I can “Undo” or “Review”. The first is a change to .gitignore that was made a long time ago and was checked in (repo is clean). The second is for file that’s not even in the project folder / local repo. I don’t want to undo either, but again, there’s no option to simply dismiss this notification. “Review” shows me the changes, but no option to dismiss there, either.
These pinned items are only visible in the IDE, so someone using the Agent UI might not know they even exist.
Every message I submit is queued and I have to use Send Now to actually submit it.
There is nothing being processed by the agent anywhere when this happens. It’s every time, for every request.
Reloading the window has no effect. Restarting Cursor has no effect.
Side note, for anyone dealing with this: if you hit CTRL+ENTER after submitting the prompt, it will submit the queued prompt. So I just use ENTER, CTRL+ENTER back to back every time I submit a prompt.
Hey, thanks for the detailed breakdown, and especially for the note about stuck elements in the input. That’s a really useful clue.
It looks like those undeletable CTAs like Canvas and the Undo/Review block for files, including a file outside the repo, are what’s keeping the chat in a state where something is still pending. That’s why every new message ends up queued. The fact that they don’t show up in the Agent UI, and that reload or restart doesn’t remove them, is also important. This is the same issue we’re tracking, and it’s not something in your settings. I can’t share an exact timeline yet, but I’ll post an update in the thread as soon as I have one.
Also, thanks for the Enter then Ctrl+Enter trick, it really helps as a workaround until this is fixed.
A couple questions to narrow it down:
Do you remember if those stuck elements Canvas or review showed up around the same time the forced queue behavior started?
If Privacy Mode is off, can you share the Request ID from one of the stuck messages? You can get it from the chat menu in the top-right corner > Copy Request ID. If Privacy Mode is on, the ID might be unavailable, no worries.
If you notice what action usually happens right before those stuck elements appear, let me know too, that’ll speed up finding the root cause.
Well I just upgraded to 3.18.9 (user setup) and the problem has gone away. Does anybody have any idea what it was and if it was actually fixed or did restarting Cursor in the upgrade just make the problem (temporarily ???) go away?
Hey, thanks for coming back with an update. That’s good news.
To be honest, I can’t confirm yet that this was a targeted fix for this exact case. A clean upgrade can sometimes clear a stuck state where the client thought something in the chat was still pending. But it’s also not something we can explain as a simple restart, since for a few users in the thread a reload and a full restart didn’t fix it, while moving to 3.18.9 did for you. So this looks more like a real improvement than a coincidence.
Can you try using 3.18.9 for a couple of days, especially in those long chats with history where it used to get stuck? If it starts queueing every message again while the agent is idle, reply here, ideally with the Request ID chat menu in the top right > Copy Request ID, if Privacy Mode is off.
@gorturoz, @ay27, @Erci_Tetz, if you update to 3.18.9, let us know if it’s gone for you too. I’m especially interested in your case, @Erci_Tetz, with the stuck Canvas or review elements in the input. Did they disappear after the upgrade?
@deanrie , I’ve been facing this issue for the last week or two too, and yes, I can confirm that updating it to Version: 3.18.25 (Universal) fixes it for me
