The editor layout won’t stay how I want it. See steps to repro. Version 3.0.13
This is so frustrating. I’m going back to 2.x.
Steps to Reproduce
start in editor mode
close the agent panel
switch to agent mode
switch back to editor mode
bug. notice the agent panel appears again
Expected Behavior
the agent panel should stay hidden.
Additionally, when I move the “main panel” to the right, it should stay there.
Operating System
Windows 10/11
Version Information
Too late. Already uninstalled and I’m re-installing.
v. 3.0.13.
This isn’t the only complaint I’ve seen like this. Please prioritize this! I don’t think you realize just how jarring of an experience this is for people who still want to look at code and not just talk to agents.
It’s frustrating that workbench.sideBar.location doesn’t help either. That’s a separate but related issue.
Sadly, we don’t have a public tracker for individual bugs. But the team is aware of both issues, the agent panel and the sidebar position. I can’t share an exact ETA yet, but your report really helps us prioritize this, especially since it’s clearly blocking day to day work.
If everything is fine on 2.x, sticking with that for now is a totally reasonable workaround until we ship a fix. We’ll update the thread when we have news.
As @emragins reported, it is not only the sidebar location which does not work.
In Agent mode → I close the agents list bar → only to keep the Chat visible → switching to Editor then to Agent again → agents list sidebar is visible again
In Editor mode → I close the Chat (I only want file explorer sidebar) → switching to Agent then to Editor again → Chat is always displayed again
In other words closing agents list sidebar in Agent and closing Chat view in Editor → these are not kept on switch, they are always reset (agents sidebar always reappears in Agent, and Chat always reappears in Editor) - and spoiler alert - I switch a lot :))
Cursor is a great product, I really appreciate the vision with Glass and moving forward the vision, but this is a bug which disrupts the workflow in a big way.
And I am speaking from the perspective of someone who uses it a lot - this month I reached $1500 in usage → $1000 paid on top of the $200 Ultra plan.
Hey, thanks for the update and the video. Since the old ticket was closed, we’ve made changes in the layout code, so I want to verify this on the latest build.
Can you update to the latest version via Help > Check for Updates, it should be 3.3.30+ and retest the same Cmd+E scenario? I’m interested in both cases:
Editor mode: hide Chat, switch to Agent and back
Agent mode: hide the agents list, switch to Editor and back
If it still resets on the new version, please share your version from Help > About and a short recording here, and I’ll file a new issue with an up-to-date repro.
I’m still sitting on version 2.6.22 because of this issue; as I really do not like the way this bug interrupts my workflow.
It’s also unfortunate to see that the cursor team doesn’t really seem to care to fix it… or re-test the product themselves rather than asking the community to do it. I like cursor, but I can no longer recommend the product and it’s unlikely I’m going to renew my subscription due to this bug.
Hey, I get the frustration, and thanks for coming back with an update anyway.
Unfortunately you’re right that the bug is still reproducible. Mihai confirmed it in the 3.4.20 thread, and I’ve opened a new internal issue that links to that thread and the repro video. The old ticket was closed earlier because we thought a fix in the layout code would cover it, but as you can see, it didn’t. So your question is totally fair.
To be honest, I don’t have an ETA for a fix, and I won’t promise we’ll fix it soon. That wouldn’t be fair to you or the team. What I can say is the issue is now tracked with an up to date repro, and reports like yours and Mihai’s help with prioritization. If there’s any movement, I’ll post an update here.
I get that staying on 2.6.22 isn’t ideal, and the subscription decision is up to you. If anything changes with the fix, I’ll let you know in the thread.