Bugged Chat on another screen

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Chat on a new window is really bugged:

When I try to attach a code or file it closes immediately.
The Custom Agent selection UI seems odd (it shoots up).
I can’t select previous chats without resetting the chat.
Trying to “Ctrl+L” to go to the chat closes it.

Steps to Reproduce

  1. Open a new chat as Editor
  2. Drag the chat to another screen or outside of Cursor
  3. Resize the chat to be full screnn
  • Try to attach a code block
    – On a file, select a the code and press the “Add to Chat” Keybind (not clicking it)

  • Try to select another Custom Mode on a previous chat, the selector will appear on the top, not on the Agent.

  • On a previous chat (already with conversation), try to select another chat on the Chat History (top right), clicking will do nothing.

  • Trying to use the Go to Chat keybind closes the chat, when it opens again it appears on the sidebar.

Expected Behavior

The chat on a screen outside of Cursor is really handy sometimes, you can see more and it occupies less space on the actual editor.

I should be able to fully use the chat on another screen, all the features and keybinds should work fine.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.7 (user setup)
VSCode Version: 1.99.3
Commit: 6aa7b3af0d578b9a3aa3ab443571e1a51ebb4e80
Date: 2025-08-27T22:43:32.248Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Additional Information

On clicking to go to a previous chat, on the console (Developer tools) there is an error occuring:

Uncaught TypeError: Cannot read properties of undefined (reading ‘shiftKey’)
at Object.onClick (workbench.desktop.main.js:4823:8345)
at HTMLDivElement. (workbench.desktop.main.js:1544:15251)
onClick @ workbench.desktop.main.js:4823
(anonymous) @ workbench.desktop.main.js:1544

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

Hey, thanks for the report here!

The team have been working hard on improving this type of experience, so I’d recommend checking our next few updates for some significant improvements on this Agent-only view.

I have passed your feedback to them in the meantime :folded_hands:

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