The layout keeps changing each time i reopen the cursor ide the sized of panels that i left out with are not saved its annoying each time to resize everything how i like it
Steps to Reproduce
restart ?
Expected Behavior
The layout should be saved and restored on how it was left out when quitting the app
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
when I’m chatting with an agent, when it responds it widens it’s window, again and again, until it’s as wide as it can get, and the sidebar is way too narrow to use. it doesn’t matter how often I resize it, it just keeps self-widening, making it hard to use another agent in the sidebar.
Steps to Reproduce
type in chat and submit
Expected Behavior
it should NEVER auto resize a window, ever
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
The thing that confuses me, is I think it was 2.0.40 that it stopped being an issue for me. Why is it still an issue for so many people?
This is one of the things about bugs in Cursor, and the nature of how they affect different groups of people. I haven’t been able to use @Docs for over two months now. However, some people seem to be able to use that feature today. Other people have mentioned losing the ability to use @Docs just a couple of weeks ago.
That is extremely strange. Why would bugs affect people at different times, across different versions, especially when an explicit fix was made, IIRC, in 2.0.40? There is a level of robustness and consistency in design and implementation, that could alleviate these extremely strange bugs that appear to be very difficult to track down and resolve. It might also help prevent repetitive regression with each new version of Cursor.
I’ve also been experiencing this issue mostly with the File Explorer sidebar. I’m not 100% sure, but IIRC this started happening arount the introduction of Agents workspace.
This is EXACTLY my issue, it resizes ALL THE TIME and I’m having this issue with the “file explorer” left panel, which is even more annoying since I’m only doing normal vscode workflow not even using much of the AI / Agent features.
++I am having this same issue, if any new file opens or any plan file opens, Panel will reset always, haven’t been fixed since Cursor 2.x version ! @deanrie
Under certain conditions, the left panel of Cursor’s IDE automatically resizes itself to 50%. Manually resizing it becomes tiresome after it happens multiple times in a session.
Steps to Reproduce
Manually resize the left panel to the size you want, let’s say 20% or so of the screen.
Maximize the right panel (for me that’s usually Terminal) so that it fills up the rest of the screen.
Open a file in the left panel.
Observe that the third panel is opened properly with the file that was selected, but the left panel is now 50% of the screen rather than whatever size you set in step 1.
Expected Behavior
The left panel should always stay the size that I set it.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
This is probably closely related to the bug that crashes macOS when coming out of sleep mode after grabbing 2x the available memory on the machine. My machine has 64GB RAM. Just before crashing, I’ve seen Cursor taking 105GB RAM. Every other app is paused… and there’s no coming back, even if you manage to Force Quit Cursor.
Mostly my “Timeline” section is always fully expanded, and the file browser is super short
it doesn’t remember either that the Timeline seciton’s height, or that it was minimized
I wanted to add my latest experiences here. I, too, am now experiencing the “Timeline” section always expanding. It started within one of the recent updates, not sure which, as I thought somehow I was triggering the issue, but it is clear this is NOT something I am doing and the Timeline section is constnatly expanding to take up most of the vertical space in the left-hand panel. I prefer that my project panel take up most ofthe space most of the time, however fundamentally, the UI should not be messing with these panels automatically at all.
This is a basic QC issue. You guys really need a team, of at least a couple people, to be performing constant QC checks and maybe implement automated QC testing to prevent these kinds of issues from leaking through to your production releases. Its clear Cursor is about as vibe-coded as it gets, and that there is very little if ANY quality assurance checks on your releases. This is to the DETRIMENT of your users, and of all the issues you guys have right now, introducing some level of quality assurance is really essential if you guys want to build a reputation of anything other than: “Oh, yeah, Cursor is just vibe-coded junk.” Because that is kind of the sentiment that is seeping in here…the sheer volume of half-baked new features, buggy and forgotten existing features, and repetitive regressions lends to no other assumption. :\