Starting an agent with a worktree does not create a worktree

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I initialize a new agent task in a worktree, but the task begins locally instead.

Steps to Reproduce

  1. New Agent
  2. Choose “Worktree”
  3. Submit prompt
    It’s not in a worktree

Expected Behavior

It should be in a worktree.

Is worktree creation now up to agents? This is a problem because:

  1. That’s not what the UI implies.
  2. Now all benign terminal commands require approval instead of auto-running.
  3. Apparently, one of my agents failed to create a work tree, or moved changes to main without asking, I didn’t realize it AND I PERMANENTLY DELETED UNTRACKED FILES IN THE DIFF VIEW, THINKING THEY WERE MISTAKENLY COPIED TO THE WORKTREE. But in fact, it was not the worktree because I guess the agent didn’t create a worktree like asked?! Those untracked files are now gone.

I have so far found Cursor 3 to be a major usability AND FILE INTEGRITY regression.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.0.4
VSCode Version: 1.105.1
Commit: 63715ffc1807793ce209e935e5c3ab9b79fddc80
Date: 2026-04-02T09:36:23.265Z
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: Darwin arm64 22.6.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

1 Like
5

Hey, thanks for the detailed report and the video.

This is a known issue. Worktree support in Glass (Cursor 3) is still not fully finished. Right now in Glass mode the worktree isn’t created automatically like it was before, and if the agent doesn’t run the internal instruction to create the worktree, it will quietly keep working in the main working directory. I get that this directly conflicts with what the UI shows.

As a workaround for now, in editor mode (not Glass) you can use the /worktree slash command directly in the agent chat. That’s more reliable. More details here: Can't find a way to run an agent on a worktree - #11 by Colin.

Let me know if you have any questions.

6

A post was merged into an existing topic: Can’t find a way to run an agent on a worktree