You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ideally to combine multiple levels into the description of there is only one repo
Why this matters
Having a lot of repositories to work on right now is hard to find the right one to continue.
When having to work on a lot I always have a directory structure where those repositories are checked out on that specific machine. It would therefor be great to simply tap into this structure.
Smallest useful scope
Having a manual 2nd group level that can be assigned to any of the current groups
Alternatives considered
I don't know a reasonable workaround
Risks or tradeoffs
As this is only relevant when there are a lot of repositories it should be gated behind a setting - ie multilevel groups is disabled per default, then manual as a second option and directory based as a third.
enhancementRequested improvement or new capability.needs-triageIssue needs maintainer review and initial categorization.
1 participant
Converted from issue
This discussion was converted from issue #3722 on August 15, 2026 09:43.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Before submitting
Area
apps/desktop
Problem or use case
I am working on 80+ different repositories, some of them with the same directory name. ie I have 5 "api" repositories.
Differentiating them is right now basically impossible - by best guess is right now if I remember the previous conversation and know it by this.
Further it would be great to navigate in a way that I have already as a structure to differentiate the different repos.
Proposed solution
With a new option to add grouping above the current chat grouping, it would be possible to differentiate the different routes.
ie having the following:
would first look for all paths and find the common root of
/home/user/workspaceand then show a tree like:ideally to combine multiple levels into the description of there is only one repo
Why this matters
Having a lot of repositories to work on right now is hard to find the right one to continue.
When having to work on a lot I always have a directory structure where those repositories are checked out on that specific machine. It would therefor be great to simply tap into this structure.
Smallest useful scope
Having a manual 2nd group level that can be assigned to any of the current groups
Alternatives considered
I don't know a reasonable workaround
Risks or tradeoffs
As this is only relevant when there are a lot of repositories it should be gated behind a setting - ie multilevel groups is disabled per default, then manual as a second option and directory based as a third.
Examples or references
No response
Contribution
All reactions