On Cursor’s Agent window, I have 4 different repositories that all point to the same GitHub repository. However, once I add them, they are merged together in the sidebar under the single GitHub repository name.
This is not the expected behavior, because I need to easily identify each workspace and open chats within them separately.
Is there a workaround to group items in the sidebar by OS folder instead?
Steps to Reproduce
Clone the same GitHub repository four times into different local folders. Then start chatting or clicking within each folder’s chat.
All chats end up merged under the single GitHub repository name in the sidebar. This makes it very difficult to identify which workspace you’re in or to open a new chat for a specific repo.
Expected Behavior
Sidebar should have a grouped by “Os Folder” not by “Github Project” behavior
Hey, thanks for the report. This is the current behavior in the Glass layout. The sidebar groups chats by the git remote URL, not by the local folder. So if multiple clones point to the same remote, they’ll show up under one section.
At the moment, this limitation is blocking our team from migrating to the “Glass” UI. We need to be able to easily create multiple chats within a specific folders and clearly track which chats are active or completed for each folders.
+1 on this. I have on ssh remote multiple checkouts of the same repo (I also use separate dev containers for them). I legitimately thought this was a bug that the chats were getting clobbered in glass.
Same here. I was so excited about the new unified cursor 3 layout. Is that what “glass” is? It’s pretty much unusable though, even for git worktrees. Everything just gets grouped into the same thing in the sidebar, and then once I start an agent I have no idea what folder/worktree/project I’m in. Sort of makes the entire thing DOA, and I’ll have to go back to the editor view and managing multiple different windows again for now. Darn.
IMO they should be grouped by folder or actual workspace, and even let you open a workspace by .code-workspace file.
Ok I got a hack working! In the sidebar I selected “Group by” Environment, and then added some “fake” hosts to my ~/.ssh/config that just map back to localhost:
Host host1
HostName 127.0.0.1
User myuser
ForwardAgent yes
Host host2
HostName 127.0.0.1
User myuser
ForwardAgent yes
Host host3
HostName 127.0.0.1
User myuser
ForwardAgent yes
This works for now, but hopefully they’ll still improve this in the future.
