Bug: "Open as Editor" and "Move to new window" on chat tabs breaks the prompt input

[Michael_Cole]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I “Open as Editor” or “Move to new window”, Cursor used to just intermittently have problems. So I could create a new tab and just keep using it.

Now, the prompt doesn’t type, or it crashes something in the backend, or it starts typeing backwards, or any of several other bugs.

Please make this feature work. I have 4 monitors and vision problems. Please make the AI chat windows work in a 2nd window so I have enough worspace to SEE.

Steps to Reproduce

Start a chat
“Open as Editor” or “Move to new window”
Try to use the prompt and it has all kinds of buggy behavior. Doesn’t type. Crashes. Types backwards.

Expected Behavior

It moves to a new window as promised.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Cursor 2.0.69
VS Code 1.99.3

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report. This is a known issue - chat in separate windows isn’t fully supported right now due to multi‑window rendering limitations. The team is aware and working to bring this back, but there’s no timeline yet.

Workaround for multi‑monitor setups:

If you need chat in a separate window: after “Open as Editor” → “Move to New Window,” reload the window: Ctrl+Shift+P → type “Developer: Reload Window” → Enter. This temporarily fixes input.

I’ll flag this to the engineering team given the accessibility impact.

[Michael_Cole]

Thank you!