People have been asking for a fix for the chat/composer hotkey toggle since Cursor released basically. If you rebind any of the default hotkeys relating to toggling the chat/composer sidebar, they will just stop working completely. A very few selection of them “work”, as in, you can press the hotkey and open the window, but then you cant close it. I’ve seen many devs blame this on “chat focus”, but this is not the case. Even if you unfocus the chat the hotkeys will still not work.
I wouldn’t have such a problem with this issue if it didn’t seem like the devs were constantly ignoring it over the course of years. There has been repeated posts about this specific bug many times in both the github issues and forums, to which devs reply they will “fix it” and then promply close the issue and do nothing about it…
Now I see in more recent posts devs just saying things along the lines of “just use the default hotkey”. This is a frankly ridiculous response. Why bother forking VSCode if you’re going to break the functionality it already has? Like there is built in functionality in VSCode “workbench.action.toggleAuxiliaryBar”, that handles this, and this actually works as expected, BUT only if you use “CMD + ALT + B” (the default hotkey). If you rebind this in anyway, then it ceases to work entirely… I dont understand how the cursor devs have screwed it up this bad???
Honestly, I was very bullish on Cursor but after seeing these incredibly trivial bugs go ignored in favor of gimmick and hype functionality, it makes me not only question the motives of the devs behind cursor, but also the general quality standards to which Cursor hold themselves. Perhaps the reason this issue doesn’t get fixed, is because Cursor itself is incapable of fixing it and maybe that is what the devs are relying on at this point?
And it’s not just this 1 small bug, Cursor imo seem to have a trend of ignoring basic usability features/fixes and instead chasing gimmick features they know will get them investment, even if they are completely unusable or unaffordable for most people.
Personally despite being a big fan of Cursor’s AI functionality, I will be cancelling and no longer recommending Cursor to anyone until they start getting some of these basic usability bugs fixed… If this were open source, I would definitely cut some slack, but for a paid product that also gets private and VC investment, and also employs some very talented developers, this is quite frankly unacceptable. You expect us customers to believe that despite Cursor having a 2.5bn valuation, you can’t task 1 single developer who is able to fix these basic usability issues that have been a problem for years?