Cursor source control tab issue

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

I use a multi-repo project. When the project is opened, the source-control tab stooped display all the repos and the changes.

Steps to Reproduce

Open a folder with sub-folders, each is a diff repo.
Check the source control tab.

Expected Behavior

All the repos should be displayed, with changes (if applicable) , branch name and status etc…

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.64 (Universal)
VSCode Version: 1.99.3
Commit: 25412918da7e74b2686b25d62da1f01cfcd27680
Date: 2025-11-06T04:35:14.424Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Additional Information

You can contact me via email to get more info or screens.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. This is a known issue after recent updates.

Solution: re‑enable the “Git: Detect Submodules” setting

  • Open Settings CMD + ,
  • Search for git.detectSubmodules
  • Make sure it’s enabled (not set to “false”)

This setting sometimes gets disabled during updates. Let me know if turning it back on fixes the issue!

10x @deanrie
Unfortunately this have not fixed the issue.
The option was "false” (checkbox unselected), but also after marking it as “true” and restarted the IDE the source control tab is empty.

Thanks for confirming. Since git.detectSubmodules didn’t help, let’s check a few more settings:

Please verify Cmd + , → search each:

  • git.autoRepositoryDetection - should be true or openEditors
  • git.repositoryScanMaxDepth - try setting to 3 or 4
  • git.enabled - confirm it’s enabled

Also, please share:

  • Any errors in the console? (Help → Toggle Developer Tools → Console tab)
  • Does this happen with a fresh workspace?

This will help determine if we need to escalate to the team.

Hi @deanrie
git.autoRepositoryDetection - is set to openEditors. no change.
git.repositoryScanMaxDepth - was set to 1, changed it to 4.
git.enabled - is set to true (checked). no change.

This happens also when opening other folders / projects where I have multiple repos.

There are many errors on the console:

Thanks for the extra info. Here are a few more checks:

  1. Workspace Trust
  • Click the shield icon in the bottom-left status bar
  • Ensure the workspace is “Trusted” (not Restricted): Workspace Trust
  1. Git Path
  • Cmd+, → search “git.path”
  • Leave it empty to use system Git, or set a valid path: /usr/bin/git
  • Verify in Terminal: git --version
  1. Clean Settings Test
  • Cmd+Shift+P → “Preferences: Open User Settings (JSON)”
  • Back up the file, then remove all git.* settings
  • Reload the window
  1. Fresh Profile Test
  • Run:
    /Applications/Cursor.app/Contents/MacOS/Cursor --user-data-dir=/tmp/cursor-test
  • Open your project and check if Source Control works
  1. Check Logs
  • Cmd+Shift+P → “Git: Show Git Output”
  • Share any errors you see

If this doesn’t help, a full reinstall of Cursor might be needed. Let me know what you find.

Hi @deanrie

  1. Workspace is trusted.
  2. Git path is an empty string.
  3. removed all git.* for the settings, no change, still do not see the source control as expected.
  4. run the command, no change, still do not see the source control as expected.
  5. only error i can see is “[info] error: No such remote ‘origin’“.
  6. tried to uninstall an re-install the IDE. no change, still do not see the source control as expected. but all the settings (like proxy and mcp servers) were kept, so i don’t know if it was a “full” removal including all settings and caching.

Thanks for the thorough testing. Since the standard diagnostics didn’t help, let’s try two more steps:

Test without extensions:

  • Run from the terminal: cursor --disable-extensions
  • Open the project and check if Source Control appears

The console error “No such remote ‘origin’” might be key - does this happen across all repositories in your workspace or only some? If some repos don’t have a remote origin, that could explain why they’re not showing up.

For a clean reinstall of Cursor, do the following:

  • cd ~/Library/Application\ Support
  • mv Cursor Cursor.old

Let me know how it goes

Hi @deanrie
Unfortunately the status is the same even after doing the above.

  1. Running w/out extenstion → same issue.
  2. Deleting cursor and renaming cursor under application support, re-installing it → same issue.

If I open each repo as a “stand alone” (i.e open the sub-folder and not the “parent” one), I can see the source control with all the data. So i don’t believe there is an issue with remote origin.

I have also created a new parent folder and cloned some repos into it, opened it as a new project, and now i see a message that the folder currently doesn’t have a git repository.

Thanks for the thorough testing - really appreciate your patience. I think I see the confusion, and what you’re seeing is expected behavior.

When you open a parent folder with multiple git repositories, Cursor/VS Code won’t automatically show all nested repos in Source Control. Instead, use a multi-root workspace.

How to set up a multi-root workspace:

  • File → Add Folder to Workspace (select the first repo)
  • File → Add Folder to Workspace (select the second repo)
  • Repeat for each repository
  • File → Save Workspace As… (save as a .code-workspace file)

Now, when you open that workspace file, all repos will appear in Source Control with their own sections, branches, and changes.

This is the recommended way to work with multiple repositories in VS Code-based editors. Does this fit your workflow?

@deanrie
Yes! Thanks for all your assistant.

I must say that I never worked like this, years of working with VSCode, and recently with Cursor (until latest update), I have always opened the parent folder with all the repos as sub-folders. For example open terminal in the root folder and type cursor . or code . and start working. I never had to work with a dedicated workspace. VSCode still works as before.
But at least now I can work with the project properly set up.

Thanks again!

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.