In the Agents Window, typing a message and trying to send it does nothing:
Ctrl+Enter does not send
The Send button also does not send
The message is not submitted and the agent does not start/continue.
If I then open the same agent session in the IDE chat tab / side panel, the drafted message is already sitting in the input, ready to send. Sending from there works normally.
So the draft is shared correctly between UIs, but the submit path appears broken only in the Agents Window.
This does not look like a user keybinding misconfiguration: both keyboard submit and the Send button fail in Agents Window, while the identical draft succeeds in the IDE chat tab.
When I press the send button from the Agents Window, I can see this in the dev tools log.
Hey, thanks for the detailed report and the screenshot. I can see [composer] current bubble is undefined in the console on submitChatMaybeAbortCurrent, so the submit action in the Agents Window is failing silently, while the draft still gets saved and then picked up in the IDE chat tab. That shouldn’t happen.
A couple things that’ll help us narrow it down:
In the Agents Window, run Developer: Reload Window from the Command Palette and try sending again. Does that bring sending back? This kind of issue on Remote-WSL often gets fixed by rebuilding the workspace or agent binding.
Does this happen in every agent session in the Agents Window, or only a specific one?
Did this start after a specific Cursor update, or was it like this from the start?
For now, the workaround you already found, sending from the IDE chat tab or side panel, is fine to use.
The problem was introduces with some new versions installed about 10 days ago, but no problem at all, I just installed latest version solved the problem.
Glad the update fixed it. Looks like something in an intermediate build was interfering with the submit path in the Agents Window, and the latest version picked up the fix.
If the no-op comes back and Send or Ctrl+Enter stop sending in the Agents Window again, reply here with the DevTools console output at the moment of the dead click and your Cursor version, and we can dig deeper. For now I’m marking this thread as resolved.