cursor Source Control Tab Doesn't Showing Counter Badge

Screenshot:

Windows 11 Pro 22H2
If there is any changes in the files and the git repo is initialized it doesn't show the counter badge of the number of file changes.

Sep 11 '23 05:09 salaarkhan-dev

Not showing for me as well

Sep 12 '23 02:09 pedrotmr

+1 Same here, but on latest MacOS Sonoma 14.3.1, Mac studio m1 max

Mar 07 '24 14:03 edheltzel

I had the same issue. So I tried to change the Activity Bar orientation to vertical. What this did, was disable the activity bar completely and take my setting from vs code and thus shows the number of files changed counter.

Before:

After:

Aug 13 '24 15:08 RahulReddy75

I'm having this issue as well. Toggling between horizontal and vertical with the workbench.activityBar.orientation setting does not fix it for me.

The badge does show in vertical orientation, however.

Aug 13 '24 23:08 EthanDM

That is a major issue for me. My commits were getting way bigger as I kept forgetting to do it.

Reverting to vertical did do the trick for me.

Sep 07 '24 13:09 igor9silva

@EthanDM you can right click it

Sep 07 '24 13:09 igor9silva

  "workbench.activityBar.orientation": "vertical",
  "workbench.activityBar.location": "top"

this fixed it for me

Sep 12 '24 08:09 AmanVarshney01

  "workbench.activityBar.orientation": "vertical",
  "workbench.activityBar.location": "top"

this fixed it for me

"workbench.activityBar.orientation": "vertical"

Sep 19 '24 06:09 refanbanzhang

macos 14.7, cursor Version: 0.41.3, VSCode Version: 1.91.1 doesnt work for me either.

Oct 09 '24 06:10 alsotang

this is still not fixed by defualt

Dec 03 '24 20:12 Vanekkk1

0.43.6 macos Still not fixed

Jan 03 '25 02:01 whcxxb

related issue: https://github.com/getcursor/cursor/issues/771

Jan 04 '25 12:01 AMD-NICK

i hade same issue.

Version: 0.44.9 VSCode Version: 1.93.1 Commit: 316e524257c2ea23b755332b0a72c50cf23e1b00 Date: 2024-12-26T21:58:59.149Z Electron: 30.5.1 Chromium: 124.0.6367.243 Node.js: 20.16.0 V8: 12.4.254.20-electron.0 OS: Darwin arm64 24.2.0

Jan 04 '25 18:01 dotKa

Same.

Version: 0.44.11 VSCode Version: 1.93.1 Commit: fe574d0820377383143b2ea26aa6ae28b3425220 Date: 2025-01-03T07:59:06.361Z Electron: 30.5.1 Chromium: 124.0.6367.243 Node.js: 20.16.0 V8: 12.4.254.20-electron.0 OS: Linux x64 5.15.0-130-generic

Jan 19 '25 11:01 aminahbl

Same here

Version: 0.45.15 (Universal) VSCode Version: 1.96.2 Commit: 73dd83bb6f8e3a3704ad8078a8e455ac6d4260d0 Date: 2025-02-22T10:15:54.481Z (1 day ago) Electron: 32.2.6 Chromium: 128.0.6613.186 Node.js: 20.18.1 V8: 12.8.374.38-electron.0 OS: Darwin arm64 24.3.0

Feb 23 '25 21:02 birobirobiro

the original post was on windows, but it's also happening on macOS. The counter doesn't show whereas in VSCode it does show... Cursor imported my settings from VSCode so I shouldn't have to set up different settings right?

Feb 26 '25 23:02 mesqueeb

try these settings

Feb 27 '25 04:02 amit-tai



{
  "workbench.activityBar.location": "default",
  "workbench.activityBar.orientation": "vertical"
}

Steps to Apply These Settings:

Open Cursor AI.
Press Command + Shift + P (or Ctrl + Shift + P on Windows/Linux) to open the Command Palette.
Search for "Open Settings (JSON)" and select it. (settings.json)
Add the above lines to your settings.json file.
Save the file and restart Cursor AI for the changes to take effect. (reload window)

Mar 24 '25 19:03 dharmveer97

I don't know how to achieve the same result as in VS Code. The horizontal position and badge count. I think it used to work. With vertical position it works fine.

In VSCode:

Jun 09 '25 19:06 kkot

    "workbench.activityBar.location": "top",
    "workbench.activityBar.orientation": "vertical"

seems to not work for me:

I mean, it works, but not the way I imagined 🤦

Jun 17 '25 08:06 przemoch-dev

I want horizontal orientation as well, why can it only work in vertical orientation?

Jun 17 '25 16:06 mesqueeb

    "workbench.activityBar.location": "top",
    "workbench.activityBar.orientation": "vertical"
seems to not work for me:

I mean, it works, but not the way I imagined 🤦

Got exactly same problem. Anyone got the fix?