Bug in Agent chat input field when set in floating window

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

There’s an issue with Agent chats in Cursor. Everything works fine as long as the chats remain docked in the main application. However, when I detach a chat into a floating window and move it to my second monitor to work alongside another codebase, then close the remaining chats using the “Toggle Agents” icon in the top-right corner, the input field starts behaving incorrectly.

After typing each character, the text cursor jumps back to the beginning of the input field. The same issue occurs when backspacing, making it difficult to edit or type messages normally.

I hope this bug can be addressed in an upcoming update. Thanks!

Steps to Reproduce

  1. Open Cursor and start an Agent chat.
  2. Detach the Agent chat from the main application and move it to a second monitor as a floating window.
  3. Keep a different codebase open on the main monitor.
  4. Click the “Toggle Agents” icon in the top-right corner to close the remaining Agent chats.
  5. Try typing or backspacing in the floating Agent chat’s input field.
  6. Observe that the text cursor jumps to the beginning of the input field after each keystroke, making normal text editing difficult.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.14.7 (user setup)
VS Code Extension API: 1.128.0
Date: 2026-07-30T06:41:34.009Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26300

For AI issues: which model did you use?

Composer 2.5 Fast

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hi @Devesh_panwer, this should be fixed in newer versions of Cursor. You’re on 3.14.7, and the latest release includes a fix for the text cursor jumping to the start in a floating chat window, so updating should clear it up (you can grab the latest from cursor.com/download if the in-app update doesn’t offer it).