I have lost the visibility for my git submodules in the git tab. In the previous version this worked OK.
Just open a git project with a git submodule
MacOS
Version: 1.4.2
VSCode Version: 1.99.3
Commit: 07aa3b4519da4feab4761c58da3eeedd253a1670
Date: 2025-08-06T19:23:39.081Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0
Hi the submodule will come back there if you open a file in the submodule, but yes we changed the settings to match what vscode does and only show the main repo until you do anything in the submodules
If you like the old behavior you can change the settings git.autoRepositoryDetection and git.detectSubmodules
This does not restore original behavior. These settings do not work. Original behavior is you open a project, and immediately you open the git panel and can see all submodules IMMEDIATELY, with 0 config or settings changes. The absolute best we can do after this update is enable “git.detectSubmodules” and ignore “git.autoRepositoryDetection” (Since it does the same behavior regardless of what it is set too). Then with that you can get it to where you then have to go and navigate to EACH submodule, and open a file and it will show finally in the git panel for that specific submodule, but I do not know a single person with submodules that wants it to work like that…
No idea why you guys decided to arbitrarily change this for no reason when no one was even asking, but would be greatly appreciated if you guys could revert it back to the old behavior.
I just put these settings back and restarted cursor and saw all of our submodules show up immediately as it used to be, did you restart cursor after changing them?
Yes changing “detect submodules limit” fixes it. I updated my post in another bug report post to include this fix, but “detect submodules limit” is not documented anywhere regarding this issue, by Cursor, nor VSCode.
The main issue itself I think stems from the fact that after the update, this value seems to be force set to 0 for some reason regardless of its previous value, and then there is just 0 mention of this setting anywhere. Even googling this setting you get basically 0 docs for it, let alone anything in the recent VSCode or Cursor update notes to indicate why this was changed.
Let me see if there’s better defaults here I can set so it’s easier to go back to the old behavior. Sorry for the hassle here
Ok next patch release will revert the submodules limit config change, verified that all you have to do is check “Git: Detect submodules” and they will all show up (after restart)
Git submodules are not visible in the source control panel of Cursor, but it works in VS Code for the same project.
Create Git submodules in a project and open the project in Cursor.
Windows 10/11
Version: 1.4.2 (user setup)
VSCode Version: 1.99.3
日期: 07aa3b4519da4feab4761c58da3eeedd253a1670
Electron: 2025-08-06T19:23:39.081Z
ElectronBuildId: 34.5.1
Chromium: undefined
Node.js: 132.0.6834.210
V8: 20.19.0
OS: 13.2.152.41-electron.0
No - Cursor works, but with this issue
its settings in vscode
@st_liu have a look at this current thread. I merged your post here as it is relevant and contains answers.
it worked OK for me now, thank you!
