# Git in Multi-root repos are not recognising

**URL:** <https://forum.cursor.com/t/git-in-multi-root-repos-are-not-recognising/163104>\
**Category:** Bug Reports\
**Tags:** performance, nightly\
**Created:** [June 12, 2026, 10:02am UTC](https://forum.cursor.com/t/git-in-multi-root-repos-are-not-recognising/163104 "2026-06-12T10:02:09Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [June 12, 2026, 10:46am UTC](https://forum.cursor.com/t/git-in-multi-root-repos-are-not-recognising/163104/5 "2026-06-12T10:46:27Z")

</div>

Hey, this is a known issue. Source Control can sometimes get stuck on “Scanning workspace for Git repositories…” when you have multiple repos inside the same parent folder.

The most reliable workaround right now is to disable full directory scanning:

1. Settings `Cmd+Shift+,` then search for `git.autoRepositoryDetection`
2. Set it to `openEditors`

This skips the recursive scan of subfolders, which is what causes the freeze. If your repos don’t get picked up automatically after this, open any file from the repo you want and it should detect it.

You can also try restarting the built-in Git extension Extensions \> `@builtin git` \> Restart and tweaking `git.repositoryScanMaxDepth`.

We’ve logged the bug, but I can’t share an ETA for a fix yet. Let me know if the workaround helped. Related threads for context: [Source Control hangs on “Scanning workspace for Git repositories...”](https://forum.cursor.com/t/source-control-hangs-on-scanning-workspace-for-git-repositories/157143) and [Scanning folder for Git repositories](https://forum.cursor.com/t/scanning-folder-for-git-repositories/159767).

---

_[View the full topic](https://forum.cursor.com/t/git-in-multi-root-repos-are-not-recognising/163104)._