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 Windowfrom 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.
This looks like it’s in the same family as the Remote-WSL Agents Window issues we’re tracking, see also this thread: [WSL Remote] anysphere.cursor-agent-exec never registers — every agent prompt times out (ERROR_EXTENSION_HOST_TIMEOUT) in remote-WSL windows only; works locally and via cursor-agent CLI. Your case with a silent no-op is a bit different, so the answers above will help. Let me know how it goes after Reload Window.