Agents Window: Send / Ctrl+Enter does nothing; same draft sends fine from IDE chat tab (WSL2)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

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.

Steps to Reproduce

  1. Open a workspace over Remote-WSL (Ubuntu).
  2. Open Agents Window (Command Palette → “Open Agents Window”).
  3. Select an existing agent (or create a new one).
  4. Type a message in the input.
  5. Press Ctrl+Enter — nothing is sent.
  6. Click the Send button — nothing is sent.
  7. Open the same agent in the IDE chat tab / side panel.
  8. Observe: the same message draft is present in the input.
  9. Send from the IDE chat tab — it works.

Expected Behavior

Send / Ctrl+Enter in the Agents Window should submit the message the same way the IDE chat tab does.

Operating System

Windows 10/11

Version Information

Windows 10 Pro 22H2 (Build 19045.7548) + WSL2
WSL: 2.7.11.0 (kernel 6.18.33.2-microsoft-standard-WSL2, WSLg 1.0.73.2)
Distro: Ubuntu 20.04 LTS (Focal)
Cursor: 3.13.25 (stable)
Commit: 31e8d61c448c7472e371505838a0fe34083dad50
VSCode: 1.128.0

Additional Information

  • Workaround: open the same agent in the IDE side panel / chat tab and send from there.
  • Happy to provide screenshots or a short screen recording if useful.

Does this stop you from using Cursor

No - Cursor works, but with this issue

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:

  1. 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.
  2. Does this happen in every agent session in the Agents Window, or only a specific one?
  3. 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.

Hi Dean,

thank you for your quick reply.

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.