Pending chat message buttons are no longer working

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

For a while now, the up arrow to send now and the trashcan to delete message, as well as the ability to click the chat message itself to edit it have all been inoperative.

Steps to Reproduce

Just press enter to send a message while the agent is producing output or waiting for approval of something. So long as Cursor is not configured to immediately interrupt the model this behavior will show.

Expected Behavior

I expect to be able to click the pending chat message to edit it (this was possible in the past), and to be able to click the “send” up arrow button, and the trashcan button for deleting the message before sending it.

Screenshots / Screen Recordings

Cursor_PYGl2k0FzL.png
Cursor_PYGl2k0FzL.png886×487 16.1 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.49 (user setup)
VSCode Version: 1.105.1
Commit: 21a2ed198584d56a91c0b996d1a09c93f8538440
Date: 2025-12-05T07:49:06.016Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

Not relevant but GPT-5.1 Codex Max Extra High Fast

For AI issues: add Request ID with privacy disabled

49e2cec0-17c1-4594-8a78-0c73127a52e2

Additional Information

If the agent is waiting for approval of a command then the current “enter to send now” is very misleading as this will FIRST approve and start running the command, then a second press of enter will interrupt THAT by sending the message.

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report.

To file the bug, please send:

  • A short video showing clicks on the send arrow, the trash icon, and the pending message itself.
  • Logs from Help > Toggle Developer Tools > Console at the time of the clicks.
  • Repro checks:
  • in a new empty chat and after a restart,
  • with extensions disabled: run from the terminal cursor --disable-extensions.
  • Which version it last worked on before 2.1.49.
  • Temporarily toggle the setting that stops the model when a new message arrives and tell me if the button behavior changes.

Once I have the data, I’ll pass it to the team.

3

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.