Worktrees in agent sidebar

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I first opened the new agents window, I could see the 2 worktrees that I had. After a couple second they disappeared and now I can only see the git origin name of the project.

Steps to Reproduce

Not sure how to reproduce this. I tried the customize sidebar, but that didnt help. I also tried adding the worktree with open workspace.

Expected Behavior

I thought the worktrees would show up as separate section in the sidebar as it first did, i.e. agents in one worktree are a separate section.

Screenshots / Screen Recordings

Screenshot 2026-04-03 233446.png
Screenshot 2026-04-03 233446.png270×901 14.3 KB

Operating System

Windows 10/11

Version Information

Version: 3.0.9 (user setup)
VSCode Version: 1.105.1
Commit: 93e276db8a03af947eafb2d10241e2de17806c20
Date: 2026-04-03T02:06:46.446Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like
5

I saw a similar issue, not with worktrees but local workspaces. They suddenly disappeared, and I had to reopen them.

6

Same issue here. I saw multiple worktrees in a sidebar but then it changed to per repo. In my case i am working in a huge mono-repo, so per repo view is useless. Ability to see per-worktree agents are actually what’s blocking me switching to agentic view. My current workaround is using multiple instances of Cursor per worktree.

8

Hi all,

This is a known limitation in the Agents Window (Glass layout). The sidebar currently groups chats by repository (based on the git remote URL), so worktrees and multiple clones of the same repo appear under a single section rather than separately.

Per-worktree sidebar grouping in Glass is being worked on. In the meantime, worktrees are still available via the /worktree slash command in agent chat, which creates an isolated checkout for the agent to work in. More details here: Worktrees

A few related threads for context:

For per-worktree sidebar separation right now, your best options are:

  1. Switch to the Editor layout (Cursor Settings > General > Layout) – the Editor layout preserves per-folder scoping, so each worktree gets its own sidebar context

  2. Multiple Cursor instances per worktree (as Dmitrijs mentioned)

I understand this is a blocker for adopting Glass, especially for monorepo workflows. Your feedback here helps with prioritization.

4 Likes