In Cursor v2.3, the Command Center no longer appears in the top bar.
As a result, it is no longer possible to display or use the forward/back navigation buttons (history navigation) in the top bar.
This functionality worked correctly in Cursor v2.2 with the same settings and workflow.
This appears to be a UI regression introduced in v2.3, where the top bar no longer exposes the Command Center entry point.
Steps to Reproduce
Install and launch Cursor v2.3.
Open any project or workspace.
Look at the top bar / title bar area.
Attempt to locate the Command Center or enable navigation-related UI entries.
Compare with Cursor v2.2 under the same environment.
Operating System
Windows 10/11
Current Cursor Version (Menu â About Cursor â Copy)
version: 2.3.26ďźNo more, because Iâve already uninstalled the buggy version.
Iâm facing this too and I just updated my Cursor. Before which they were present.
Version: 2.3.29 (Universal)
VSCode Version: 1.105.1
Command Center: enabled
Custom Title Bar Visibility: auto
OS: macOS 14.5
Even after following the steps mentioned by @deanrie I donât see the navigation arrows. I use these a lot and this issue definitely stops me from using Cursor.
Experiencing the same issue, the above mentioned steps donât help. Command center setting was already enabled, switching it off and on, restarting, nothing helped. Itâs a regression in 2.3.29
My settings:
Version: 2.3.29 (Universal)
Command Center: enabled
Custom Title Bar Visibility: auto
OS: Windows 11
Adding my comment, it makes the IDE very inconvenient to use without being able to easily traverse calls. You should absolutely be able to use the coding agent, and inspect the work easily and go back and forth through functions calls.
Ironically when I have settings tab open I can see the navigation come back at the top but as soon as I close the settings tab it disappears again. So definitely seems like something isnât working correctly here.
3. Unfortunately I actually canât replicate the settings causing it to appear bug from before, however, Iâve noticed that with the file explorer on the left and agent on the right it doesnât show but the other way around it does, see below for example.
Hitting cmd + e does infact solve my issue, but I am still confused as to why the above screenshot is highlighting Editor which makes me obviously assume thatâs the view iâm in? but when I use cmd + e nothing is highlighted? (see below)
Additionally you said that in agent view navigation doesnât work but my above screenshots, where I was in agent mode by accident, show that it appears when the agent is on the left (and works!) but doesnât appear when the agent is on the right?
So either it shouldnât work at all in which case them showing when the agent is on the left is a bug or they should work and it not showing when the agent on the right is a bug?
About the confusion between Agent vs Editor view, youâre right, itâs genuinely confusing. When you see a checkmark on âEditorâ in View > App Layout, that means you picked the Editor layout (donât confuse this with the mode youâre currently in). To switch to code editing mode (where navigation works), press Cmd + E.
Now, about what you noticed, yeah, thatâs a real bug. The navigation buttons work in the latest Cursor release in Agent view. We brought them back because a lot of users requested it. But they show up when the agent is on the left, and disappear when the agent is on the right. The team already knows about it and is working on a fix.
Guys, you should really focus on not breaking VSCode, youâre barely better than other tools, if you keep breaking the basic features people are just gonna leave.. Settings is enabled for both user and workspace, still no command center and debugger dock is gone, need to switch to floating layout in order to even be able to debug properly. When i restart my Cursor itâs back for a second and then it is gone again, definitely nothing wrong with my config and everything wrong with the latest version.
Okay so I had picked the âeditorâ layout inside the âAgentâ mode, is that correct?
But this is where iâm getting further confused, in this reply to me youâre telling me its a but because youâve brought them back due to high user requests, but not 1 reply before this one you told me that they shouldnât be there because theyâve been removed, and only when I questioned it did you then tell me that actually they should be there again and itâs a bug?
I suppose my problem is solved now, although some others in this thread are having further issues but I just wanted to raise the feedback that 1. the editor within the agent mode is confusing, and 2. it seems like there is a bit of confusion about what should and shouldnât be present regarding this feature and new releases and that could do with being ironed out prior to further support requests coming in iâm sure!
Either way, thank you for helping me understand and being patient with me when at the end of the day the initial issue was purely user (me) error due to not being in the right mode!
