The Agent prompt text and the Backspace button Acts FUNNY

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

It seems like you have a lot of issues even in the forum, after I wrote the description, I modified the [Support - Bug Reports], It cleans all what I add JUST like your IDE prompt text.

ANYWAY, The agent prompt textbox didn’t focus with mouse left-button for more than 30 seconds of tries.

The Backspace button makes the cursor move to the zero index.

In multiple line (CTRL + Enter), The Backspace select the entire texts and remove it and when trying to move with Up/Down Arrow, it moves to the chat history, I think it tries to remove it also.

Steps to Reproduce

Open an agent in a new tab and do any job until the prompt text became very tight single-line-height (WHY DON’T YOU MAKE THE TEXTBOX A LITTLE BIT BIGGER???) and try to focus the textbox, try with single line and hit the Backspace button, Try to write multi-line with CTRL+Enter and try to move Up/Down and use the Backspace button.

It’s missy

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.1.17 (user setup)
VSCode Version: 1.105.1
Commit: fce1e9ab7844f9ea35793da01e634aa7e50bce90
Date: 2026-04-19T19:33:58.189Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report and the video. There are a few different things here, so let’s break it down:

  1. Up and Down in the chat input goes to history. That’s the current intended behavior. The arrow keys browse previous prompts. In multi-line mode this is annoying, agreed. Related threads: Any Mode + Up Arrow, : Chat input field doesn't capture Option+Arrow keys, triggering app-level navigation shortcuts
  2. Backspace jumps to the start or deletes everything in multi-line. This looks like a cursor position bug. I’ve seen a similar pattern before.
  3. The textbox doesn’t focus on click for about 30 seconds. That’s not good, we’ll need a bit more detail.

To report this more accurately, can you confirm:

  • After a full Cursor restart, do the issues happen right away?
  • Do you have any extensions installed that change keybindings, like Vim, emacs, IdeaVim, etc.? If yes, try running cursor --disable-extensions and check if it still happens.

Once you confirm, I’ll file a bug ticket for the team.

  • After restart the IDE, It works for the first message and the Backspace button was working properly after the first message, Back to the issue mentioned above, Cursor focus, Backspace, and other things happened I can’t explain all the keys, You need to try it your self.

  • I have no keybindings extensions.

  • Another issue with PASTING with CTRL+V, It pastes the text in the first position (index zero)

    It’s MISSY, A lot of issues

Thanks for the details. This matches a known bug with the chat input in the editor layout. After certain interactions, the Lexical editor in the tab gets out of sync with the real cursor position. That’s why Backspace, Up/Down, and Ctrl+V act somewhere else than where the cursor looks. We’re tracking the issue, but I can’t share an ETA for a fix yet.

What helps right now:

  1. Quick workaround: press Ctrl+Shift+P, then run Developer: Reload Window in the tab where the agent is open. After reload, typing works again until it gets stuck again.
  2. More stable option: switch from the Layout editor back to the Agent panel in the side panel. The bug doesn’t reproduce there.

Related threads for context:

About the textbox size and Up/Down acting like history, those are separate points and they’re also noted. Once I have an update on the input fix, I’ll reply in this thread.

Actually, I have difficulties to accept that, You are more professional than me and you built an IDE with a special AI agent to help developers like me, It’s NOT acceptable for me as a subscriber and in the age of the AI to not give that issue an extremely high priority.

I have difficulty to believe that you can’t fix that.

I hear you, and the frustration is totally fair when something this annoying is stuck in the input box you use every day.

To be direct: the bug is logged on our side, and I’ve linked your report to the related tickets so it counts toward priority. I won’t give you a fake ETA. I don’t have one, and overpromising wouldn’t be fair.

For now, the most reliable option is to use the Agent in the side panel instead of the Layout editor tab. The bug doesn’t happen there, so you can keep typing normally. If you prefer the editor tab, Ctrl+Shift+PDeveloper: Reload Window resets the input until it gets stuck again.

The textbox size and Up/Down going to history are tracked separately, and both are noted. If anything changes on the input fix, I’ll post in this thread.