I sometimes work with multiple projects in the same parent directory in coordination. In such a case, the Source Control view sometimes shows all nested repos of this parent directory and their changes correctly, sometimes only shows part of the repos which are all those detected and selected in View & Sort > Repositories, and sometimes it doesn’t detect any repo at all and shows “Initialize Repository” for the parent directory.
PS: I used VS Code a lot and it didn’t have this issue.
Steps to Reproduce
As above, create a directory with multiple nested Git repos and open it with Cursor.
Hey there! Thanks for reporting this. This is a known issue we’ve seen when you open a parent folder that contains several nested Git repos: the Source Control panel’s initial repo scan can be racy, so detection comes out differently across launches (all repos, some, or none).
A few things that reliably sort it out:
Only some repos showing: they’re usually hidden rather than undetected. In the Source Control panel, open the ... menu → View & Sort → Repositories and re-enable any that are unchecked.
No repos / “Initialize Repository”: re-trigger the scan with Cmd+Shift+P → Developer: Reload Window, or restart the built-in Git extension (Extensions → search @builtin git → Restart).
Repos nested deeper than one level: raise git.repositoryScanMaxDepth (default is 1). Heads up: the per-folder value is only applied when the workspace is Trusted, otherwise the global value is used.
If the scan keeps coming up short, setting git.autoRepositoryDetection to openEditors skips the recursive scan entirely; repos then show up as you open a file from each. The trade-off is you lose the automatic up-front listing of every repo.
We’ve logged this and it’s actively being tracked, though I don’t have an ETA to share yet. Let me know if any of the above helps!