I have a hybrid workflow. I use a dedicated git worktree for each ticket I’m assigned, and I often use the git CLI to create these worktrees. Sometimes I even use (heresy!) IntelliJ to write code by hand. The new Cursor Agents view makes this workflow quite painful.
Workflow
Use Git CLI to create a new worktree.
Run command: cursor <new-worktree-dir>
Open Cursor Agents view
Write a prompt, expecting Cursor to make changes in the directory from which it was opened.
Problem #1
Cursor Agents view always opens in “Home,” regardless of the directory I invoked cursor with.
This is possibly even a regression? I don’t know what the design intent is.
Problem #2
The workspace selector does not allow me to pick from existing git worktrees. There’s no way to open my new worktree except via the OS file browser.
Problem #3
Even if it’s a recently-used workspace, the workspace selector does not show enough of the file path to be useful, no matter how much screen real estate I give it.
As you can see in the screenshot, the important bit of the path is truncated.
There’s no way to scroll this view. I can use type-ahead to narrow it down but there’s no way to see if I’m getting the right result.
These are all valid pain points, and you’re not alone in reporting them. Here’s where things stand:
Problem #1 (opens in “Home”) – This is a known issue. When you open Cursor via cursor <dir>, the Agents Window should default to that directory, but it currently doesn’t. The team is aware and tracking this.
Problem #2 (can’t pick existing worktrees) – The Agents Window currently manages its own worktrees via the /worktree slash command, but it doesn’t yet support selecting pre-existing worktrees created outside of Cursor. Support for importing external worktrees is planned as part of the ongoing worktree rebuild.
Problem #3 (path truncation) – Agreed, the current path display in the workspace selector makes it very difficult to distinguish between similarly-named directories. This is a UX gap the team is aware of.
For now, the best workaround for your workflow is to switch to the Editor layout (Cursor Settings > General > Layout). The Editor layout preserves per-folder scoping, so each worktree opened via cursor <dir> gets its own context. You also get access to the /worktree and /best-of-n slash commands there.
A few threads where we’ve addressed the worktree situation in more detail:
Cursor 3: Worktrees & Best-of-N – the official announcement explaining the new worktree commands, with details on multi-repo support and ongoing improvements
