Chat text field unexpectedly stops working

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Suddenly and without warning, the text box in the chat pane stops accepting keyboard input.

I am typing but nothing happens.

Steps to Reproduce

Not sure what steps get it in that state. Usually it’s after a long time chatting with the agent, so I assume the bug manifests when there is a very long thread of conversation behind it.

Expected Behavior

Supposed to not prevent me from typing

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.44
VSCode Version: 1.105.1

For AI issues: which model did you use?

Sonnet 4.5

Does this stop you from using Cursor

Yes - Cursor is unusable

Agent chat randomly disallowing user input
2

Hey, thanks for the report.

This issue sometimes happens with the chat input field. A temporary workaround:

  1. Press CMD+Shift+P in the chat window
  2. Select “Developer: Reload Window”

This will reload the window and should restore input.

To help the dev team figure out the cause, please share:

  1. Are you using multiple monitors? Do you open chat as a separate window?
  2. Do you see any errors in the Developer Console (Help > Toggle Developer Tools > Console tab) when the issue happens?
  3. About how many messages are in the chat when this happens?

Let me know if this helped.

3

Reloading the window doesn’t help, this chat is dead in the water, I have to start a new one.

I did a bit of debugging (now that I discovered the dev console :hugs: ) and I found this. It’s being blocked by defaultPrevented. Hope that helps!

Screenshot 2026-01-01 at 4.09.26 PM
Screenshot 2026-01-01 at 4.09.26 PM1492×1906 452 KB

I have Cursor in that state if you want to debug this live :grinning_face:

4

Thanks for debugging this. The defaultPrevented info is really helpful!

I’ll pass this along to the dev team. If the chat is still in that state and you’re up for helping with debugging, can you send the full log from the Developer Console? Also, about how many messages were in the thread when this happened?

For now, the only workaround is to start a new chat.