[feat] Support Multi-Repository Workspaces (VS Code-style Multi Root Workspace) #5354

Activity

1. OnGets45

   added

   enhancementNew feature or requestNew feature or request

   on Jun 25, 2026
2. Kitenite

   added

   Feature

   and removed

   enhancementNew feature or requestNew feature or request

   on Jul 10, 2026
3. mrTurkay commented on Sep 3, 2026

   

   mrTurkay

   on Sep 3, 2026

   More actions

   +1 on this — hitting the same wall running full-stack coding agents (e.g. Claude Code) from a parent folder that isn't itself a git repo, e.g.:

   parent-folder/
   ├── frontend/   (own .git)
   └── backend/    (own .git)
   

   Superset currently requires the workspace root to be a git repo, so the only workaround is a dummy git init in the parent — which breaks clean VCS assumptions and worktree isolation for both sub-repos.

   To make this useful for agent workflows specifically, I think two things need to hold:

   1. Allow opening a directory that isn't a git repo itself but contains nested git repos (this issue).
   2. Detect the nested repos and keep branch/worktree isolation scoped per sub-repo, while still letting an agent read across the whole parent tree for holistic context (backend API contracts + frontend implementation together).

   Related: #5796 covers the diff-view side of nested-repo detection in detail, and #1003 (closed, folded into #5594) describes a similar "monorepo of repos" layout, though it assumes the root itself has its own .git — this issue's case is the root has none at all.

   Happy to help discuss the design or contribute a PR if there's interest.
4. harshithmullapudi commented on Sep 30, 2026

   

   harshithmullapudi

   on Sep 30, 2026

   Collaborator

   More actions

   #7699 -- We are working on this here, should have update in the coming week or so