Chat window does not work in new window

[kursormike]

Hi all. I’m quite new with Cursor. I realized that Cursor allows me to open the chat window in a separate window (which I couldn’t do in vscode with co-pilot). However, as soon as it is in a detached new window, I’m no longer able to type in the chat box.

I’m on OSx 13.6.1 on M2 Pro.

[litecode]

Hi @kursormike ,

I documented similar behaviour in this post:

@litecode

I’d also love Ctrl + L to be able to ‘pop out’ so that I could drag it to another screen - currently I can click on the ‘Chat in Editor’ icon, and then drag the ‘AI Chat’ tab to another screen, but there seems to be a bug where the prompt area then stops accepting text.

I also added a bug report about a related issue of not being able to drag Composer to a new screen:

Composer disappears when dragging it to another screen

I love Cursor and Composer . I also love the pop-out/floating feature of Composer. (I would love it on Ctrl + L too). I mentioned it previously in a post comment but thought I would create a separate post for this behaviour, which seems to be unintentional. Composer ‘disappears’ when you try to drag it to another screen. See attached screenshot of undesired behaviour. Having Composer and Ctrl L in another screen would keep the Cursor interface free of distractions etc. I ac…

[kursormike]

Thanks. Yes, it is as you described that it no longer accepts text once it popped out.

[litecode]

I think someone else reported that the scroll bar stops working too.

Pop out window for AI Chat

confirm this. Chat editor when moved as a window to otehrscreen doesn’t scroll.

[kursormike]

This behaviour seems to be a little inconsistent. I tried a bunch of times, on occasion I’m able to type in the chat box.

Workaround: I thought it’d be an interesting experiment if I pop in some history in the chat box whether the chat would become editable, and it did. So this is my work around for now.

Yes, the non-scrollable chat is an issue in a separate window.

[maxpower]

it’d be great if chat worked in a separate window because often I’m limited with space, but could easily chuck the chat on another display

[jvaldiviezo]

I’d like to mention that this happens on Windows as well. Not just macOS.

[thezstack]

just noticed this as well

[adventurousDev]

There seems to be a workaround:

@adventurousDev

I just noticed that adding any second tab to the cursor chat/ composer window activates the input field. Strange, but a useful workaround for now.