Worktree chats no longer get their own sidebar tab — all chats grouped under main repo (Glass / recent update)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

  • Cursor IDE

Describe the Bug

Before a recent Cursor update, when I opened a worktree as a folder, it appeared as a separate entry in the sidebar, so I could group chats per worktree. After the latest update, chats from worktrees are grouped together under the main repository tab in the sidebar instead of staying separated by worktree. I can no longer keep parallel worktree conversations organized the way I used to.

Steps to Reproduce

  1. Open your main repository in Cursor (note the sidebar / chat context for that folder).

  2. Open a git worktree as a separate folder (e.g. File → Open Folder to the worktree path, or however you normally open Cursor’s worktree under ~/.cursor/worktrees/<repo>/...).

  3. Start or open Agent chats in that worktree window.

  4. Compare sidebar behavior to the previous version: worktree chats used to appear under a distinct sidebar tab/context; now they appear grouped with the main repo tab instead of per-worktree.

Expected Behavior

Each worktree opened as its own folder should have a distinct sidebar scope (or equivalent) so chats stay grouped per worktree, not merged under the main repository tab.

Operating System

  • MacOS

Version Information

Version: 2.7.0-pre.168.patch.0 (Universal)
VSCode Version: 1.105.1
Commit: 3f0e6a8c771f907d2f9207a19ab565b931ae61b0
Date: 2026-03-30T08:16:08.514Z
Layout: glass
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Additional Information

  • This affects worktree / parallel-agent workflows where separate chat threads per worktree are important.

  • If this was an intentional Glass / unified workspace change, a setting to restore per-folder or per-worktree chat grouping in the sidebar would resolve it.

Does this stop you from using Cursor?

  • No - Cursor works, but with this issue has changed my workflow with Glass (see Additional Information)
1 Like
2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

5

I have edited it. Thanks!

7

Hi @ayrmiz,

This is expected behavior in the Glass layout. Glass groups chats by repository (based on git remote URL) rather than by folder path, which is why worktrees of the same repo appear under a single sidebar section.

In the older editor layout, each worktree opened as a separate folder got its own sidebar scope. Glass changed this to a repo-centric model, which intentionally unifies worktrees of the same repository.

In the meantime, if per-worktree chat separation is critical for your workflow, you can switch back to the Editor layout (Cursor Settings > General > Layout) which preserves the old per-folder scoping behavior.

8

Oof. Mentioned in Cursor 3 merges multiple local clones into one GitHub repo in sidebar - #9 by longlostnick , but that makes this singular view pretty much DOA for folks that use multiple repo clones or git worktrees (which I assume is many of us?).

1 Like
9

+1, it would be really nice if Cursor could distinguish between not only repo remote paths, but also local paths for the cases Nick mentioned. It’s pretty common for me to clone the same repo to 2nd location so I can work on longer-running efforts, where switching branches is tiresome because it’s using a completely new / different set of dependencies installed (like for major migrations to a new React version, for instance).

1 Like