Chat Input Malfunctions After Long Agent Sessions (Shift+Enter / Text Deletion Issues)

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After extended conversations with the Agent, text input behavior in the chat becomes incorrect.

Pressing Shift+Enter inserts a line break at an unexpected position.
When selecting a block of text with the mouse and deleting it, only the last character is removed instead of the full selection.

The issue occurs intermittently and cannot be reliably reproduced. Closing and reopening the chat window restores normal behavior.

Steps to Reproduce

The issue is not consistently reproducible. It has been observed under the following conditions:
Have a long-running conversation with an Agent (large chat context).
Continue interacting in the same chat session.
Text input issues may start to appear (Shift+Enter behavior and incorrect deletion).
Close and reopen the chat window → issue is resolved.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.43 (system setup)
VSCode Version: 1.105.1
Commit: 32cfbe848b35d9eb320980195985450f244b3030
Date: 2025-12-19T06:06:44.644Z
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

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

After leaving Cursor running while the computer was idle for several hours, I found it had hit an OOM error when I returned.
Cursor was fully restarted after the OOM.

3

Hey, thanks for the report.

This is a known issue where the chat cursor position can get out of sync after long sessions. The team is working on a fix.

As a temporary workaround, closing and reopening the chat (like you found) is the best option for now.

To help with debugging, could you:

  • Next time it happens, open Developer Tools (Help → Toggle Developer Tools), check the Console tab for errors, and paste them here

About the OOM: after long idle time this could be a memory leak. Did you notice memory usage climbing during active Agent use, or did the OOM happen only while Cursor was idle?

4

The OOM was discovered after the computer had been in screen-off / sleep state around noon.
When I woke the screen, Cursor was already showing the OOM error.

Before the screen was turned off, there were no large programs running.
Cursor was idle at that time (no active Agent tasks or interactions).