Agents sidebar shows multiple identical sections for one local repo after path migration (all chats resolve to same path)

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Title: Agents sidebar shows multiple identical sections for one local repo after path migration (all chats resolve to same path)

Where
Cursor IDE — Agents / Glass sidebar

Version
Cursor 3.12.29 (stable)
Commit: cd1c87ff9b66021918fb9731605f8d1d5fd2f0b0
OS: Windows 10
Describe the bug
After moving a git repo off OneDrive/Documents to a single canonical path (C:\Users<user>\GitHub\ha-milford), the Agents sidebar still shows multiple separate sections all labeled ha-milford (3–4).

Hovering chats in those sections shows the same path (C:\Users<user>\GitHub\ha-milford). There is no UI way to tell the sections apart, merge them, or remove extras. No “Group by” control is visible in this build.

Underlying chat data appears consolidated to one workspace/path; the duplication is in the Agents sidebar grouping/UI only. Internally, stale workspace IDs from old path spellings (…\OneDrive\Documents\GitHub\ha-milford and …\Documents\GitHub\ha-milford, which is a junction to OneDrive) remain in sidebar section order (workspace: alongside repo:github.com//ha-milford) and get reintroduced on relaunch even after cleanup.

Steps to reproduce
Use a repo under OneDrive/Documents (or a Documents junction to OneDrive), create several Agent chats.
Migrate the clone to a non-OneDrive path (e.g. C:\Users<user>\GitHub<repo>), open only that path going forward.
Optionally update chat workspace metadata so chats point at the new path.
Fully quit and reopen Cursor.
Observe Agents sidebar: multiple sections with the same repo basename; hover shows the same new path on chats.
Expected
One Agents sidebar section per logical repo/path once chats all resolve to that path.

Actual
Multiple identical ha-milford sections; chats in each show the same GitHub path on hover; no GUI merge/dedupe; no visible Group by control.

Extra context
C:\Users<user>\Documents is a junction to OneDrive\Documents, so historical path aliases were the same folder spelled two ways, then a third canonical clone under GitHub.
Related (not the same): Glass repo-centric grouping threads, e.g. 156331, 156578, 158523 (“identically named workspaces”).
This case is the opposite leftover: same path, multiple ghost sections after migration.
Impact
Agents sidebar is hard to use for that repo; cannot identify or consolidate duplicate sections from the UI.

Steps to Reproduce

Appeared after lastest upgrade. Screenshot of agents sidebar attached.

Steps to reproduce

  1. Use a repo under OneDrive/Documents (or a Documents junction to OneDrive), create several Agent chats.
  2. Migrate the clone to a non-OneDrive path (e.g. C:\Users<user>\GitHub<repo>), open only that path going forward.
  3. Optionally update chat workspace metadata so chats point at the new path.
  4. Fully quit and reopen Cursor.
  5. Observe Agents sidebar: multiple sections with the same repo basename; hover shows the same new path on chats.

Expected Behavior

One Agents sidebar section per logical repo/path once chats all resolve to that path.

Screenshots / Screen Recordings

Capture.JPG
Capture.JPG474×1103 33.8 KB

Operating System

Windows 10/11

Version Information

Version: 3.12.29 (user setup)
VS Code Extension API: 1.128.0
Commit: cd1c87ff9b66021918fb9731605f8d1d5fd2f0b0
Date: 2026-07-21T03:26:05.811Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.19045

Additional Information

Extensive chat with cursor (AI auto) unable to resolve issue.

C:\Users<user>\Documents is a junction to OneDrive\Documents, so historical path aliases were the same folder spelled two ways, then a third canonical clone under GitHub.
Related (not the same): Glass repo-centric grouping threads, e.g. 156331, 156578, 158523 (“identically named workspaces”).
This case is the opposite leftover: same path, multiple ghost sections after migration.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. I see the screenshot with several ha-milford sections in the Agents sidebar.

This is a known bug on our side. It’s a grouping and visibility issue, not data loss. The chats still open normally. The sections in the Agents sidebar are grouped on the fly based on the live workspace or repo identity for each chat, not based on what’s stored in local storage. Older chats created before repo tracking existed don’t have repo metadata, so they fall back to a stale workspace identity from older path spellings like a junction and a OneDrive alias for the same folder. That’s why one physical repo gets rendered as multiple sections with the same name. Editing the local storages won’t move them, so nothing changes.

A few things that can help right now:

  1. Group by control is available in 3.12.29. It’s behind the filter icon Customize Sidebar at the top of the Agents sidebar, under the Grouping submenu Workspace, Repository, Updated, Status. Switch to Updated or Status. That disables workspace or repo grouping and puts all chats into a single list by recency or status, so the duplicate sections collapse.

  2. Right-click the header of the extra section, then select Remove from Sidebar. This hides the ghost section. It can come back after new activity, that’s also known behavior.

  3. Going forward, open the repo only via the canonical path C:\Users\<user>\GitHub\ha-milford so new chats group under the repo correctly.

We’re tracking this issue, but to be transparent, improvements won’t retroactively migrate chats created before workspace tracking existed. Switching the grouping mode is the most reliable way to access them. I can’t share an ETA for a fix yet.

Let me know if switching to Updated or Status pulls everything into one list.

7

After update your suggestions work to get rid of duplicates. No repo show in side bar , not what iI was hoping for, but its less confusing. Thanks.