Cursor activity bar can't be hidden

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Activity bar in the latest update can’t be hidden now, it ruins most/all of the configuration setups done by people.

Either create your own ide or support vscode configurations.

Steps to Reproduce

Latest update, activity bar can’t be hidden

Expected Behavior

To hide the activity bar

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.40 (Universal)
VSCode Version: 1.99.3
Commit: a9b73428ca6aeb2d24623da2841a271543735560
Date: 2025-10-30T04:12:35.564Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

For AI issues: which model did you use?

IDE

Does this stop you from using Cursor

Yes - Cursor is unusable

8 Likes

hi @hmeng and thank you for the detailed bug report. I will forward it to the team.

1 Like

thanks! here is the json property:

  "workbench.activityBar.location": "hidden",
1 Like

I would really appreciate having the option to hide the activity bar for a cleaner UI. I primarily navigate using the keyboard and have been hiding the activity bar for several years. Losing that flexibility has been a bit inconvenient for me. I believe this action has been made so that agents/editor view is always visible.

2 Likes

Same here, this is just bad UX from them. Especially if you use cursor as full screen (e.g on mac and swiping) like me, you don’t even see the agents/editor buttons.

They should just create a keyboard command to switch between agent/editor or a right click>option to switch for non keyboard heavy users. I have a switch keyboard option between the two and it tends to be glitchy:

  • The width of the agent section is set by a fixed amount instead of scaling/% based on the screen size → css problem,

  • This also includes the explorer view, sometimes if you refresh vscode and do a switch, it doesn’t remember the previously set width.


If a PM from cursor is reading this, it’s important to preserve the flexibility of vscode for custom setups, unless the targeted ICP is a random vibe coding donnie who doesn’t even know how cursor works. If that’s the case, let us know.

@condor if you know the PM at cursor responsible for managing this, I’m more than happy to jump on a call for like 10-15minutes to explain/show.

Went crazy trying to find out why this broke when I’ve had it hidden for so many years. Hope theres a fix coming asap

1 Like

@condor do we have an ETA for this to be fixed?

@hmeng I do not have a timeline at this time as we are overall looking at all feedback and improvements necessary.

1 Like

Well this is an obvious bug → it should be fixed.

If it’s a breaking change to the setup, maybe try feature flags that’ll be controlled by the users and gain feedback that way?

Regardless of the change: flexibility to change >> breaking overnight deployments

Thank you for your feedback, I have reported the issue to the team already.

1 Like

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Before we were able to set the activity bar location to “hidden” to hide it but now it seems like it’s not an option anymore? Are we not able to hide it now?

Steps to Reproduce

Set workbench.activityBar.location setting to “hidden”

Expected Behavior

Hides the activity bar

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.40 (Universal)
VSCode Version: 1.99.3
Commit: a9b73428ca6aeb2d24623da2841a271543735560
Date: 2025-10-30T04:12:35.564Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I tried adding “workbench.activityBar.visible”: false to my settings.json, but it keeps getting removed after a while.

Steps to Reproduce

Added “workbench.activityBar.visible”: false to my settings.json, but after using Cursor for a while, it gets removed.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.43 (Universal)
VSCode Version: 1.99.3
Commit: 8e4da76ad196925accaa169efcae28c45454cce0
Date: 2025-10-30T18:49:27.589Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The latest update completely ignores the settings “workbench.activityBar.location”: “hidden”

Steps to Reproduce

Reopen Cursor

Expected Behavior

This should hide the activity bar

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.43 (user setup)
VSCode Version: 1.99.3
Commit: 8e4da76ad196925accaa169efcae28c45454cce0
Date: 2025-10-30T18:49:27.589Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26200

Additional Information

Bro, please don’t create more bugs than features on each release.

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

Bro, I just didn’t get it how a serious bug like this even happens.
This is crazy bad, crazy bad.

4 Likes

I agree, quite important to preserve the flexibility of vscode.

Hopefully they’ll fix the css issues/remembering %s of the layouts etc, but that’s nitpicking/ux details..

Shocking this was removed. The activity bar icons are a huge waste of pixels for those of us on small screens.

image

@deanrie @condor could we prioritize the bug fix here?

The reason why I’m asking, usually stuff like this would get lost somewhere in the backlog - but it’s quite important

1 Like

Hey, the team is already working on it.

2 Likes

A fix for this is going out in the next release! Should be available later today / tomorrow

5 Likes

thanks! @austinp

did you guys manage to fix the % memory fixes when switching between editor/agent tabs? it doesn’t remember the previous setting upon switching and if switching between different screen sizes, it “remembers” pixels not %/relative numbers