I’ve given a list of them below.
The theme for most of these is that it feels like features are being whacked on top of each other, perhaps by different people within Cursor, without anyone looking at overall cohesion between them (e.g. ‘Composer’ and ‘Chat’), or VSCode (e.g. Cursor chat hijacks VSCode keyboard shortcuts).
Given that half the battle of Cursor with other Coding IDEs is UX, these feel like worthwhile things to improve.
UX/UI improvement suggestions (ranked):
- Similar commands should maintain consistency in being reversible
e.g. currently ctrl + L x2 opens and closes chat. But ctrl + i x2 doesn’t open and close Composer - Give an option to put Composer back in the right side bar alongside Cursor Chat and Cursor Review
- Prioritise explaining an existing feature over releasing a new one
this has already being requested extensively: Cursor team, can you please share a demo vid with each feature release? - Explain what something does at the point where a user finds out about it. For example explain ‘Always keep composer in bound’ setting in Cursor > Beta, at that point in the UI (maybe with a tooltip and screenshot?). I’ve learnt what it is now, but it was annoying to find out.
- User interface shouldn’t go outside the bounds
Composer sometimes extends above the Cursor window. I don’t think it ever should - When the user submits text it should disappear from the text entry field.
See WhatsApp for a good example - Make commands consistently available. For example the /reference files featuring Composer is great, so why is it not available in the normal ctrl + L chat!
- Make commands consistent. For example why does Composer have a hashtag to refer to files but chat doesn’t.
This makes it very hard to learn new features - Don’t hijack the keyboard shortcuts when in ‘Cursor’ mode
Example problem: I press ctrl + L to get chat. I then press my ctrl + b keyboard shortcut to minimise the left sidebar. It no longer works! I need to click out of ctrl + L. This is infuriating! - When scrolling through already sent messages it should be clear to see what the user has entered and what the system is entered
See WhatsApp for a good example - Composer escape should always do the same thing, but sometimes it minimises, and sometimes it gives focus to a background tab.
- The system should identify when it hasn’t worked for some reason and then let the user know. All too often nothing is happening but it doesn’t really make it clear to the user and the user needs to figure out and decide when to try again.