This is just awful UX. I often have to close the chat due to lack of screen space and now I have to click twice instead of once, for no apparent reason? There’s plenty of space.
7 Likes
Hey, thanks for the report. Anyway, you can try pressing Ctrl + I, this should close the sidebar with the chat.
Thanks for pointing out a workaround. However, at least for me, that’s not as convenient, since I mostly can’t use a keyboard.
But even general users may not have their hands on the keyboard while reading code, so I would argue that it’s still an unnecessarily worse experience.
2 Likes
Agree, that was a horrible UX decision to remove the x. Please bring it back.
4 Likes
Appreciate the feedback here!
Close Chat is now an option under the context menu to avoid that top bar being too crowded, but I’ll pass the feedback to the team!
Please bring back the “close chat” X button. I made a forum account, literally just to give feedback about this change, and I have almost never created forum accounts ever, for anything, as it’s usually far too inconvenient for me to care. But this change has been so bad, I’ve been back to this thread 4 times over the last 2 days hoping for updates, and the inconvenience of the UX change was large enough where I just had to create an account to say this. Especially since I hope to be using and paying for Cursor for years to come.
It’s such an egregiously bad UX change. I have been using Cursor for about a year now, and I hit that X button all the time. I frequently have 2-3 code viewports open, side by side (Split Right button). Whenever I use the Chat, I use Ctrl-L to auto-open it, and after doing so, I turn on “Toggle Editor Group Sizes” (the thing when you double click the tab, that maximizes it’s size). I then quickly chat (Agents are cool, but I utilize the Ask more than anything), and then close the Chat, so I can see my code.
Since the change, I have just been frequently annoyed. Sure, this has ruined my specific flow, but it literally ruins any flow that frequently opens/closes the Chat but uses their mouse a lot (which is the case if you’re copying and pasting back and forth between Documentation and the Cursor Chat a lot!).
On PopOS (Linux) specifically, half the time it doesn’t even close now as well. I right click, hit Close Chat, and it doesn’t close. I then hit Ctrl+I, and it doesn’t close. I have to specifically “focus” the code viewport, and only then will Ctrl+I work. Regardless of the bug, the double click to press “Close Chat” is still really really annoying.
I agree that making the top bar less crowded is probably good, but at least put an option in the Cursor Preferences/Cursor Settings to bring the X back! Like, this adds so much annoying friction that I’d rather just Alt-Tab to my ChatGPT window, because it doesn’t block the visibility of my code, and takes just as many, if not less now, clicks/keypresses.
Rant over… Overall, the 1.0 update and the updates leading up to it have been really great, kudos to the whole Cursor team. Although, this change specifically has really been ruining my productivity, and I don’t doubt I’m the only one.
2 Likes
The close chat button in the context menu does not close the chat for me (linux).
Can this be made a top level button? I get that making it harder to dismiss probably contributes to better usage numbers, but it is a frustrating user experience.
1 Like
For me does not work either, Im on Windows.
Thank god Im not the only person whos getting ■■■■■■ over these ridiculous UI limitations…
1 Like
Thanks a lot, much appreciated!